You Don't Need Microservices
medium.com
You Don't Need Microservices
1–10 of 169 posts
Re: You Don't Need Microservices
#2Why the monolith should remain the default choice for new, small, and medium-sized engineering teams. Considering how we can leverage the monolith to realize the benefits that microservices claim for themselves.
Re: You Don't Need Microservices
#3Aren't microservices nice because they allow you to have different teams own different parts of the code and minimize the communication overhead?
Re: You Don't Need Microservices
#4While I agree that there are definitely some cautionary tales regarding microservices, consistent and autonomous delivery across many teams with a complex monolith is equally if not more difficult than some of the cons that come with microservices.
I don't think the answer is as easy as "you don't need microservices". I think the answer is "you can effectively use both".
Re: You Don't Need Microservices
#5Aren't microservices nice because they allow you to have different teams own different parts of the code and minimize the communication overhead?
Yea. IMO, microservices are usually more of an organizational solution than a technical solution
Re: You Don't Need Microservices
#6Aren't microservices nice because they allow you to have different teams own different parts of the code and minimize the communication overhead?
That makes a lot of sense when you have real team (and most importantly) process boundaries. Isolate the code and deployment aligned with your team and process boundaries.
But if you're a company of 10-20 people all pretty much working on the same code? Microservices just adds complexity and overhead. Deployment, telemetry, documentation, version synchronization, tracing -- everything becomes more complex when you start creating boundaries between sub parts of your system.
For me, microservices are about boundaries. The question is what benefit that boundary provides for the team. For large companies where there are many discrete teams following different processes and release cadences, microservices might be worth the overhead. For small companies, it is wasted effort.
Re: You Don't Need Microservices
#7>Modularize Your Monolith
It is true that probably any monolith can be break down into components, that won't prevent the full redeployment (and all the risks that it brings) though.
I think in reality no one needs Microservices, or Monolith for that matter. You would pick the poison that adjust the best to your needs.
Re: You Don't Need Microservices
#8Aren't microservices nice because they allow you to have different teams own different parts of the code and minimize the communication overhead?
That makes a lot of sense when you have real team (and most importantly) process boundaries. Isolate the code and deployment aligned with your team and process boundaries. But if you're a company of 10-20 people all pretty much working on the same code? Microservices just adds complexity and overhead. Deployment, telemetry, documentation, version synchronization, tracing -- everything becomes more complex when you st…
Sometimes boundaries are good.
Not all things should be easy.
The question is which things need to be easy, and which things need to be hard?
Often the answer is "we don't know" but there is still an optimal answer to the question.
Re: You Don't Need Microservices
#9I wrote a library [1] for Laravel that lets you put a kind of "microservice" inside of your monolith.
It lets you develop, deploy, and execute AWS Lambda functions from your Laravel application.
The theory here is that sometimes you need some other language/infrastructure beyond what you're comfortable devops-ing yourself, and Lambda is actually quite good at providing you with an entire stack of stuff you don't have to own.
So if you need a single Node, Python, or Ruby function you can put just that part on Lambda and still call it from Laravel as if it were a native PHP function. No API gateway or anything to muck about with, either.
Is it a true microservice? Not really, although who knows what that actually means. It does allow you to take advantage of some parts of microservices without the pain though!
Re: You Don't Need Microservices
#10Why the monolith should remain the default choice for new, small, and medium-sized engineering teams. Considering how we can leverage the monolith to realize the benefits that microservices claim for themselves.
[deleted]