Microservices key points to be considered

Recently watched on YouTube video about microservice it’s like a conversation between two great persons samNewman and martin fowler It makes sense to watch this wonderful conversation And I got some bullet points from their speech, it’s very super cool to know about in this era of microservice and here I mentioned some of the key points.

1.When to use microservices

Our industry tends to focus on tech instead of the outcome. One should use microservices as a means to obtain the desired outcome rather than for the sake of using new technology.

2.Don't use microservices as a default option?

Microservices shouldn’t be the default option. If you think a service architecture could help, try it with one of the modules from a very simple monolith typology and let it evolve from there

3.Top 3 reasons to introduce microservices

• Zero-downtime independent deployability
• Isolation of data and of processing around that data
• Use microservices to reflect the organizational structure

4.How to avoid a distributed monolith

• Creating a deployment mechanism
• Looking for patterns and deciding how to deal with them

5.Why strive for independent deployment

• It’s easier to limit the impact of each release when using microservices
• As the team size increases it gets exponentially harder to coordinate a deploy

6.Organizations and teams

We tend to violate monolith architecture by not respecting the modules. Breaking them into services makes it hard to do so.

7.Handling data

A lot of the complexity of breaking complex systems lies in the data. After extracting the microservice you need to understand what part of the old database this system uses.

8.Handling people

Microservice architectures will very rarely save you money. There has to be a willingness to change as an organization if you want to make the most out of using microservices.

You can go and watch the full video by using the link
https://www.youtube.com/watch?v=GBTdnfD6s5Q&feature=youtu.be