Age of Ascent

Thought I'd share the Alpha test announcement. I've enjoyed following Ben Adams for years and watching the progress on AoA and their contributions/insight to .NET Core performance. https://twitter.com/ben_a_adams https://www.ageofascent.com/2020/06/23/technical-progress-with-age-of-…

Why not? The latest techempower results show ASP.NET Core saturating a 10GbE network card with 7M+ req/sec while being a full-featured framework, compared to custom C++ web servers. [1] The memory management, type safety, and high-level productivity make it great for building load balancers and other infrastructure components. 1. https://www.ageofascent.com/2019/02/04/asp-net-core-saturating-10gbe-a…

C# is great. It's a high level programming language and it's also super-fast handling ~7.000.000 requests per second on a single server according to the following benchmark: https://www.ageofascent.com/2019/02/04/asp-net-core-saturating-10gbe-a…

Not saying its easy and we have discovered the reason most MMOs have long wind up animations for actions... The other layers (chat, non-space game state) are handled by discrete microservices on other connections to other hosts - to keep the space flight data slim and connection dedicated in use. Can always give it a try, our next public playtest is on Saturday 6 Feb 8pm GMT/UK | 12pm Pacific | 3pm Eastern US at http://www.ageofascent.com/ Just don't try it on a phone; give us a chance with the latency ;-)

It's hard for blanket statements not to raise hackles, I think you highlight a real trend but it feels a little broad of a statement to me (the joys of distilling opinions into text). The first language I learned was Python and then I got a job in a .NET shop and I've been .NET since, to declare my bias. But I'm not dyed-in-the-wool Microsoft stack, I think Postgres is better than SQL Server for almost every use case (though SQL Server is superior to Oracle or MySQL for most others), that something like Rust is better for embedded or systems programming, that if you need cross-platform UI you're better off using something outside the Microsoft stack and that it makes a lot more sense to host a .NET web app on a Linux server and I have no interest in Azure, or indeed any cloud vendor's properitary tools. I think there exists a trend, as in Oracle shops or IBM shops, for some large/corporate companies to tie in to a tech stack and consider, for example, Sharepoint or CRM or SAP, to be the solution to everything. I think this has less to do with individual developers and more to do with sales pressure. A lot of developers just code for a job, they have no interest in it outside of it being a tool to work with and since .NET is (in the studies I've seen) within the top 3 techs by number of jobs in most of the Anglosphere it tends to be overrepresented in corporate environments where development is 'just a job'. But there are also many companies using whatever tool is best for…

I'm a .NET developer with 5 years of experience, mostly in the enterprise space. I've worked on large projects with .NET 3.5 - 4.7, and recently I've been building things in .NET core. Honestly, .NET core makes a lot of sense for new projects that need to be highly scalable. If you have an API service that's hosted in a cloud provider, or a tool that generates PDFs of items, or a tool that scrapes API data and chucks it in a database, then this is great. These are simple applications that do not need an awful lot of authentication, crazy UI frameworks, or other windows-only features. The code itself runs faster [1]. It might not matter for business / CRUD applications, but that's a nice to have thing. The biggest selling point is cross platform support. Now, I don't care if the company switches from Windows 2016 VM's to some variation of RHEL. My code will work on that too. This gives your organization improved flexibility and reduced technical debt. If you have a big legacy application using .NET Framework, it's probably not worth rewriting it for .NET Core. You will run into package conflicts. I have had to rewrite ".NET Framework only" pacakges to support .NET Core. That will throw your estimates off and probably delay the project. And that becomes really difficult to justify to project stakeholders. [1]: https://www.ageofascent.com/2019/02/04/asp-net-core-saturating-10gbe-a…

I'll just leave this here https://www.ageofascent.com/2019/02/04/asp-net-core-saturating-10gbe-a…

Even if connections per second can be a magnitude or two lower than requests per second this result is still quite off by today's alternative. 14 core machine comparing .net core with other top webservers: https://www.ageofascent.com/2019/02/04/asp-net-core-saturating-10gbe-a…

https://www.ageofascent.com/2019/02/04/asp-net-core-saturating-10gbe-a… That actix you see appearing in most lists and mostly nearly top is written in Rust btw. Fun fact- frameworks managed by microsoft dominate the space ;)

this is absolutely not a function of Azure vs AWS, the perf diff is completely between .Net Framework (which was used on Azure) and .Net Core (which was used on AWS). This compares Apples and Watermelons. https://www.ageofascent.com/2016/02/18/asp-net-core-exeeds-1-15-millio… http://codinggorilla.domemtech.com/?p=1499

“On Azure I’m using .NET 4.6 on the v1 runtime while on AWS I’m using the same code running under .NET Core 1.0.“ .NET Core has way less baggage than .NET 4.6 [1] so you’d be expecting AWS to come out ahead. It looks like Azure functions supports .NET Core now [2]. (Edit: just noticed the author is aware of this [3].) Of course it might also be Blob storage having higher latency than S3. Having used Azure Functions before I agree with the article’s criticisms about scaling. [1] https://www.ageofascent.com/2016/02/18/asp-net-core-exeeds-1-15-millio… Mind this article is talking about comparing ASP.NET with ASP.NET Core, and .NET with .NET Core, not just .NET Core’s performance. [2] https://github.com/Azure/Azure-Functions/issues/98 [3] https://www.azurefromthetrenches.com/azure-functions-v2-preview-perfor…

I struggle to understand, from a practical standpoint, where it comes from. The performance of ASP.Net is becoming outright ludicrous[1]. I've personally rewritten a lot of C++/CLR to C# and we've seen performance gains over 20% each time. C# is a language that hasn't gone stagnant, regular iterations on the language are made to meet real-world demands. Now that the OS is no longer an issue, why isn't C# seeing more startup usage? Just look what StackOverflow does with it.[2] Startups shouldn't be judging developers for knowing it, they should be looking at it themselves. [1]: http://www.ageofascent.com/asp-net-core-exeeds-1-15-million-requests-1… [2]: http://highscalability.com/blog/2014/7/21/stackoverflow-update-560m-pa…

We plan on moving to it sometime this year, from "old" dotnet. The timings is unclear because it depends on a few factors both on our side and from Microsoft/the community. For example we are on trend of using Entity Framework less in favor of dapper, so when the bits we are still using are fully supported by entity framework core that block will be cleared. Other big dependencies like a posgresql driver are already ready to go IMO. Tooling still isn't 100% ready in visual studio 2017 with web deployment being a key problem. My advice would be to only use it now if you are starting from scratch and you have no business goals in the next 6 months (you are building an MVP and can take the hit of some random bugs in production). I know that at least one startup is using it for critical services, but they are also committed to fixing the dotnet core source code when they run into a problem and I believe are part of the reason for the good pref of kestrel (new web server), I think unless you are willing to do that you should wait a bit longer. https://www.ageofascent.com/category/asp-net-core/