Monolith First (2015)
What many seem to have missed from this is the bit at the end where Fowler concedes:<p>> I don't feel I have enough anecdotes yet to get a firm handle on how to decide whether to use a monolith-first strategy.<p>after linking and mentioning points of a guest post [1] (with which I strongly agree) which argues against starting with a monolith. A key part from that post:<p>> Microservices’ main benefit, in my view, is enabling parallel development by establishing a hard-to-cross boundary between different parts of your system. By doing this, you make it hard – or at least harder – to do the wrong thing: Namely, connecting parts that shouldn’t be connected, and coupling those that need to be connected too tightly. In theory, you don’t need microservices for this if you simply have the discipline to follow clear rules and establish clear boundaries within your monolithic application; in practice, I’ve found this to be the case only very rarely.<p>[1] <a href="https://martinfowler.com/articles/dont-start-monolith.html" rel="nofollow">https://martinfowler.com/articles/dont-start-monolith.html</a>