3 ms·
> Microservice architecture tells you more about how and where to split The architecture doesn't tell you anything: it is you who decide how to split. Yes, the
by kilburn 8y ago
> Microservice architecture tells you more about how and where to split
The architecture doesn't tell you anything: it is you who decide how to split. Yes, there are guides and what not to help you make this decision, but again you could do exactly the same splits in a monolithic system.
> Sure. You can also write really gross, convoluted monoliths.
Totally. That's what I was implying when I said "complexity grows exponentially and developers want to run away from the project like hell".
> they found that microservices allowed them to move faster on features
While the article is fine, I don't agree with this affirmation at all. They rewrote the entire system (bit by bit) using better engineering principles, better internal organization, and with a lot of experience about their domain that they didn't have before. As I see it, the outcome you see here is not "microservices!", it is just "doing a better job".
- staticassertion 8y ago> The architecture doesn't tell you anything: it is you who decide how to split. I don't really agree. The major difference between SOA and Microservice is the guiding principals, such as the bounded context. > As I see it, the outcome you see here is not "microservices!", it is just "doing a better job". Maybe so.