Need advice about which tool to choose?Ask the StackShare community!
.NET Core vs MEAN: What are the differences?
## Introduction
In this comparison, we will explore the key differences between .NET Core and MEAN stack.
1. **Architecture**: .NET Core is a cross-platform, open-source framework provided by Microsoft for building modern, cloud-based, internet-connected applications, while MEAN stack is a collection of JavaScript technologies used for developing web applications.
2. **Technology Stack**: .NET Core primarily uses C# as its programming language and provides a set of libraries and tools for development, whereas MEAN stack consists of MongoDB (database), Express.js (web framework), Angular (front-end framework) and Node.js (runtime environment).
3. **Community Support**: .NET Core has a strong community support from Microsoft and the developer community, with regular updates and improvements, whereas MEAN stack has a more diverse community support due to its open-source nature but might lack the same level of support as .NET Core.
4. **Scalability**: .NET Core is known for its scalability and performance optimization features, making it suitable for enterprise-level applications, while MEAN stack can also be used for scalable applications but may require additional effort in optimization.
5. **Deployment and Hosting**: .NET Core applications can be deployed on various platforms including Windows, Linux, and macOS, with support from Microsoft Azure and other cloud services, whereas MEAN stack applications are typically deployed on cloud platforms like AWS, Heroku, or Google Cloud Platform.
6. **Learning Curve**: .NET Core might have a steeper learning curve for developers unfamiliar with C# and the .NET ecosystem, whereas MEAN stack, being a collection of JavaScript technologies, is more accessible to developers with JavaScript experience.
In Summary, .NET Core and MEAN stack differ in their architecture, technology stack, community support, scalability, deployment options, and learning curve.
I was researching multiple high performance, concurent//parallel languages for the needs of authentication and authorization server, to be built on microservice architecture and Linux OS. Node.js with its asynchronous behavior and event loop suits the case best. Python Django & Flash turns to be slower and .NET Core & Framework wasn't the best choice for the Linux environment at the time (summer 2018).
I also tested Go lang and Rust, although they didn't meet the quick prototyping criteria as both languages are young and lacking libraries or battle-tested ORM.
There has been a lot of buzz around having PostgreSQL for ASP.NET Core 3.1 web apps. But Configuring Identity Server 4 with PostgreSQL is a real challenge. I've made a simple video to configure the ASP.NET Core 3.1 based Web application that uses AngualrJS as front end with Single Page App capabilities with Identity Server 4 talking to the PostgreSQL database. Check out this Video tutorial on how to do that in detail http://bit.ly/2EkotL5 You can access the entire code here on github http://bit.ly/35okpFj
Pros of .NET Core
- Perfect to do any backend ( and a fast frontend) stuff30
- Fast27
- Cross-platform26
- Great performance25
- It promotes better codebase architectures and organizat18
- All Platform (Mac, Linux, Windows)18
- Very fast development with templates11
Pros of MEAN
- Javascript86
- Easy62
- Nosql58
- Great community52
- Mongoose50
- Modularity50
- Open source48
- Organized37
- Simple32
- Boilerplate31
- AngularJs10
- CLI9
- It's simply awesome9
- Cutting edge tech8
- Passport7
- It's a great new exciting stack6
- Yeoman6
- Docs6
- Friendly & Fun5
- Great Flexibility ;)4
- The WordPress of javascript apps4
- Genius3
- Modular2
- Scalable2
- JavaScript only2
- Growing Community1
- It's fun and has great potential1
- Gulp1
- Because i can write everything using javascript1
- Fast1
- The best0