Don’t start with a monolith… when your goal is a microservices architecture. Great article by @stilkov on @martinfowler web site. Check it out: martinfowler.com/articles/do… #microservices #monotith
3
3
12
I fully agree with @simonbrown if you are not able to build a well structured monolith, why should you be able to build a well structured microservices system....
1
2
That is completely backward, and @simonbrown and I have disagreed about this for a long time :)
1
1
We have? I thought that we disagreed about monolith first vs going microservices from the start ... not a team’s lack of ability to create a decent modular codebase. 😀
1
3
Maybe I remember our discussions incorrectly, entirely possible. My point is: The whole point of microservices/self-contained Systems is that they prevent you from accidentally creating tight coupling
2
3
I agree 100% that a distributed monolith is much worse than a non-distributed one
1
1
2
Replying to @stilkov @simonbrown @SebastienAndreo @educostadev @JuttaEckstein @martinfowler
But the early-stage separation, if done correctly, can help you prevent creating it in the first place

Sep 26, 2019 · 8:14 PM UTC

2
Replying to @stilkov @simonbrown @SebastienAndreo @educostadev @JuttaEckstein @martinfowler
If we were able to create monoliths with perfectly decoupled, internal modules, there’d be indeed no need for microservices
1
1
4
more replies
Replying to @stilkov @simonbrown @SebastienAndreo @educostadev @JuttaEckstein @martinfowler
But that’s just like saying we wouldn’t need debuggers if we simply created correct programs in the first place
1
1
more replies