Building the Great Wall: API Driven Applications
summary
Argues for an API‑driven architecture that decouples client and server, shows a progression from tiny JSON endpoints to reusable abstractions and presenters, and gives concrete tools: Sinatra, Rails, Sprout core, Backbone. Claims the 98% case is CRUD so helpers save repetition, then uses presenters, Memcached and JSON templates to vary representations and caching. Notes tradeoffs: Sprout core is opinionated and changing, Backbone is low‑level and powerful, approach helps scaling when those problems exist.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 7:19Start Small
- 13:54The Client
- 14:05ClientSide MVC
- 15:28DogsController
- 16:38Pros and Cons
- 17:47Backbone
- 18:53Collection
- 19:49Pros Cons
related talks
23mIntegrating Web Apps
41mAPPLICATION ARCHITECTURE: BOUNDARIES, OBJECT ROLES, & PATTERNS
42mWeb API's with ERLANG a Ruby Dev's POV
42mBuilding Better Web APIs with Rails
28mSplitting Your App
30mAPI Design Matters
43mThe Clean Architecture: How to Grow From Startup to Enterprise
35mBuilding Ambitious APIs with Ruby