Need advice about which tool to choose?Ask the StackShare community!
ASP.NET vs Play: 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, Play is detailed as "The High Velocity Web Framework For Java and Scala". Play Framework makes it easy to build web applications with Java & Scala. Play is based on a lightweight, stateless, web-friendly architecture. Built on Akka, Play provides predictable and minimal resource consumption (CPU, memory, threads) for highly-scalable applications.
ASP.NET and Play can be primarily classified as "Frameworks (Full Stack)" tools.
Play is an open source tool with 11.2K GitHub stars and 3.77K GitHub forks. Here's a link to Play's open source repository on GitHub.
Coursera, Zalando, and Keen are some of the popular companies that use Play, whereas ASP.NET is used by Performance Assessment Network (PAN), Making Waves, and Jitbit. Play has a broader approval, being mentioned in 112 company stacks & 47 developers stacks; compared to ASP.NET, which is listed in 76 company stacks and 76 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 mvc6
Pros of Play
- Scala78
- Built on akka55
- Web-friendly architecture55
- Stateless50
- High-scalable47
- Fast46
- Open source39
- Java34
- High velocity27
- Fun24
- Lightweight9
- Non-blocking io8
- Developer friendly5
- Simple template engine5
- Scalability4
- Pure love3
- Resource efficient2
Sign up to add or upvote prosMake informed product decisions
Cons of ASP.NET
Cons of Play
- Evolves fast, keep up with releases3
Sign up to add or upvote consMake informed product decisions
What is ASP.NET?
What is Play?
Need advice about which tool to choose?Ask the StackShare community!
What companies use ASP.NET?
What companies use Play?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Play?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+12