MongoDB MEAN Stack Webinar October 7, 2015
2 likes•604 views
The document discusses building a REST API using Node.js and MongoDB. It covers creating schemas for products, categories, and users using Mongoose. It also discusses building out routes for retrieving, adding, and removing data. Testing the API is covered using Mocha and Superagent to make HTTP requests. Schema design principles like embedding related data are also summarized.
![*
•Queries in MongoDB should be simple
•Strive for minimal data transformation by server
•“Store what you query for”
•“If you need [the aggregation framework in a heavily
used API endpoint], you're screwed anyway, and should
fix your program.” - Linus Torvalds
•Good for performance and developer sanity](https://image.slidesharecdn.com/meanstackwebinar20151007-151007165630-lva1-app6891/85/MongoDB-MEAN-Stack-Webinar-October-7-2015-21-320.jpg)
MongoDB MEAN Stack Webinar October 7, 2015
- 1. Valeri Karpov Node.js Engineer, MongoDB www.thecodebarbarian.com github.com/vkarpov15 @code_barbarian
- 2. * •MongoDB is great for storing web/mobile app data •So let’s build a REST API using Node.js! •+ learn a bit about test-driven dev with Node.js •+ learn two MongoDB schema design principles •Server-side only - just JSON, no HTML •No AngularJS part, focus more on MongoDB •Upcoming EdX course
- 3. * •Part 1: Shopping Cart Application • Search for products • Add them to your cart • Check out with Stripe •Part 2: Using the Mongoose ODM •Part 3: Schema Design •Part 4: Building an API with the Express framework •Part 5: Testing with Mocha + Superagent
- 4. *
- 5. *
- 6. *
- 7. * •"Bad programmers worry about the code. Good programmers worry about data structures and their relationships." - Linus Torvalds •3 schemas for 3 collections: •Products •Categories •Users
- 8. * •Product belongs to one or more categories •Users can have multiple products in their cart •Representing relationships in MongoDB is tricky •But that’s what mongoose is for
- 9. * •“Object document mapper” (like ORM, but for MongoDB) •“MongoDB object modeling designed to work in an asynchronous environment” •Written for Node.js •Provides schema validation, pseudo-JOINs, etc.
- 11. * Register event handler In node.js, you don’t execute I/O imperatively. You register a callback to execute when the I/O is done Prints before “done reading”
- 13. * Create User Save user to MongoDB Load user from MongoDB Print user to stdout
- 14. * •Mongoose provides several neat features • Model part of MVC • Default values • Schema validation and declarative schema design
- 15. * •3 schemas: • Product • Category • User •Going to use mongoose to define schemas •Will use a couple key schema design principles
- 16. *
- 17. *
- 18. *
- 19. * •What categories are descendants of “Electronics”? • • •What categories are children of “Non-Fiction”? • •What categories are ancestors of “Phones”?
- 20. *
- 21. * •Queries in MongoDB should be simple •Strive for minimal data transformation by server •“Store what you query for” •“If you need [the aggregation framework in a heavily used API endpoint], you're screwed anyway, and should fix your program.” - Linus Torvalds •Good for performance and developer sanity
- 22. * User’s cart as an array of ObjectIds...
- 23. * •Product and user = many-to-many relationship •Don’t necessarily need a mapping table •User won’t have 1000s of products in cart •Can represent relationship as array in user since one side is small •If one side of many-to-many is bounded and/or small, it is a good candidate for embedding •Arrays that grow without bound are an antipattern! • 16mb document size limit • network overhead
- 24. * •Most popular Node.js web framework •Simple, pluggable, and fast •Great tool for building REST APIs
- 26. * •Representational State Transfer •HTTP request -> JSON HTTP response •Business logic on top of MongoDB schemas • Access control, emails, analytics, etc.
- 27. *
- 29. *
- 30. *
- 31. * •Recall cart is an array of products
- 32. * Get cart from HTTP request Overwrite user’s cart Let mongoose handle casting and validating data
- 33. * •Mongoose lets you be lazy •Access control using subdocs
- 34. * Create a Stripe charge with the npm ‘stripe’ module
- 35. * Error handling Empty user cart on success
- 36. * •Express REST API on top of mongoose • Access control • Business logic • Define what operations user can take on database •Mongoose casting and validation for APIs
- 37. * •Building an API is tricky •Lots of different error conditions •Express has a lot of magic under the hood
- 38. * •Node.js runs in an event loop •Single threaded •Can run client and server on same thread! • Client sends HTTP request • Client registers a callback awaiting the result • Server’s “on HTTP request” event handler is triggered • Server sends response, continues waiting for events • Client’s callback gets fired •Test server end-to-end
- 39. * •NodeJS HTTP client •Isomorphic: runs in both browser and NodeJS •Same author as Express
- 40. * •Testing Framework for NodeJS •Same author as Express •BDD-style syntax • describe() -> test suite • it() -> individual test
- 41. *
- 42. *
- 43. * •NodeJS concurrency makes testing easy •Not just unit tests - full E2E for your REST API •Can manipulate database and make arbitrary HTTP requests
- 44. * •Upcoming EdX Video Course •Slides on http://www.slideshare.net/vkarpov15 •Looking for beta testers! Sign up for notifications • http://goo.gl/forms/0ckaJ4YvJN •Interested in learning about AngularJS? • Professional AngularJS on Amazon •More NodeJS+MongoDB content at: • www.thecodebarbarian.com • Twitter: @code_barbarian