Book Image

MEAN Blueprints

By : Robert Onodi
Book Image

MEAN Blueprints

By: Robert Onodi

Overview of this book

The MEAN stack is a combination of the most popular web development frameworks available—MongoDB, Angular, Express, and Node.js used together to offer a powerful and comprehensive full stack web development solution. It is the modern day web dev alternative to the old LAMP stack. It works by allowing AngularJS to handle the front end, and selecting Mongo, Express, and Node to handle the back-end development, which makes increasing sense to forward-thinking web developers. The MEAN stack is great if you want to prototype complex web applications. This book will enable you to build a better foundation for your AngularJS apps. Each chapter covers a complete, single, advanced end-to-end project. You’ll learn how to build complex real-life applications with the MEAN stack and few more advanced projects. You will become familiar with WebSockets and build real-time web applications, as well as create auto-destructing entities. Later, we will combine server-side rendering techniques with a single page application approach. You’ll build a fun project and see how to work with monetary data in Mongo. You will also find out how to a build real-time e-commerce application. By the end of this book, you will be a lot more confident in developing real-time, complex web applications using the MEAN stack.
Table of Contents (13 chapters)
MEAN Blueprints
About the Author
About the Reviewer

The message history data model

The message history will be a collection of user-submitted messages through the chat application. We can choose from a number of approaches when storing such data in MongoDB. The good thing is that there is no correct implementation, although we have a number of common approaches and considerations for each implementation.

Our starting point will be that messages sent by users are part of a conversation thread. When two or more users chat with each other, initially a conversation thread is created for them. The messages become private for that conversation. This means that the messages have a parent-child relationship with another entity, a thread entity in our case.

Keeping in mind our application's requirements, we can explore the following implementations to store our messages:

  • Store each message in a separate document: This is the easiest to implement and it's the most flexible one, but it comes with some application-level complexity.

  • Embed all messages...