#MEAN vs #LAMP – How Do They Stack Up? via @backand_ #Linux #NodeJS #mysq #Mongodb…
- In the MEAN stack, the web server – provided by Apache in LAMP – is provided by Node.js.
- The MEAN stack replaces LAMP’s use of MySQL (or another relational database) with MongoDB (or an equivalent non-relational database).
- MEAN makes use of Express.js and AngularJS to drive web page presentation and control flow, tasks covered by PHP or Python in the LAMP stack.
- While the MEAN stack is designed to work with a non-relational database, there are plug-ins for Node.js that allow the stack to run off of a relational database just as easily.
- Converting to the MEAN stack gives your development team a number of benefits, the three most significant being a single language from top to bottom, flexibility in deployment platform, and enhanced speed in data retrieval.
Comparing the venerable LAMP (Linux, Apache, MySQL, PHP/Python) stack with the up & coming MEAN stack (MongoDB, Express, AngularJS, NodeJS)
@K0YCHEV: #MEAN vs #LAMP – How Do They Stack Up? via @backand_ #Linux #NodeJS #mysq #Mongodb…
The first choice in any tech stack is the operating system. While the LAMP stack locked the operating system to a variant of Linux, the MEAN stack has no such restrictions. Linux is still a good choice for an app built on MEAN, but it is by no means the only option; any operating system that can run Node.js is a viable alternative.
In the MEAN stack, the web server – provided by Apache in LAMP – is provided by Node.js. This can improve the performance of the application, as Node.js is entirely non-blocking and event-based, allowing for true concurrency among requests. Node.js is lightweight and relatively new, however, which ultimately means that your organization will be largely on its own when it comes to non-standard extensions. While there is active plug-in development for Node.js, the technology is not as matured as Apache. This usually means that you need to write your own plug-ins to cover the areas where…