Re:Give Me Back My Monolith
by gregorygoc on Wednesday March 13, 2019 @06:27PM
(#19384568)
You must be doing something wrong. In a company I work for, we clearly have separated microservices by bounded context, thus making them completely decoupled.
[ Parent
| on HN ]
Re:Give Me Back My Monolith
by jasonpeacock on Wednesday March 13, 2019 @06:53PM
(#19384785)
This is the key - decoupled. When you have to rollback commits across multiple service, they are not decoupled, and you're doing something wrong.
Each service should be fully independent, able to be be deployed & rolled-back w/o other services changing.
If you're making API changes, then you have to start talking about API versioning and supporting multiple versions of an API while clients migrate, etc.
>then you have to start talking about API versioning and supporting multiple versions of an API while clients migrate, etc.
Which adds some more complexity that just does not exist in monolythic architecture
Re:Give Me Back My Monolith
by icebraining on Wednesday March 13, 2019 @07:41PM
(#19385124)
Sure it does. Once you have a large monolith, the same coordination problems hit. Just ask the Linux kernel developers: https://lwn.net/Articles/769365/