Npgsql.FSharp VS awesome-fsharp

When working with F#, my database layer code has always seemed ugly. It feels like functional languages don't pair well with storage. I've used F# with Dapper, EF, and Npgsql.FSharp. Although Npgsql.FSharp works well, I would still like to use something like EF since it handles inserts and updates so well.

Not a big fan of ORMs in general, I've been using https://github.com/Zaid-Ajaj/Npgsql.FSharp for postgres.

On Postgres, there's a decent low ceremony option by Zaid Ajaj: https://github.com/Zaid-Ajaj/Npgsql.FSharp

For database, I use PostgreSQL with https://github.com/Zaid-Ajaj/Npgsql.FSharp and I like it very much. Writing the services, I do hide database operations behind interfaces like

Npgsql.FSharp

2. https://github.com/fsprojects/awesome-fsharp#data-science

I found this list of resources and libraries for F# which should get you started if you're looking for a specific library, like one for Postgres.

Yeah, it's not the most mainstream programming language, but despite that there are some interesting F# projects.

I'd suggest having a look through https://github.com/fsprojects/awesome-fsharp and look at the high starred items (though some are not strictly F# but just something F# can use)

maybe something like suave (backend web framework).

The bigger problem I found going down the F# route is F# libraries go dead. For long term projects, far better not to use any thirdpary F# libraries and just use pretty popular third party .net libs from the C# world or the core .net lib. These days I mostly just use C#. The advantages of F# are not that big compared to just writing C# with a similar coding mindset.