this post was submitted on 06 Jul 2026
334 points (93.0% liked)
Technology
86131 readers
3269 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Scalability was the primary reason. An application running on physical Windows-based servers can't quickly scale up and down, leading to higher hosting costs due to everything scaled to maximum capacity at all times. Or, more often, leading to slow performance and lost revenue due to the customer not wanting to pay for maximum hosting capacity at all times. So the customers want scalable cloud hosting. And when losing a customer often means a loss of millions of dollars in revenue for my former employer, they want to keep those customers.
A secondary goal is increasing the speed of deployment for new customers. Scripting the entire environment - including servers, network, storage - can make it very fast to spin up a new customer or testing environment. That can be done without .NET, of course, but .NET Core is the obvious next step for a large distributed enterprise product suite that is (was) already running on .NET Framework.
.NET Core isn't a primary platform for desktop or mobile client applications. It is very common as a hosting platform; that is likely to continue.