Rails APIs: The Next Generation
summary
Procore runs a ten‑year Rails monolith with ~700 staff, ~120 engineers, 22 squads and 500+ controllers and builds a single public API by enforcing style guides and API contracts (JSON), adding support levels alpha / beta / production, and shipping reusable pieces: a filterable gem for uniform filtering, ActiveModel::Serializer extensions for named views, Swagger/OpenAPI docs linted and rendered by a Ruby AWS Lambda pipeline, and parallel front‑end/back‑end workflow that proves the approach works.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:31autonomy
- 4:34why invest in an api?
- 7:08what makes a good api?
- 8:37how did we do it?
- 10:35don't make them think
- 11:06have a style guide
- 12:21boilerplate & examples
- 15:59use reusable components
- 18:13serialization
- 22:15documenting the api
- 25:59writing swagger at procore
related talks
26mKeeping the Rails Magic Alive After 18 Years
34mIndustrial Rails
01h 03mRuby at Scale
28mBringing Your Rails Monolith Along As The Business Grows
51mRails Core AMA
32m2000 engineers, 2 millions lines of code: the history of a Rails monolith
42mHow Rails fosters a diverse and competitive tech ecosystem in the era of big tech
26mMonolith-ifying perfectly good microservices