- cross-posted to:
- [email protected]
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
- [email protected]
You must log in or register to comment.
Microservices are great if you have enough traffic that you can get an efficiency gain by independently scaling all those services. But if you aren’t deploying onto thousands of servers just to handle traffic volume, you probably don’t need 'em.
Your startup that has no users yet does not need the kind of architecture that Google uses, because your startup doesn’t have the scaling problems that Google has.
In defense of those startups, I’m sure most of are doing it because theyve got organizational PTSD from beeing places be too fucked to be able to update their architecture rather than just overeagerness.
Well yeah, but you don’t solve that by layering more complexity on top of it. If you can’t yet release your code onto five servers without breaking the world for all users, you’re not yet into a place where you need fifteen microservices. Google didn’t have Kubernetes or Borg when they started out either; they had servers held together with Lego blocks because that’s what they happened to have.
Microservices are great if you have enough traffic that you can get an efficiency gain by independently scaling all those services. But if you aren’t deploying onto thousands of servers just to handle traffic volume, you probably don’t need 'em.
I don’t think that’s a valid take. Microservices have nothing to do with scaling or performance, at least for 99% of the cases out there. Microservices are a project- and team-management strategy. It’s a way to peel out specific areas of responsibility from a large project, put together a team that is dedicated to that specific area of responsibility, and allow it to fully own and be accountable for the whole development life cycle, specially operations.
Being able to horizontally scale a service is far lower in the priority queue, and is only required once you exhaust the ability to scale vertically.
Microservices have nothing to do with scaling or performance,
Microservices are not just about scaling and performance but it is a core advantage. To say they have “nothing” to do with it is outright false.
Scalability isn’t something you pull out of the pocket when you need it, you must incorporate scalability by design in everything you do. (Same as with security, and testability, etc.)
Microservices are about modular design and decoupling units of code from each other. Having a bunch of pieces of code run together on a monolithic group of resources that you choose to scale vertically becomes a choice not the be-all-end-all way of doing things.
Being able to horizontally scale a service is far lower in the priority queue, and is only required once you exhaust the ability to scale vertically.
The problem with this approach is that switching from vertical to horizontal is extremely hard if you didn’t plan for it from the start. Thinking in monolithics is a very hard habit to break and it’s good odds that any platform that is steeped in verticality will be permeated by it at all levels. You can’t just come in and switch, you typically end up having to uproot and redesign a lot of things from scratch, which in most cases ends up as a non-starter from a cost perspective.
Microservices are not just about scaling and performance but it is a core advantage. To say they have “nothing” to do with it is outright false.
They have nothing to do with performance. You can improve performance with vertical scaling, which nowadays has a very high ceiling.
It’s not a coincidence that startups are advised against going with microservices until they grow considerably. The growth is organizational, and not traffic.
Microservices are about modular design and decoupling units of code from each other.
Yes, but you’re failing to understand that the bottleneck that’s fixed by peeling off microservices is the human one faced by project managers. In fact, being forced to pay the microservices tax can and often does add performance penalties.
The problem with this approach is that switching from vertical to horizontal is extremely hard if you didn’t plan for it from the start.
I think you’re missing the point that more often than not ain’t going to need it.
In the rare cases you do, microservices is not a magic wand that fixes problems. The system requires far more architectural changes that go well beyond getting a process to run somewhere else.
Someone in the thread mentioned that to get the benefits of micro services in a monolith, you can use a linting rule to prevent dependencies across modules
Share data, not state.
In Rust this is a pretty good use-case for channels, which can be used to send messages across threads.
Someone in the thread mentioned that to get the benefits of micro services in a monolith, you can use a linting rule to prevent dependencies across modules
I don’t think that makes any sense. The main benefit of microservices is organizational, more specifically how a single team gets to own all aspects of developing, managing, and operating a service.
Lower in priority, there’s enabling regional deployments and improved reliability.
How are linting rules even expected to pull that off?
Should have explained my viewpoint. Most startups should not do micro services.
Using linting to prevent coupling between modules can give you some of the benefits of micro services without going all in.
Using linting to prevent coupling between modules can give you some of the benefits of micro services without going all in.
My point was that modularizing an application and decoupling components does not, by any mean, give any of the benefits of microservices.
The benefits of microservices are organizational and operational independence. Where do you see coupling between components to play a role in any of these traits?
Microservices are a reflection of Conway’s law. You can bend it with multiple services masquerading as a monolith. But you can’t break it and when you need to decouple deployments, data releases, and development across a fairly large org: they’re hard to beat. Of course OP is right, just call them services too. One per team is about as much as you want to break out, don’t go micro
There is no standard tooling for microservices-based development - there is no common framework
DAPR gets you most of the way there.
orchestrating units is a very joyful experience though. Doesn’t matter if those are actual (micro-)services on dedicated servers or just pure functions.
And if you write pure functions (stateless, no sideeffects, work only on the data you get via parameters), the step to make it scalable is super tiny.
Unfortunately most people’s code is not modular enough to be a good fit for microservices, and attempting to do microservices like that ends up in pain. That if you mentioned is a pretty big if.
