Re:Give me back my monolith (2019)
by jbluepolarbear on Tuesday May 10, 2022 @12:41PM
(#31329178)
A better solution would be to build modules independently and have a single service use each module. Then things are unified, each team has a client it must deliver to, and issues must be fixed in order for them to be released in the final product. How are microservices better? Often each service is out of sync with each other, one service will upgrade and break another, that’s not possible with a single source and multiple modules.
[ Parent
| on HN ]
Do people not version their API requests?
Re:Give me back my monolith (2019)
by jbluepolarbear on Tuesday May 10, 2022 @01:52PM
(#31330136)
Yep and it gets worse, you’ll have teams add new breaking features or deprecate features without letting the other team know. Hey their tests pass so what do they care. I’ve worked with both strategies and modules over microservices are easier to integrate, ensure integrity, and reduces the probability that stuff breaks in production. Often microservices develop to a set of requirements and never consider the client that will be using that service. With modules that can’t happen.