Building mobile APIs with services at Yelp
summary
Yelp moves from a single monolith (yelp-main) to 70+ production services over three years, trading long two‑hour, manual pushes and tangled homegrown abstractions for independently deployable services. The mobile backend is an aggregator with one endpoint per app page, supports multi‑version APIs so old clients keep working, and uses acceptance tests in Docker (docker‑compose) plus monitoring and alerts. Stack specifics: Pyramid SQLAlchemy uWSGI with Swagger/Bravado for API specs; the approach reduces push contention and proves reliable in production.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:50Yelp: a brief history lesson • founded in 2004
- 10:40Why Not Services?
- 11:22How to make sure it doesn't break
- 13:43Setting up acceptance testing
- 17:29The Biz App service
- 19:42Developing a mobile app backend mobile apps have releases in our case, they're synchronized, both in time and in features
- 21:41Multi-version API maintaining multiple versions can become costly adding fields is backwards compatible
related talks
30mGraphQL APIs: REST in Peace
33mArrested Development
26mBuilding Scalable Microservice APIs From The Beginning
45mService Mesh Security: Shifting Focus to the Application Layer
43mBreak Up the Monolith: Testing Microservices
48mTransforming a monolith to an API platform
21mThe great SOA migration
38mFrom Monolith to Microservices at Zalando