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

Setting up the base application

In previous chapters, we used our own boilerplate to bootstrap the application's development. This chapter is going to have a fresh folder structure, but don't worry; we are still going to use a lot of code from the existing boilerplate.

A new folder structure will give us more flexibility, as at the moment we have outgrown our initial architecture. One benefit, which we are not going to cover in this chapter, is that you can move each module to a separate package and install them as dependencies.

Before jumping into things, let's see a high-level view of our architecture:

-- admin/
-- api/
-- auth/
-- frontstore/
-- shared/
---- helpers/
---- middlewares
---- models
---- services
---- environments/
---- strategies

The explanation for the folder structure is as follows:

  • apps: This folder will contain several micro apps, such as frontstore, which will serve as the client application for users visiting our e-commerce store.

  • core: This...