Doing Data as a Frontend Developer
summary
Front-end developers get DBA-level patterns: browser storage (sessionStorage, localStorage, IndexedDB) for client state, and cloud DBs running inside VPCs with ALBs, subnets and AZs for shared state. Relational systems give ACID transactions and normalization; non-relational systems trade that for partitionable scale (one example cites 75,000 servers at the largest deployment). NewSQL (AWS Aurora, Fauna using the Calvin protocol) and hybrid stacks with in-memory cache plus search engine are practical solutions; data infrastructure matters more than picking a single database.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:13The Database
- 7:39Structured Language
- 9:41Normalization
- 12:04Limitations
- 12:54Built for Scale
- 13:30Unstructured
- 13:47Partitionable
- 20:39Tribalism Bad
related talks
08mWhen Worlds Collide: Frontend vs Database
52mData storage for modern applications - Mike Lehan
40mBeyond Relational: Data storage for modern applications
59mModernize your applications with purpose-built databases
23mState in a stateless world: data serving in the cloud
34mData Storage: NoSQL Toasters and a Cloud of Kitchen Sinks
41mDo you really need that relational DB?
24mBuild modern applications with purpose-built AWS databases