2 ms·
And if they do call back and forth, then all of the advice Fowler gave in the initial article still holds. So my point is his earlier views are for the most par
by vidarh 10y ago
And if they do call back and forth, then all of the advice Fowler gave in the initial article still holds. So my point is his earlier views are for the most part not in contradiction with the microservices patterns - if anything, the latter is a evolution of the former, and the combination can basically be distilled down to:
If you must/want to split, split along service boundaries where communication is mostly with the client, and minimise communications surfaces between services. If you do that, you gain ability to scale services separately, and develop them separately.
If there are lots of interdependencies, you have bought yourself lots of latency and reliability issues for little gain elsewhere.
> I'm not saying it's ideal but people who write crap software in monolithic form are only going to do a worse job when faced with the additional complexity of having it all chopped up into little pieces.
I agree with that, and those people should probably start with articles like the linked one to learn to think about latency issues first.