Ask HN: Database Recommendations for Asp.net Core API

I am building an ASP.Net Core API. What database would you recommend?

I have experience with MySql, but I am wondering if MongoDB would maybe be easier..

5 comments

[ 2.5 ms ] story [ 20.8 ms ] thread

Not sure how you expect anyone to answer this as you have provided absolutely no information other than you plan to use .net.

What’s the purpose of the server? Who’s the audience? What will it be doing? What sort of volume will it expect?

One does not simply create an API server!

And there a lot more to it - I’m no expert but my recent foray into this involved a front end API server in the DMZ, and a backend handler (both running under Kubernetes), RabbitMq , Redis, Sql Server and Postgres.

Does this API server even need a database? If so, why?

Questions, questions, questions…

BeeFriedman 2y ago ↗

I totally agree that the answer would be easier to answer with more information, but I was just wanted some recommendations based on the little facts I was able to provide at this point in time..

wild_egg 2y ago ↗

When in doubt, just use postgres. It can handle everything you might want from either MySQL or MongoDB and take you to a scale where you can afford to pay someone to figure out a more appropriate stack for your needs

BeeFriedman 2y ago ↗

thanks! will look into it..

neonsunset 2y ago ↗

Seconding Postgres recommendation - it's just so difficult to go wrong with it. It's incredibly versatile and works very well in non-pure-RDBMS scenarios too as document store, querying JSON data in jsonb fields and as vector store with pgvector.