To understand the advantages of microservices architectures today, it's critical to understand where it all started from.
Monolithic applications
Initially each application, residing on a single server, comprised three layers:
Presentation
Application/business logic
Database
These layers were built in a single, intertwined stack located on a single, monolithic server in a data center. This pattern was common across every industry vertical and technology architecture. Generally speaking, an application is a collection of code modules that serve a particular function-for example, a database, various types of business logic, graphics rendering code, or logging.
In this monolithic architecture, users interacted with the presentation layer, which talked to the business logic layer and the database layer, and information then traveled back up the stack to the end user. Although this was an efficient way to organize an application, it created many single points of failure, which could result in long outages if there was a hardware failure or code bug. Unfortunately, "self-healing" did not exist in this structure. If a part of the system was damaged, it would need to be repaired by human intervention in the form of a hardware or software fix.
Furthermore, scaling on any one of these layers meant purchasing an entire new server. You had to purchase a monolithic application running on a single server and segment a portion of users over to the new system. This segmenting resulted in silos of user data that had to be reconciled by nightly batch reports. Thankfully, client need became thinner as webpages and mobile applications became more popular, so new methods of application development began to take shape.
Read more: https://www.ateamsoftsolutions.com/top-45-microservices-questions-and-answers-what-are-microservices/
𝐁𝐎𝐎𝐊 𝐎𝐍𝐄 - 𝐅𝐢𝐫𝐞 𝐒𝐞𝐫𝐢𝐞𝐬 only has 7 chapters available because this book is now available FOR FREE on kindle unlimited!!
Books 2 & 3 will be in full!
-----
Blurb for book 1:
𝐃𝐘𝐋𝐀𝐍 𝐇𝐀𝐑𝐑𝐈𝐒
I messed up - I messed up in typical Dylan fashion because I could never stand up to my Dad, I just couldn't be the Alpha that I was meant to be, that my older brother would have been proud of.
Instead I was the Alpha that locked his mate away for a crime that I didn't even know if he actually committed, I thought about rejecting him because he was a man and I'm not gay and I refused to give into the bond and love him back.
I felt insecure around Raiden because he's a feline.
I was insecure because he's stronger, faster, more dominant and I hated how much my body gave into him - how much my body wanted to submit to him because I'm an Alpha and Alphas don't submit.
So I caved and I tainted our bond, I hurt him beyond repair and when I just couldn't deny the bond anymore, I found out just how hard it would actually be to gain his trust back - to get him to want me again.
Our bond ended with my mistake but our story began with my redemption.