Npgsql.FSharp VS FSharp.SystemTextJson

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

Likewise, it looks like it'll be a while before FSharp.SystemTextJson has Swagger integration too.

You can customize it with with https://github.com/Tarmil/FSharp.SystemTextJson

Let's move on to the Json requests. In F# Json Serialization/Deserialization is an interesting topic because we're used so much to use things like Option, Result, Discriminated Unions and other F# specific constructs that sometimes they don't translate well to plain json or from plain json and that's why often F# libraries leave the that aspect out of scope to other libraries like Thoth.Json or FSharp.SystemTextJson. For now we'll fall back to the BCL and use the System.Text.Json namespace since we are only using primitive types in our model