Microservices are relatively small and autonomous services deployed independently, with a single and clearly defined purpose. Microservices enable smaller codebases, allowing small teams to work on separated and focused services by using the most suitable technologies for their job that can be deployed and scaled independently. In this work, we briefly introduce antipatterns and a catalog of antipatterns with possible solutions, based on common bad practices that have created problems for practitioners in the past. The identification of these smells is based on a survey performed over the course of two years among 72 senior developers focusing on bad implementation or design practices they found during the development of microservices-based systems and on how they overcame them.

1. From Monolith to Microservices:
Migration Patterns and Benefits
Davide Taibi
SFScon 2017
Microservices Antipatterns - SFScon

2. Microservices Antipatterns - SFScon
Microservice is like teenage sex
everyone talks about it,
nobody really knows how to do it,
everyone thinks everyone else is doing it,
so everyone claims they are doing it…

3. Microservices Antipatterns - SFScon
Background
[2] PWA Research

4. Microservices Antipatterns - SFScon
Background
[2] PWA Research

5. Monolith
Microservices Antipatterns - SFScon
[3] Matt Stine. Developing for the Cloud Track

6. Microservices
Microservices Antipatterns - SFScon
[3] Matt Stine. Developing for the Cloud Track

7. What is a microservice?
Microservices Antipatterns - SFScon
Fine-grained units of execution designed to do one thing very well [1]
Based on the single responsibility principle
“Gather together those things that change for the same reason,
and separate those things that change for different reasons.”
[1] Janakiram MSV. “Microservices: How to prepare next-generation cloud applications“ Computer Weekly – 3 March 2015

8. Main Benefits
Microservices Antipatterns - SFScon
• Maintainability
• Independent and self-deployable services
• Independent service testing
• Simplified distributed development.
• Small size of each microservice è increasing code
understandability
• Scalability
• Scaling monolithic systems requires huge investment
• microservices are not automatically scalable

9. Migration Process (1/2)
Microservices Antipatterns - SFScon

10. Migration Process (2/2)
Microservices Antipatterns - SFScon

11. Conclusion
• Microservices can improve the quality of your software
• Are not the silver bullet
• Need highly experienced software architects
Microservices Antipatterns - SFScon

12. Thank you for your attention!
davide@taibi.it
Microservices Antipatterns - SFScon