Become a MEAN Stack Developer

The MEAN stack is MongoDB, Express.js, AngularJS (or Angular), and Node.js. Because all components of the MEAN stack support programs written in JavaScript, MEAN applications can be written in one language for both server-side and client-side execution environments.

MEAN was coined by Valeri Karpov, a MongoDB developer. He introduced the term in a blog post.

The logo concept, initially created by Austin Anderson for the original MEAN stack LinkedIn group, is an assembly of the first letter of each component of the MEAN acronym.

The components of the MEAN stack are as follows:

MongoDB, a NoSQL database
Express.js, a web application framework that runs on Node.js
Angular.js or Angular, JavaScript MVC frameworks that run in browser JavaScript engines
Node.js, an execution environment for event-driven server-side and networking applications

Comments

Create Web API in Asp.Net Core MVC with Example

Introduction : Here we will learn how to create web api in asp.net core mvc with example or asp.net core mvc rest web api tutorial with example or asp.net core mvc restful api with example or implement web api using asp.net core with examples. By using asp.net core mvc web api templates we can easily implement restful web api services based on our requirements. To create web api first we need to create new project for that Open visual studio à Go to File menu à select New à Project like as shown below Now from web templates select Asp.Net Core Web Application ( .NET Core ) and give name ( CoreWebAPI ) to the project and click OK button like as shown below. Once we click OK button new template will open in that select Web API from Asp.Net Core templates like as shown below Our asp.net core web api project s...

.NET Core 2.0 Changes – 4 Key Things to Know

1. .NET Standard 2.0 Expanded APIs & the Ability to Reference Full Framework Libraries .NET Standard broadens the set of APIs available to include a lot of the missing features. It now supports 32,000+ APIs. It is now much easier to port your code to a .NET Standard library without major code changes. One of the biggest problems with .NET Core was the lack of third-party libraries. For example, when 1.0 came out, popular logging libraries like log4net were not even available (it is now). However, this was really only a problem if you wanted to deploy your app on Mac or Linux. You could have used .NET Core and targeted full .NET framework and not had these issues. .NET Standard 2.0 has added a new compatibility shim that will enable any .NET Core app to reference any full framework library. 2. Expanded OS Support One of the big goals with .NET Core is portability across multiple operating systems. Including desktops, servers, and even mobile. Microsoft ...

Think Next Generation Technologies

Search This Blog