4 ms·
Agree with this fully because had experienced this first-hand. We had a working monoloth, it was not the best but it was stable and it did the job. Then new CT
by romanovcode 11y ago
Agree with this fully because had experienced this first-hand.
We had a working monoloth, it was not the best but it was stable and it did the job. Then new CTO comes in and spreads the microservice hype. We built everything in microservices in such hurry and didn't even implement the most important part - the orchestration.
Now system is doing pretty much the same thing, except it's way less stable. But hey, we're microservices! (Also went from PHP to Node, which also IMO is a huge mistake)
- qaq 11y agoI totally agree with the article but your example seems a bit flawed.If you rebuild anything "in such hurry and dodn't even implement the most important part...". Regardless of architectural choices you will end up with something "way less stable".
- zwischenzug 11y agoI've seen this happen twice - once with the microservices dogma, and then with the introduction of an ESB to a large organisation without thinking about the cost of the orchestration...