Alternatives to ASP.NET logo

Alternatives to ASP.NET

ASP.NET, ASP.NET Core, PHP, JavaScript, and Node.js are the most popular alternatives and competitors to ASP.NET.
13K
294
+ 1
0

What is ASP.NET and what are its top alternatives?

.NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications.
ASP.NET is a tool in the Frameworks (Full Stack) category of a tech stack.

ASP.NET alternatives & related posts

ASP.NET logo

ASP.NET

13K
294
0
13K
294
+ 1
0
An open source web framework for building modern web apps and services with .NET
    Be the first to leave a pro
    ASP.NET logo
    ASP.NET
    VS
    ASP.NET logo
    ASP.NET

    related ASP.NET posts

    Greg Neumann
    Greg Neumann
    Indie, Solo, Developer · | 6 upvotes · 70.4K views
    TypeScript
    TypeScript
    Vue.js
    Vue.js
    Electron
    Electron
    Quasar Framework
    Quasar Framework
    ASP.NET
    ASP.NET
    Xamarin Forms
    Xamarin Forms
    .NET Core
    .NET Core
    Xamarin
    Xamarin

    Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.

    This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!

    But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?

    I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.

    Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...

    See more
    ASP.NET
    ASP.NET
    Puppeteer
    Puppeteer
    vuex
    vuex
    ExpressJS
    ExpressJS
    React
    React
    Angular 2
    Angular 2
    Vue.js
    Vue.js
    Netlify
    Netlify
    Heroku
    Heroku
    #Seo
    #Heroku

    I found Heroku to be a great option to get ExpressJS up and running with very little hustle. The free tier is great, but I'd recommend to set up a cronjob to visit your site every few minutes so that the server stays awake. Netlify was the option to host the front-end because doing the server side rendering on #Heroku would have taken a little more time than I'd like to. For the moment pre-rendering the app with prerender-spa-plugin is enough to help with #seo. Puppeteer was my choice over other options because it made it easier to scrape websites made on ASP.NET which is what I needed in this case. And Vue.js is my top choice at the moment because it's really beginner friendly and it has a lot of the features I like about Angular 2 and React. vuex is a must in most of the app I build.

    See more
    ASP.NET Core logo

    ASP.NET Core

    65
    46
    0
    65
    46
    + 1
    0
    A cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux
      Be the first to leave a pro
      ASP.NET Core logo
      ASP.NET Core
      VS
      ASP.NET logo
      ASP.NET
      PHP logo

      PHP

      59.5K
      15.3K
      4.3K
      59.5K
      15.3K
      + 1
      4.3K
      A popular general-purpose scripting language that is especially suited to web development
      PHP logo
      PHP
      VS
      ASP.NET logo
      ASP.NET

      related PHP posts

      Nick Rockwell
      Nick Rockwell
      CTO at NY Times · | 27 upvotes · 329.6K views
      atThe New York TimesThe New York Times
      Apache HTTP Server
      Apache HTTP Server
      Kafka
      Kafka
      Node.js
      Node.js
      GraphQL
      GraphQL
      Apollo
      Apollo
      React
      React
      PHP
      PHP
      MySQL
      MySQL

      When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

      So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

      React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

      Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

      See more
      Ali Soueidan
      Ali Soueidan
      Creative Web Developer at Ali Soueidan · | 16 upvotes · 89.7K views
      npm
      npm
      Babel
      Babel
      PHP
      PHP
      Adobe Illustrator
      Adobe Illustrator
      Asana
      Asana
      ES6
      ES6
      GitHub
      GitHub
      Git
      Git
      JSON
      JSON
      Sass
      Sass
      Pug
      Pug
      JavaScript
      JavaScript
      vuex
      vuex
      Vue.js
      Vue.js

      Application and Data: Since my personal website ( https://alisoueidan.com ) is a SPA I've chosen to use Vue.js, as a framework to create it. After a short skeptical phase I immediately felt in love with the single file component concept! I also used vuex for state management, which makes working with several components, which are communicating with each other even more fun and convenient to use. Of course, using Vue requires using JavaScript as well, since it is the basis of it.

      For markup and style, I used Pug and Sass, since they’re the perfect match to me. I love the clean and strict syntax of both of them and even more that their structure is almost similar. Also, both of them come with an expanded functionality such as mixins, loops and so on related to their “siblings” (HTML and CSS). Both of them require nesting and prevent untidy code, which can be a huge advantage when working in teams. I used JSON to store data (since the data quantity on my website is moderate) – JSON works also good in combo with Pug, using for loops, based on the JSON Objects for example.

      To send my contact form I used PHP, since sending emails using PHP is still relatively convenient, simple and easy done.

      DevOps: Of course, I used Git to do my version management (which I even do in smaller projects like my website just have an additional backup of my code). On top of that I used GitHub since it now supports private repository for free accounts (which I am using for my own). I use Babel to use ES6 functionality such as arrow functions and so on, and still don’t losing cross browser compatibility.

      Side note: I used npm for package management. 🎉

      *Business Tools: * I use Asana to organize my project. This is a big advantage to me, even if I work alone, since “private” projects can get interrupted for some time. By using Asana I still know (even after month of not touching a project) what I’ve done, on which task I was at last working on and what still is to do. Working in Teams (for enterprise I’d take on Jira instead) of course Asana is a Tool which I really love to use as well. All the graphics on my website are SVG which I have created with Adobe Illustrator and adjusted within the SVG code or by using JavaScript or CSS (SASS).

      See more

      related JavaScript posts

      Nick Parsons
      Nick Parsons
      Director of Developer Marketing at Stream · | 33 upvotes · 223.6K views
      atStreamStream
      Go
      Go
      Stream
      Stream
      Python
      Python
      Yarn
      Yarn
      Babel
      Babel
      Node.js
      Node.js
      ES6
      ES6
      JavaScript
      JavaScript
      #Languages
      #FrameworksFullStack

      Winds 2.0 is an open source Podcast/RSS reader developed by Stream with a core goal to enable a wide range of developers to contribute.

      We chose JavaScript because nearly every developer knows or can, at the very least, read JavaScript. With ES6 and Node.js v10.x.x, it’s become a very capable language. Async/Await is powerful and easy to use (Async/Await vs Promises). Babel allows us to experiment with next-generation JavaScript (features that are not in the official JavaScript spec yet). Yarn allows us to consistently install packages quickly (and is filled with tons of new tricks)

      We’re using JavaScript for everything – both front and backend. Most of our team is experienced with Go and Python, so Node was not an obvious choice for this app.

      Sure... there will be haters who refuse to acknowledge that there is anything remotely positive about JavaScript (there are even rants on Hacker News about Node.js); however, without writing completely in JavaScript, we would not have seen the results we did.

      #FrameworksFullStack #Languages

      See more
      Yshay Yaacobi
      Yshay Yaacobi
      Software Engineer · | 27 upvotes · 280.1K views
      atSolutoSoluto
      Docker Swarm
      Docker Swarm
      Kubernetes
      Kubernetes
      Visual Studio Code
      Visual Studio Code
      Go
      Go
      TypeScript
      TypeScript
      JavaScript
      JavaScript
      C#
      C#
      F#
      F#
      .NET
      .NET

      Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

      Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

      After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

      See more
      Node.js logo

      Node.js

      29.9K
      23.8K
      7.9K
      29.9K
      23.8K
      + 1
      7.9K
      A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
      Node.js logo
      Node.js
      VS
      ASP.NET logo
      ASP.NET

      related Node.js posts

      Nick Parsons
      Nick Parsons
      Director of Developer Marketing at Stream · | 33 upvotes · 223.6K views
      atStreamStream
      Go
      Go
      Stream
      Stream
      Python
      Python
      Yarn
      Yarn
      Babel
      Babel
      Node.js
      Node.js
      ES6
      ES6
      JavaScript
      JavaScript
      #Languages
      #FrameworksFullStack

      Winds 2.0 is an open source Podcast/RSS reader developed by Stream with a core goal to enable a wide range of developers to contribute.

      We chose JavaScript because nearly every developer knows or can, at the very least, read JavaScript. With ES6 and Node.js v10.x.x, it’s become a very capable language. Async/Await is powerful and easy to use (Async/Await vs Promises). Babel allows us to experiment with next-generation JavaScript (features that are not in the official JavaScript spec yet). Yarn allows us to consistently install packages quickly (and is filled with tons of new tricks)

      We’re using JavaScript for everything – both front and backend. Most of our team is experienced with Go and Python, so Node was not an obvious choice for this app.

      Sure... there will be haters who refuse to acknowledge that there is anything remotely positive about JavaScript (there are even rants on Hacker News about Node.js); however, without writing completely in JavaScript, we would not have seen the results we did.

      #FrameworksFullStack #Languages

      See more
      Nick Rockwell
      Nick Rockwell
      CTO at NY Times · | 27 upvotes · 329.6K views
      atThe New York TimesThe New York Times
      Apache HTTP Server
      Apache HTTP Server
      Kafka
      Kafka
      Node.js
      Node.js
      GraphQL
      GraphQL
      Apollo
      Apollo
      React
      React
      PHP
      PHP
      MySQL
      MySQL

      When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

      So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

      React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

      Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

      See more
      Python logo

      Python

      29.3K
      22.5K
      5.9K
      29.3K
      22.5K
      + 1
      5.9K
      A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
      Python logo
      Python
      VS
      ASP.NET logo
      ASP.NET

      related Python posts

      Nick Parsons
      Nick Parsons
      Director of Developer Marketing at Stream · | 33 upvotes · 223.6K views
      atStreamStream
      Go
      Go
      Stream
      Stream
      Python
      Python
      Yarn
      Yarn
      Babel
      Babel
      Node.js
      Node.js
      ES6
      ES6
      JavaScript
      JavaScript
      #Languages
      #FrameworksFullStack

      Winds 2.0 is an open source Podcast/RSS reader developed by Stream with a core goal to enable a wide range of developers to contribute.

      We chose JavaScript because nearly every developer knows or can, at the very least, read JavaScript. With ES6 and Node.js v10.x.x, it’s become a very capable language. Async/Await is powerful and easy to use (Async/Await vs Promises). Babel allows us to experiment with next-generation JavaScript (features that are not in the official JavaScript spec yet). Yarn allows us to consistently install packages quickly (and is filled with tons of new tricks)

      We’re using JavaScript for everything – both front and backend. Most of our team is experienced with Go and Python, so Node was not an obvious choice for this app.

      Sure... there will be haters who refuse to acknowledge that there is anything remotely positive about JavaScript (there are even rants on Hacker News about Node.js); however, without writing completely in JavaScript, we would not have seen the results we did.

      #FrameworksFullStack #Languages

      See more
      Jeyabalaji Subramanian
      Jeyabalaji Subramanian
      CTO at FundsCorner · | 24 upvotes · 284.8K views
      atFundsCornerFundsCorner
      Zappa
      Zappa
      AWS Lambda
      AWS Lambda
      SQLAlchemy
      SQLAlchemy
      Python
      Python
      Amazon SQS
      Amazon SQS
      Node.js
      Node.js
      MongoDB Stitch
      MongoDB Stitch
      PostgreSQL
      PostgreSQL
      MongoDB
      MongoDB

      Recently we were looking at a few robust and cost-effective ways of replicating the data that resides in our production MongoDB to a PostgreSQL database for data warehousing and business intelligence.

      We set ourselves the following criteria for the optimal tool that would do this job: - The data replication must be near real-time, yet it should NOT impact the production database - The data replication must be horizontally scalable (based on the load), asynchronous & crash-resilient

      Based on the above criteria, we selected the following tools to perform the end to end data replication:

      We chose MongoDB Stitch for picking up the changes in the source database. It is the serverless platform from MongoDB. One of the services offered by MongoDB Stitch is Stitch Triggers. Using stitch triggers, you can execute a serverless function (in Node.js) in real time in response to changes in the database. When there are a lot of database changes, Stitch automatically "feeds forward" these changes through an asynchronous queue.

      We chose Amazon SQS as the pipe / message backbone for communicating the changes from MongoDB to our own replication service. Interestingly enough, MongoDB stitch offers integration with AWS services.

      In the Node.js function, we wrote minimal functionality to communicate the database changes (insert / update / delete / replace) to Amazon SQS.

      Next we wrote a minimal micro-service in Python to listen to the message events on SQS, pickup the data payload & mirror the DB changes on to the target Data warehouse. We implemented source data to target data translation by modelling target table structures through SQLAlchemy . We deployed this micro-service as AWS Lambda with Zappa. With Zappa, deploying your services as event-driven & horizontally scalable Lambda service is dumb-easy.

      In the end, we got to implement a highly scalable near realtime Change Data Replication service that "works" and deployed to production in a matter of few days!

      See more
      Java logo

      Java

      27.4K
      16.9K
      3.2K
      27.4K
      16.9K
      + 1
      3.2K
      A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible