What do you think?
Rate this book
Write Modern Web Apps with the Mean Stack: Mongo, Express, Angularjs, and Node.Js
Traditionally, web applications have been architected so that the back-end houses all the front-end code. This has resulted in heavy projects that are difficult to manage and scale. This book will explain a new way to write web applications by treating the front-end as if it were a third-party (such as a mobile client). This book, written by a practicing MEAN developer, will take a holistic approach to using the MEAN JavaScript platform for creating modern web applications and lay out how to use the MEAN (Mongo, Express, AngularJS, and Node.js) set of tools to create a web application, from installation and setup of the tools to debugging and deploying your app. After an introduction to how web development is changing and the advantages of using the MEAN stack, the author jumps into an introduction to each tool and then dives into using the complete JavaScript-based application stack to build, test, and deploy apps.
256 pages, Kindle Edition
First published September 17, 2014
1 person is currently reading
29 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 of 1 review
January 3, 2016
A hands-on and concise 'learn MEAN stack' book. I never worked with anything on the MEAN stack before (although I did some JS and web development with other stacks), and this feels the right difficulty level for me. The book's approach go like this: it explains conceptually about the MEAN stack and why it is a good choice, then proceeded to build a working 'social networking' app from the ground up, then proceeded to implementing various types of testing, and then deployment first to PaaS (heroku) and then to a cloud infrastructure (Digital Ocean).
What I think could be better is to add a bit more explanation about the choices the author make in the code. For example, he rolled his own authentication system there, and several chapters were dedicated to building this. Is this the recommended approach, or is it just a good exercise to help learning and in production we should do something else? Towards the end of the book he put more "Note" inserts that explain stuff like this, but I found these explanation lacking in the beginning of the book.
Overall, a very good book and I recommend this for people learning the stack.
What I think could be better is to add a bit more explanation about the choices the author make in the code. For example, he rolled his own authentication system there, and several chapters were dedicated to building this. Is this the recommended approach, or is it just a good exercise to help learning and in production we should do something else? Towards the end of the book he put more "Note" inserts that explain stuff like this, but I found these explanation lacking in the beginning of the book.
Overall, a very good book and I recommend this for people learning the stack.
Displaying 1 of 1 review