The Road to Hype: How NoSQL became Serverless
summary
CouchDB adopts JSON over HTTP, embeds SpiderMonkey to run JavaScript MapReduce and exposes per-document URLs so replication and global sync work out of the box; the CouchApps idea ships server-side JS and static apps but fails because the compile/deploy loop kills developer ergonomics and funding never follows. Mustache → Handlebars spawns client templating, NPM originates as a CouchApp, Hoodie packages offline-first features but loses ground to Parse/Firebase; tooling wins too: semantic-release and greenkeeper automate multi-package maintenance.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:18What Data Representation Will You Choose for Getting Data in and out of Your Database
- 6:51How To Query Your Data
- 8:21Introduction to Mapreduce
- 15:48Developer Ergonomics
- 25:41The Funding Cycle
related talks
30mWriting apps on the edge with CouchDB
55mCouchDB to the Edge
35mNoSQL, No Server, No problem: Using ORM's in Javascript Applications
29mThe Front-end Takeover
45mNoSQL: Death to Relational Databases
27mnode.js + CouchDB == Crazy Delicious
34mData Storage: NoSQL Toasters and a Cloud of Kitchen Sinks
01h 02mNext Generation Data Storage with CouchDB
