3 ms·
re this: > The better strategy is a bottom-up approach. Start with > a monolith or small set of coarse-grained services and > work your way up. Make sure
by andyidsinga 11y ago
re this:
> The better strategy is a bottom-up approach. Start with
> a monolith or small set of coarse-grained services and
> work your way up. Make sure you have the data model
> right.
the part about "or a small set of coarse-grained services"
I like this advice, but this is effectively starting with SOA! - just coarse grained. So the drive of this post should be so start with a simpler SOA, don't pre-optimize etc, not build a monolith.
- tragic 11y agoWhile you're technically correct, bear in mind that the central difficulty with microservices is managing dependencies. The worst-case for dependencies across service boundaries in a system with n services is (n - 1)*n. If n is 3, you have a theoretical maximum of 6 direct dependencies. If n is 10, that number is 90. Which is quite a big difference.
- lmm 11y agoThat part's a sop. Start with a set of size 1 - aka a monolith.