Lyft Oct 27, 2020

Decomposing network calls on the Lyft mobile apps

Article Summary

Lyft's mobile apps used to poll a single endpoint every 5 seconds for everything. That "Universal Object" became their biggest reliability nightmare.

Don Yu and the Lyft engineering team share how they decomposed one monolithic API into 40+ microservice endpoints. This year-long migration involved 13+ engineers and fundamentally changed how their mobile apps fetch data.

Key Takeaways

Critical Insight

Lyft eliminated their single point of failure by splitting one universal endpoint into isolated APIs, cutting latency by 40% and improving driver notification speed by over 20%.

The article reveals why decomposing network calls isn't always the right choice, and when a monolithic polling loop might actually make sense for your app.

Recent from Lyft

Related Articles