3 ms·
Use the best tool for the job. It's stupid to think of monoliths vs microservices. You can use both if the problem requires it. For example I'm currently worki
by pier25 4y ago
Use the best tool for the job. It's stupid to think of monoliths vs microservices. You can use both if the problem requires it.
For example I'm currently working on an audio hosting service. The main app is a monolith where 90% of the code resides but there are a couple of ancillary services.
Audio encoding (which is heavily CPU bound) is a serverless microservice that can scale up and down as needed. Users don't upload content constantly, but when they do, you want to be able to encode stuff concurrently without blocking the main app. Audio streaming is also a serverless microservice because hey for every user uploading content you can have 1000x consumers (or more).
- ricardobeat 4y agoThis argument is brought forth a lot, but it misses the point. Often people think microservices are the right tool for the job, but they vastly underestimate the complexity that it entails.
- mdaniel 4y ago> Often people think microservices are the right tool for the job, but they vastly underestimate the complexity that it entails. And that goes 10x if deploying, monitoring, or debugging said services is Someone Else's Problem ™ I'm also cognizant that such a situation is just as much an organizational/people problem as the rest of this debate, but I have a sore spot around people making decisions where they don't have to suffer the consequences from them
- pier25 4y agoIf you can solve a problem without a microservice then probably it's not the right tool for the job.
- candybar 4y agoI think your position is basically the same position that most people that advocate for monoliths (which btw is a bit of a strawman created by microservice architecture advocates in the first place) hold. People are objecting to service/network boundaries as a default domain decomposition tool and arguing that it should be used instead when there are clear and immediate technical advantages to do so.
- roflyear 4y agoYeah. Agreed. For example I need to ocr things sometimes. I literally have a process running an ocr server. It's basically a microservice.