from Hacker News

Ask HN: Database Recommendations for Asp.net Core API

by BeeFriedman on 6/18/24, 11:03 PM with 5 comments

• by MissTake on 6/18/24, 11:11 PM

  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…

• by neonsunset on 6/19/24, 12:14 AM

  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.

• by wild_egg on 6/18/24, 11:16 PM

  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