We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

How To Build a Python Microservice Without Losing a Job

Formal Metadata

Title
How To Build a Python Microservice Without Losing a Job
Subtitle
Avoid typical microservice pitfalls: about the stack, communication and deployment
Title of Series
Number of Parts
118
Author
License
CC Attribution - NonCommercial - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Sarcastic talk, sharing real-life experience on both technical and social aspects of doing an architecture migration to microservices without losing a job. Any change in software architecture is a significant time investment. 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. I would like to share typical pitfalls of choosing a framework stack, communication protocol, conventions, and deployment process — all covered by real projects.
Keywords