Storage.Net VS Npgsql

There is/was a good project for that - https://github.com/aloneguid/storage, they have interface and wrappers for Azure, S3, Filesystem (good for local dev) and in-memory (good for unit testing) and you can plug any provider you want.

There is a similar library https://github.com/aloneguid/storage that also abstracts working with filesystem and some other cloud services.

What is the difference between this https://github.com/aloneguid/storage and yours?

In theory this improves over time. .NET 8 will be the first "real" release of NativeAOT. I would expect the big ms libs to start playing nice after .net 8 comes out. Some big non-ms libs are already doing this, like npgsql. That is their issue for size reduction, many work items already done.

And yet again, I got pleasantly surprised. Npgsql - the recommended ADO.NET and Entity Framework (Core) provider - makes the adoption of PostgreSQL an almost seamless experience. Additionally, the Npgsql provider implements those PostgreSQL language elements, which are not present in the Microsoft SQL Server world. Let me mention here at least support for the ILIKE operator, as well as a range of functions related to the PostgreSQL's LTree data type.

You can just use the database driver directly, I would start with their documentation. Here's the one for postgres https://www.npgsql.org/

Probably SQL Server since they are both made by Microsoft. But I'd recommend PostgreSQL. Completely free and open source and the integration is fantastic. https://github.com/npgsql/npgsql

edit: https://www.npgsql.org

Npgsql as this issue.

As briefly touched on earlier, the primary outcome of your making a choice between PostgreSQL and MySQL is that the choice determines how you will interact with the database. This means that using the MySQL-compatible version of Aurora requires the use of the MySql.EntityFrameworkCore NuGet packages, while connecting to the PostgreSQL-compatible edition requires the Npgsql and Npgsql.EntityFrameworkCore.PostgreSQL packages, just like they were used earlier in those posts in this series. If you are considering using Babelfish with the PostgreSQL-compatible, then you would use the standard SQL Server NuGet packages as we worked with in the last few posts.

As with any database product that you will access from your .NET application, its level of support for .NET is important. Fortunately for us, there is a large community involved in helping ensure that PostgreSQL is relevant to .NET users. Let’s look at what you need to do to get .NET and PostgreSQL working together. The first thing you need to do is to include the necessary NuGet packages, Npgsql and Npgsql.EntityFrameworkCore.PostgreSQL as shown in Figure 1.