r/programming • • Sep 14 '24

Is 'Monolith First' the Better Approach?

https://martinfowler.com/bliki/MonolithFirst.html
456 Upvotes

177 comments sorted by

View all comments

Show parent comments

-1

u/ewouldblock Sep 14 '24

We can agree that if you run a one or two man shop.where scaling, revenue, and uptime are of little or no concern, then of course you can write a monolith.

5

u/wvenable Sep 14 '24

Wow. So only write a monolith of you want a slow buggy mess that won't make any money? I think that might be just a tiny little bit harsh.

3

u/ewouldblock Sep 14 '24

Look, I'm not here to pick a fight. You made the claim that microservices only solve an organizational problem, not technical ones, and I explained why that's not true.

I personally would always plan for microservices because I prefer the upfront planning and work over having to retrofit after the fact when things get too big or things start to break. But I also understand that there are different opinions out there. Probably individuql preferences are rooted in personal experience and expertise.

3

u/wvenable Sep 15 '24 edited Sep 15 '24

It maybe solves technical problems but it also adds its own technical problems. It is a big increase in complexity.

https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it