NoSQL, No Server, No problem: Using ORM's in Javascript Applications
summary
Demo builds a small Twitter clone using MongoDB, Breeze.js and Knockout and then swaps the backend to LocalStorage. Breeze brings full client-side entities, caches everything in memory, and needs only three API endpoints: get data, save data, get metadata. Examples include a sign-survey app built in three days, handling 4.2 million proof-of-play rows, and an offline record of three and a half months, showing background save, batching and validation.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:08What is ORM
- 2:35Why use ORMs
- 4:20Choosing an ORM
- 6:32Bookshelf
- 7:00Breeze
- 9:36Breeze Features
- 13:30Breeze Integrations
- 18:06Change Tracking Notification
- 18:46Model Validation
- 20:58No Server Setup
- 25:32ORM Separation
- 26:10Documentation
related talks
34mThe Road to Hype: How NoSQL became Serverless
30mGive your Data the Respect it Deserves
27mMaking Relational Cool Again (or: JavaScript on ACID)
45mThe Future of Data in Ember
18mFrom SQL to NOSQL - a gentle intro for Devs
28mBuilding in Rails, Backbone, and CoffeeScript
34mGet Your Head Out of the Cloud — Embracing Local-First Apps with Nuxt
41mDo you really need that relational DB?