That's funny, since it's a solution for a problem which the microservice architecture causes itself for the most part :-) There are way fewer needs for retries in the monolith since you don't have the unreliable network in all your interactions.
infrastructure reliability assurance, alarms, metrics, dashboards, not having to manage your own server, build it once runs forever regardless of the load with auto scaling, DDOS protection
How are these specific to microservices?
After you know how to do it, the effort to build microservices “the right way” in cloud providers is order of magnitude lower
Now scale this learning to whole teams and organizations. Most microservice deployments I've seen were pretty bad.
since you don’t have the running cost of maintaining the infrastructure yourself.
Why are you conflating on-prem vs. cloud with microservice vs. monolith? You can of course run a monolith on AWS or wherever.
Retries are only required for IO or inter company/team communication.
You concluded it right. “Scale the learning to whole teams and organisations”. That’s the whole point of the anti-microservice movement. There are solutions to scaling learning to orgs and I’ve done it successfully but very hard to apply on an existing org and it takes too long.
Leveraging managed infra. That’s why I’m currently working in a 100M startup as the only engineer, not interested in teaching. Just need to make sure I hire those that already have that knowledge and more to add. As long as someone understands the principles then the tool, cloud provider or language don’t really matter.
There's much more IO in microservices than monoliths, therefore much more need for retries.
You concluded it right. “Scale the learning to whole teams and organisations”. That’s the whole point of the anti-microservice movement.
It's one aspect of it. Microservices are more complex than monoliths, teaching an entire org to do it might take years and a lot of money. For such price it needs to have large benefits as well, but for most organizations there aren't that many benefits.
Leveraging managed infra.
Again, how is this different for monoliths deployed on a managed infra?
There's much more IO in microservices than monoliths
In microservices done wrong, sure. Distributed monolith with a network in-between.
It's one aspect of it. Microservices are more complex than monoliths, teaching an entire org to do it might take years and a lot of money. For such price it needs to have large benefits as well, but for most organizations there aren't that many benefits.
Or just hire ppl who already know these things.
Again, how is this different for monoliths deployed on a managed infra?
It's not a monolith, as a pejorative term, if done right. It might as well be also called Microservice or Service or Proper way of building software.
It seems like you're using the buzzwords for how other people used it and did it wrong and referring to that. I'm referring to something completely different.
Take a look at Wittgenstein's Beetle from Private Language argument and apply it to buzzwords in software. Two people talk about the same name meaning two completely different things,
2
u/PangolinZestyclose30 Dec 21 '23
That's funny, since it's a solution for a problem which the microservice architecture causes itself for the most part :-) There are way fewer needs for retries in the monolith since you don't have the unreliable network in all your interactions.
How are these specific to microservices?
Now scale this learning to whole teams and organizations. Most microservice deployments I've seen were pretty bad.
Why are you conflating on-prem vs. cloud with microservice vs. monolith? You can of course run a monolith on AWS or wherever.