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

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...

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 .