Microservices are not just a bunch of little apps, it’s a connected ecosystem.
Within a monolith, code modules invoke each other simply by using language- level function calls, but in a microservice architecture, communication between components does not come for free anymore. Choosing not just a protocol, but a paradigm for communication between endpoints is considered the most tricky issue of microservice approach.
Writing microservices in Python is a joy, but when you decide on it, there is often no way back. Therefore it is always an advantage to know what to expect in advance, not just from inspiring blog posts but also from the harsh reality.
Having a bunch of smooth as well as tricky microservice migrations in the past, I would like to share typical pitfalls of choosing a framework stack, communication protocol, conventions, and deployment process — all covered by real projects.
Feedback form: https://python.it/feedback-1638
in __on Saturday 4 May at 17:15 **See schedule**