Reading this, I can’t help but feel that things have got more complicated than perhaps they need to be. Microservices boundaries make most sense to me when they’re aligned with team boundaries, otherwise it just feels like making more work with little or no apparent gain.
> Microservices boundaries make most sense to me when they’re aligned with team boundaries, otherwise it just feels like making more work with little or no apparent gain.
Nothing in the article suggests how services were designed, and I would be surprised if each of the core services mentioned in the article weren't managed by independent teams.
Also, I don't think your concerns are well founded. Think about functionality implemented with function-as-a-service backends. Do you think your architecture is less complex to maintain and operate if you suddenly decide to move all event handlers into a monolith?
Are you going to rebuild your micro service every time there's a reorg?
It's nice as a SWE to own a specific service, but I think it leads to suboptimal tech stacks and adds latency.
In a redundant system, MTTR rapidly starts to be the dominating factor for high availability.
These guys seem to have the right approach.
Anyone else getting access denied on the page?
You must be in Russia? Just switch on VPN.