#Looking for suggestions for db to use.

11 messages · Page 1 of 1 (latest)

trail plinth
#

200m records is not actually that big

#

doesn't really matter tbh

#

i would recommend a SQL over NoSQL database in general though, unless you meet the requirements and use cases of a NoSQL database

sullen lichen
#

Something like MySQL or Postgres probably

steel sand
#

I was working on a project that rely on postgres for over 500m. It was smooth but didn't had a chance to compare with other dbs

civic herald
#

If it's 200m records it really doens't matter. Postgres imo or Mongo if you qualify for the advantages of no sql

lapis echo
#

It's probably more about the rate of requests, kinds of requests, kind of data

cosmic loom
atomic grove
#

I've mostly used Mongo with my containerized clients running in a k8s cluster. That may be an "old habit" of mine, but it scales well and, as others have said, 200m records isn't something to be concerned with.

trail plinth
#

20k writes per second is actually reasonably high

#

what kind of data are we talking about here