Microservices vs Monolithic Architecture: A Practical Approach
📍 Monolithic and Its issues
🙂 When we start learning backend development and implementation, many of us implement all our functionalities in one codebase. Forex. If we want to build the backend of an e-commerce store then we can go with the project with a single index.js file including the functionality of:-
- Shopping Orders
- Items or Products
🙋 But is it right to do so? We do have the advantages of the monolithic architecture like easy testing, and easily deployable. But we do have some issues like scalability, load balancing, and error handling.
🎯 With Microservices we can address these issues and we also can use some of the advanced technologies like Docker, Kubernetes effectively.
🎯 Microservices architecture includes working of separate services that are loosely coupled and work on different ports and with their own database generally.
😌 Let’s take an example of an eCommerce app with payment, product, and shipping service. It may look like this:-
–> Used:- JAVA, MYSQL
–> Working on:- PORT 3001
–> Used:- NODE, MongoDB
–> Working on:- PORT 4000
–> Used:- Python, SQLite
–> Working on:- PORT 3002
🙂 Now these services can communicate with each other using APIs and all. We have the advantages of load balancing, error handling (If payment service fails it will not affect the product service), and modular code with this architecture (Microservices).
📍 Microservices Patterns
🔥 While we implement microservices, there are some patterns like using BFF (Backend for frontend), Service Discovery
BFF (Backend for frontend)
👉 Here, we have API Gateway that handles all the stuff like Authentication, load balancing ,etc and act as a reverse proxy to accept the incoming requests and gives the appropriate results.
Service Discovery Registry
👉 It is used when we have multiple instances of a service and we get the address of the particular instance from the service discovery.
🙂 Note:- We will see the implementation too, Don’t get panic if you are not able to understand fully.
👉 This is one of the method where we can make calls between the services. You can make Sync calls or Async calls depending on the functionality. Here, we have used the Queue where the messages will be passed from service 1.
👉 This situation arises when one or more calls fails in between and other keeps waiting. forex. Service2–>Service3 call fails and Service 1 will keep waiting. In that case, we can do following:-
- Use the last recent call stored inside the cache from service 2 and 3 and give the response
- Fallback call:- It is the case when Service 3 calls another third party API and waiting for a long time. Then Service 2 can directly call to that 3rd party API
Log Aggregation Pattern
👉 It is the Pattern where we store all the logs of our active microservices so that we can track and monitor them
👉 It is a cloud computing application where we can use Functions that triggers while we call. These functions do have a cold start time though but might be very effective in most of the applications.
🔥 Follow for more. We will see the implementation in our next Blog. Share this series and drop your views