Moving monolithic to microservices

Typically, application architecture is the monolithic design that contains a Model-View- Controller (MVC) and every component within a single, big binary. A monolithic design has some benefits, such as less latency within components, being all in one straightforward package, and being easy to deploy and test.

However, a monolithic design has some downsides because the binary will be getting bigger and bigger. You always need to take care of the side effects when adding or modifying the code, therefore making release cycles longer.

Containers and Kubernetes give more flexibility when using microservices for your application. The microservices architecture is very simple and can be divided into some modules or some service classes together with MVC:

Monolithic and microservices design

Each microservice provides a Remote Procedure Call (RPC) using RESTful or some standard network APIs to other microservices. The benefit is that each microservice is independent. There are minimal side effects when adding or modifying the code. Release the cycle independently, so it perfectly ties in with the Agile software development methodology and allows for the reuse of these microservices to construct another application that builds the microservices ecosystem.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.144.172.38