using the MEAN.js Technology Stack
|Select a content section anchor button and then use the Browser’s back button to return to selections|
The MEAN Stack is an acronym coined in a Blog post by a Team Lead to “Affectionately” refer to his team’s Technology Stack choice.
The Current MEAN.js Components as of this post:
- MongoDB: version 3.0.4
- Express Node Web Server: version 0.12.7
- AngularJS: version 1.4.3
- Node.js: version 0.12.7
MEAN.js is less opinionated than MEAN.io and is more of a Boilerplate Scaffolding Framework than a Highly Opinionated Platform.
MEAN.js is less strict on the “Rules of Usage” and allows the Developers to replace chosen Technologies, if desired.
MEAN.io, in their own works, tries to “Protect” the developers by creating a platform that is more restrictive.
It was this philosophy that predicated the split from the original MEAN.io and created MEAN.js.
As of this writing MEAN.js is the
most popular MEAN Stack on GitHub
The World of ‘Open Source’ Communities
While you could certainly create a MEAN stack using the “Do It Yourself” concept but the question that would be begging to be asked is:
A dedicated and committed team of skilled Open Source Developers have already done the heavy lifting for Stack Coding, the Debug process, Best Practices Implementation and Automated Testing Suites for Client and Server code.
Your Application would have these Advantages:
A Much Faster Time to Market
A Lower Cost of Maintenance
Reduced Training Costs
A Built-in Mobile First Architecture
A Much Higher Quality of Delivered Code
A Higher Productivity Level of all the Development Team Members
The benefits of leveraging a well support
framework outweighs the DIY concept
A Single Language for all of the Technology
Stack Layers reduces Development Resource
Costs by Consolidating required Skill Sets
that translate to all aspects of the
designed Business Solution
Wisdom Pearl # 121 – Work Quality Concept
Your Work is Only as Good
… As How it is Perceived by the Next Person who Touches It
Positive Acceptance of your Work is Your Preeminent Responsibility
The following two tabs change content below.
I am a Principal Architect at Liquid Hub in the Philadelphia area specializing in Agile Practices as a Certified Scrum Master (CSM). I use Test Driven Development (TDD) and Acceptance Test Driven Development (ATDD) with Behavior Driven Development (BDD) as my bridge to Agile User Stories Acceptance Criteria in a Domain Driven Design (DDD) implementing true RESTful services