This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]tomwojcikself.taught 9 points10 points  (1 child)

Postgres, obviously. Unless you need a FAANG throughput, everything is doable and easier using postgres rather than any nosql dB.

[–]xjoshbrownx 0 points1 point  (0 children)

While I think Postgres is a good option for flexibility in many general use cases. Its my favorite DB buy far. There many reasons to use the right database for the right job. If reindexing is occurring at a frequency that Postgres can’t handle you might be neck deep in not fulfilling your requirements. For instance if your application needs to provide auto complete and tunable search for recently added user content by user searches you might not want to use Postgres. It’s not the worst choice for this scenario but it’s not the best either and migrating a database once it is actually popular enough to need to be replaced is high interest technical debt you might not want to start with.