I just want to say that although this is an opinionated article and I may not fully agree with the points presented, I really enjoyed the way you presented the arguments.

A part of me disagree with you on the monoliths, but throughout the course of my career I've seen situations where I mumbled to myself "Why don't we try basics like monolith and start going from there?", usually when business or product peeps comes in and expect super fast development and time to market window is very small, so yeah I totally understand your points here.

Also, monoliths doesn't mean "unstructured" or "messy", it just means all the logics are centralized. Monoliths can still be modularized and organized. It does present some disadvantages; but really the situation may vary from one to another so we can't really say "Uh monoliths are bad, microservices are good hurr durr". It really depends on the needs really.

I still prefer microservices, but I can see why one wants to start with monoliths first, even though I really think it may present problems in the future.

Anyway, great article!

--

--

--

Software Developer @ DANA

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Adhiputra Perkasa

Adhiputra Perkasa

Software Developer @ DANA

More from Medium

The hedge fund hiring underprivileged students as interns

The Benefits of Educational Trivia Games for Kids

A Retrospective on My Last Role as a VP R&D

Career Challenges: Turning your wheels in search of that next solution and feeling like you’re at…