Need advice about which tool to choose?Ask the StackShare community!
ASP.NET vs Grails: What are the differences?
Developers describe ASP.NET as "An open source web framework for building modern web apps and services with .NET". .NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications. On the other hand, Grails is detailed as "An Open Source, full stack, web application framework for the JVM". Grails is a framework used to build web applications with the Groovy programming language. The core framework is very extensible and there are numerous plugins available that provide easy integration of add-on features.
ASP.NET and Grails can be categorized as "Frameworks (Full Stack)" tools.
Grails is an open source tool with 2.48K GitHub stars and 945 GitHub forks. Here's a link to Grails's open source repository on GitHub.
Performance Assessment Network (PAN), Making Waves, and Jitbit are some of the popular companies that use ASP.NET, whereas Grails is used by LinkedIn, PedidosYa, and MercadoLibre. ASP.NET has a broader approval, being mentioned in 76 company stacks & 76 developers stacks; compared to Grails, which is listed in 47 company stacks and 22 developer stacks.
When I started on this project as the sole developer, I was new to web development and I was looking at all of the web frameworks available for the job. I had some experience with Ruby on Rails and I had looked into .net for a bit, but when I found Laravel, it felt like the best framework for me to get the product to market. What made me choose Laravel was the easy to read documentation and active community. Rails had great documentation, but lacked some features built in that I wanted out of the box, while .net had a ton of video documentation tutorials, but nothing as straightforward as Laravels. So far, I am happy with the decision I made, and looking forward to the website release!
Comparing to ASP.NET Core MVC or ASP.NET Core Web API Simplify.Web allows you to easily build your web-site or REST API without any additional/complicated setup, covering cases like localization by default. It's projects structure very lightweight, just a minimum amount of what you need to setup ASP.NET Core request pipeline.
It is build on top of Simplify.DI IOC container abstraction, no dependency on Microsoft.Extensions.DependencyInjection and it's syntax. You can easily switch between DryIoc, SimpleInjector, CastleWindsor etc.
Any internal module of Simplify.Web can be easily replaced on extended by your custom module, covering your custom cases.
For HTML pages generation Simplify.Templates can be used allowing you to use just regular plain HTML without additional setup.
Can be easily integrated with Simplify.WindowsServices converting your web application not just to web-application, but a standalone windows service which can also do some background jobs via Simplify.WindowsServices.
And it is open source, of course :)
Pros of ASP.NET
- Great mvc21
- Easy to learn13
- C#6
Pros of Grails
- Groovy56
- Jvm40
- Rapid development38
- Gorm37
- Web framework30
- Open source25
- Plugins21
- Extensible17
- Easy17
- Dynamic14
- Clean architecture (Dependency Injection)6
- Gradle6
- Clear what everything does, lots of options5
- RAD4
- Agile4
- Great documentation4
- Android3
- Spring3
- Easy setup2
- Java web apps with steroid1
Sign up to add or upvote prosMake informed product decisions
Cons of ASP.NET
- Entity framework is very slow2
- C#1
- Not highly flexible for advance Developers1
Cons of Grails
- Frequent breaking changes3
- Undocumented features2
Sign up to add or upvote consMake informed product decisions
What is ASP.NET?
What is Grails?
Need advice about which tool to choose?Ask the StackShare community!
What companies use ASP.NET?
What companies use Grails?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Grails?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+12