Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Presentations What Comes after Microservices?

What Comes after Microservices?



Matt Ranney talks about the limits that some companies have encountered in their large microservices deployments and some non-microservices approaches to those same problems. He also talks about the non-microservices systems that Uber is building to maintain developer productivity with a large and growing engineering team.


Matt Ranney is Chief Systems Architect at Uber, where he's helping build and scale everything he can. Previously, Ranney was a founder and CTO of Voxer, probably the largest and busiest deployment of Node.js.

About the conference

Software is changing the world. QCon empowers software development by facilitating the spread of knowledge and innovation in the developer community. A practitioner-driven conference, QCon is designed for technical team leads, architects, engineering directors, and project managers who influence innovation in their teams.

Recorded at:

Dec 13, 2016

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Business capabilities vs componentization

    by Dragan Stepanović,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Correct me if I'm wrong but, from his speech around the problems they're facing primarily with maintainability and extensibility, it seems that they didn't implement microservices around business capabilities but rather towards technical componentization and thus they have bunch of services to change (and teams to communicate with) when they need to change or add a new business feature.
    Also, the part that where he's talking about User service and changing and evolving it's schema, it definitely looks like that there are different business forces applied to the schema of a single service and that's exactly the problem that typical layered architecture faces and why microservices was originally proposed as one of the options towards better solution.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p