Before you default to microservices, weigh hidden costs and consider a modular monolith or SOA. Learn when Docker delivers consistency and scale—without sprawl.
The interesting thing about the original Amazon Prime Video blog that the article refers to, was that they problem with microservices wasn’t the development of them, or the deployment, but the cost of deployment in terms of run time. After all, if you’re doing a pipeline of anything, as they were doing, and your pipelines are very very constant, then it can just be run on a single system instead of constantly passing messages between systems running microservices.
The interesting thing about the original Amazon Prime Video blog that the article refers to, was that they problem with microservices wasn’t the development of them, or the deployment, but the cost of deployment in terms of run time. After all, if you’re doing a pipeline of anything, as they were doing, and your pipelines are very very constant, then it can just be run on a single system instead of constantly passing messages between systems running microservices.