One Team at Uber Is Moving From Microservices to Macroservices

One Team at Uber is Moving from Microservices to Macroservices

There may be an undiscovered tribe deep in some jungle somewhere that hasn’t made up their mind on microservices, but I doubt it. People love microservices or love to hate microservices. There’s not much in between.

So it means something when even a team at a company like Uber announces a change away from microservices to something else. What? Macroservices.

But we’ll get to that. Think what you want about Uber the company, but from a software perspective Uber has been a good citizen. Gergely Orosz, an Engineering Manager on the Payments Experience Platform at Uber, in a tweet signaled a change in architectural direction: Exactly b/c testing and maintaining thousands of microservices is not only hard – it can cause more trouble long-term than it solves the short-term.

Yes, we’re doing this and the approach touches on a pain point of many microservices. Every service needs to support tenancies, including many stateless ones. We also need to retrofit much of this work with the existing services.

For new services, we just add it from the start.