Cloud

528 readers

1 users here now

This community was created to share news, hold discussions, insights, and knowledge sharing about cloud computing and different cloud services like AWS, Google Cloud, Azure, and many others.

Read our rules here

founded 1 year ago

MODERATORS

snowe

nibblebit

lysdexic

Death by a thousand microservices (renegadeotter.com)

submitted 1 year ago by lysdexic to c/loud

4 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] lysdexic 1 points 1 year ago (1 children)

But they obviously don’t understand the whole complexity ahead of the project start, so making nuanced decisions is not possible. They’d have to arbitrarily pick an architecture sizing in between.

The single most important decision is external interfaces, and establish service level agreements with clients.

Once the external interface is set, managers have total control over what happens internally. If they choose to, they can repeatedly move back and forth peeling out and merging in microservices. That's actually one of the main selling points of microservices: once an API gateway is in place, they are completely free to work independently on independent services and even their replacements.

Microservices are first and foremost an organizational tool.

[–] [email protected] 1 points 1 year ago

Hmm, not sure, I fully understand your point.
Yes, having those API gateways in place gives you flexibility in organization, but they cost developer velocity and therefore also money.

So, if you won't need the flexibility of those API gateways, then you shouldn't build/maintain them. But that is obviously easier said thsn predicted, which is why misjudgements happen...