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

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - archite
Post a Comment
Read more

Risk Register

A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir
Post a Comment
Read more

Lessons learned from sprint retrospective meeting

Scenario: Team Missed Sprint Goals Challenge: A development team consistently missed its sprint goals, leading to frustration and a drop in morale. Team members felt overwhelmed by the workload and struggled to communicate effectively. Retrospective Insights: During the retrospective, team members openly discussed their challenges and frustrations. They identified bottlenecks in communication, unclear priorities, and unrealistic expectations. The team realized that individual workloads were not evenly distributed, causing burnout for some members. Lessons Learned: Effective Communication Matters: The team recognized the importance of clear communication. They committed to regular stand-up meetings, where everyone shared progress, blockers, and priorities. Balancing Workloads: The retrospective highlighted the need to distribute tasks more evenly. They decided to monitor workloads and adjust assignments accordingly. Setting Realistic Goals: The team acknowledged that setting achievable
Post a Comment
Read more