Building your first MEAN application
summary
Focuses on MongoDB as the data engine in a MEAN stack and claims a JSON document model speeds prototyping and avoids heavyweight joins. Builds a working City of Toronto service-request dashboard with Angular + nvd3 directives, Node/Express REST routes and Mongoose ODM to save new requests; charts come from server-side queries using the aggregation pipeline. Covers sharding and replica sets for scale, shows the app is responsive, and warns to index fields that fit in RAM.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:13Why MongoDB?
- 3:48Terminology
- 6:56Document Data Model
- 8:02Documents are Rich Data Structures
- 10:47Document Model Benefits
- 12:07Performance
- 13:55Drivers & Ecosystem
- 14:35MEAN Stack
- 18:13Node.js MongoDB Driver
- 22:48Mongoose (getting started)
- 25:29Mongoose (example)
- 26:03Visualizing data
- 34:23Getting started with MEAN
- 36:26Scalability
- 37:36High Availability
- 39:13MongoDB Architecture
related talks
32mBuilding Next Generation Apps with Next.js and MongoDB
35mNoSQL, No Server, No problem: Using ORM's in Javascript Applications
01h 02mZero to Document Hero
28mServerless Angular, Material, Firebase and Google Cloud applications
59mA Practical Introduction to AngularJS
31mThe Year of the Cat
24mEngineering Complex Web-Apps using Angular and RequireJS
34mThe Road to Hype: How NoSQL became Serverless
