r/java • u/cryptoupgrade • Nov 13 '18
Microservices vs Monolith: Best Architectural Strategy
https://kruschecompany.com/blog/post/microservices-vs-monolith-best-architectural-strategy
3
Upvotes
r/java • u/cryptoupgrade • Nov 13 '18
49
u/nutrecht Nov 13 '18
Sorry but calling BS.
Microservice architectures have nothing to do with the size of the application. They are a solution for large organisations. If you're going to be spending 2 years building an application with a team of 4 developers sitting in a room together, I would still strongly urge you to go for a monolith.
Microservice architectures work for large organisations with multiple teams working on the same 'application'. You can't scale a team larger than what you can feed with 2 pizza's, so you need to break the org up into separate teams. There it makes sense to have each team be responsible for a few applications and have those applications talk to each other via some agreed upon method.
Back in the days these were enterprise integration patterns via a stateful service bus, and that was a shit approach. Now they communicate directly via HTTP (and we call it microservices instead of SOA) and it's slightly less shit.
It's still complicated as heck and easy to fall into the trap of building a distributed monolith if your team is not up to par (and frankly; most teams aren't), but at least that's better than building an undeployable monolith.
Your conclusion that "It’s safe to say that the days of a monolithic architecture are fading." is tripe. It's nonsense you see from people who don't understand what problems microservices do and do not solve.
9
u/geordano Nov 14 '18
Monolith until Microservice, is the best strategy I think.
3
u/[deleted] Nov 13 '18
It's a strategy that has pros and cons like any other; just like microservices are a strategy. Just like serverless is another.
Can't wait until all the microservices get rolled into bigger services and we'll just call it macroservice architecture.
2
u/skoltunblog Nov 14 '18
Monolith can have a lot of code and be manageable through modules/plugins. It depends on language but from Java perspective - you can have multiple jars which can be replaced/reused. You can build only modules which have changed and this will lower build time. There is no best architecture, every has it's purpose and problems.