Skip to main content

MERN stack

The MERN stack is a collection of technologies that developers use to build web applications using JavaScript.

The acronym MERN stands for MongoDB, Express, React, and Node.js. The MERN stack is a full-stack solution that uses JavaScript and JSON to create a three-tier architecture. It's popular because it only requires one programming language, JavaScript.


Each component plays a specific role in the architecture of a MERN application.

MongoDB:

MongoDB is a NoSQL database that is used to store data in a document-oriented format. This makes it ideal for storing JSON data, which is the native format of JavaScript objects.

Express:

Express is a web framework that is used to build the backend of a MERN application. It provides a number of features that make it easy to develop and deploy web applications, such as routing, middleware, and templating.

React:

React is a JavaScript library that is used to build the frontend of a MERN application. It provides a number of features that make it easy to build user interfaces, such as components, state management, and virtual DOM.

Node.js:

Node.js is a JavaScript runtime environment that is used to run the MERN application. It provides a number of features that make it ideal for developing web applications, such as event-driven programming, non-blocking I/O, and a large number of modules.


The MERN stack follows a three-tier architecture, which is a common pattern for designing web applications. The three tiers are:

Presentation tier:

The presentation tier is responsible for displaying the user interface of the application. It is typically implemented using a JavaScript library such as React.

Application tier:

The application tier is responsible for handling the business logic of the application. It is typically implemented using a web framework such as Express.

Data tier:

The data tier is responsible for storing and retrieving data. It is typically implemented using a database such as MongoDB.


Here are some of the benefits of using the MERN stack:

  • use JavaScript for both the frontend and backend of the applications
  • scalable
  • build a wide variety of web applications


Comments

Post a Comment

Popular posts from this blog

New way of product development

Today is the era of fast-paced world and competitive world. Companies are realizing that the old sequential approach to developing new products won’t get the job done and product can’t be reached to market when compared to competitors. The 4 stages of product development are as follows – R&D, Growth, Maturation, and Decline. Instead of sequential approach, companies are using holistic approach – as in rugby game, the ball gets passed within the team as it moves as a unit up the field. This holistic approach has six characteristics: 1)     Build-in-instability 2)   Self-organizing project teams 3)   Overlapping development phases 4)   Multi-learning 5)   Subtle (very clear and strong) control 6)   Organizational change to explore and learning The above six characteristics forming a fast and flexible process for new product development with advantage of act as a change agent, creative, market driven ideas, flexi...
Post a Comment
Read more

Product Manager vs Product Owner

Both the product manager and the product owner work towards a common goal, to build and improve products that create meaningful value for customers and all stakeholders within the company. This usually happens by delivering and optimizing product features. Product Manager Product Owner The product manager discovers what users need, prioritizes what to build next, and rallies the team around a product roadmap. The product owner is responsible for maximizing the value of the product by creating and managing the product backlog. This person creates user stories for the development team and communicates the voice of the customer in the Scrum process.      Product Manager and Product Owner's work on below vacuum. Product manager focus on: Business Strategy Long term Product Vision Long term Product Strategy Product Roadmap Alignment with Product Owner Product owner focus on: Release Plan (Product Backlog ie: ...
Post a Comment
Read more

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .
Post a Comment
Read more