Top Microservices Patterns

 What are the top microservices patterns?

When we dive into Microservices Architecture we can understand it comes with good advantages with some challenges to solve these challenges we need to follow certain patterns.

Even Driven pattern - Thumb rule of microservices is to have individual database for each microservices , so you can imagine if you have services which will update database, in this situation you need to implement event driven pattern to maintain consistency between the database tables.

Observability Patterns- We need a centralized logging service that aggregates logs from each service instance. For example, if you are using PCF(Pivotal cloud Foundry) does have Loggeregator, which collects logs from each component (router, controller, etc...) of the PCF platform along with applications . These we can connect to the Logger maintain systems like Splunk .

Cross-Cutting Concern Patterns - To Explain this Config server is the best example , this is used to externalize the configurations based on the Test , Acceptance , Production Environment we can maintain different property files with different profiles.

Circuit Breaker Pattern - As name says it will act as Circuit breaker , we can take advantage of display fallback messages if a service is going to take more time to response or if it is failing . Hystrix is the Library which is used widely to implement these kind of solutions.

Blue-Green Deployment Pattern - main Advantage of Microservices is its blue green deployment pattern . We can make old version as Blue and new version as Green , slowly divert the routers to new green version , so with this we can avoid down time and if any problem we can rollback it easily. Like this lot of other patterns are there which will help to solve challenges while implementing the microservices Architecture