> I'm quite curious who this is aimed at. .NET shops are often so deeply invested in the Microsoft ecosystem.

The cloud (even Microsoft's Azure) has changed this somewhat, and continues to do so.

I work as a architect for companies in the enterprise world, and most businesses are now much more open to using Linux and non-Microsoft systems. I recently finished a project for a Microsoft shop, using Postgres, RabbitMQ, Linux and dotnet Core, and this is no longer unusual for me. This current situation was utterly unimaginable before the cloud - I love finally having the freedom to choose something because it's a good fit, rather than being forced to use something "because policy".

Furthermore, dotnet is not purely for Microsoft shops any more - dotnet Core helped change that. Personally, I use dotnet Core for all my side projects, and it works great on Linux.

> I recently finished a project for a Microsoft shop, using Postgres, RabbitMQ, Linux and dotnet Core.

Hm, I see - that sounds like they're already very far on the journey out of the Microsoft ecosystem.

I personally haven't seen a company like that, only ones heading further into "1st party Azure services" lock-in.

All of this was deployed in the Azure. I could perhaps have been clearer - all the enterprises I've worked at in recent times have been happy to deploy non-Microsoft services, but only when those services are deployed to the cloud. As far as on-prem goes, they exclusively stick with Microsoft (and sometimes Oracle).

There is a growing number of ".NET shops" nowadays that are using non-MS open-source infrastructure. You don't hear much about it because the .NET community has always been culturally less exhibitionist than others. So much so that there are still tons of people out there who don't know that .NET runs on Linux, and has done for quite a number of years now.

These days, being able to leverage Azure helps... Of course, you can also just as easily use Azure SQL, and for that matter, the dockerized version of SQL Server is really useful for development.

Getting to the point we have a couple projects targetting kubernetes... one for hosting/deployment and testing, one only for testing, and another getting there for testing. Our apps have various differing configurations for various client deployments, so being able to spin up and test with different client configurations for applications is helpful.

Once at that point, introducing something new, such as a redis instance for connection throttling/tracking, or using Postgres locally/remotely for our app databases (service hosted for prod, k8s temporary instances for testing/dev), or spinning up rabbitmq even, or leveraging azure storage queues.

Of course we've also been writing more in node, and less in C# for some things. Getting away from all things C# has been hard in a historically .Net shop though.

> .NET shops are often so deeply invested in the Microsoft ecosystem

Nobody likes MS's SQL License fees, however.

If you're going all cloud, then you can't get away with using unlicensed/insufficiently licensed RDS instances.

The delta between Postgres an SQL Server instance pricing per hour doesn't take much to add up to a salary for a mid range DBA.

> The delta between Postgres an SQL Server instance pricing per hour doesn't take much to add up to a salary for a mid range DBA.

I agree with you, leadership didn't shrug. Keeping to as few technologies as possible is a more pricey, but also more conservative choice.

No kidding. I remember back in the .NET 4.5 days and SQL Server was per-socket pricing while Oracle and whatnot were per-core. It was an amazing deal.

Then SQL Server went per-core and our pricing went up 8-fold.

Been using PostgreSQL ever since.

SQLs socket/core pricing is a pain.

We wanted some instances, had to get our hosting provider to dig up previous generation CPU machines so we could have a lower core count. They were like "We'll give you the extra cores for free", Until we explained that it was for SQL License reasons.