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

Auction backend

In the previous chapter, we added a service layer to our architecture. We are going to follow the same pattern. Also, we are going to add an extra component called Mediator, which will serve as a single point of entry to assist us in communicating with different modules.

We will follow the mediator design pattern in the construction of our modules, which is a behavioral design pattern. This is going to be a single central point of control, through which communication flows.

The Mediator

Our Mediator is going to be an object that will coordinate interaction with different modules through channels. A module can subscribe to a given event and get notified when that event occurs. All this event-related discussion pretty much makes us think about using the events core module from Node.js, which is used to emit named events that cause execution of the functions to be called.

This is a good starting point. One thing we need to solve is that our Mediator needs to be a single point of...