What are the differences between each databases solutions?
Thomas Bnt
Dec 15 '18
γ»1 min read
For a project that requires a lot of requests to a database, which one would be the best, and what are the differences between them?
Classic DEV Post from Jan 3
72
8
Improving the way of saving posts on Dev.to while writing.
Mohammad Aziz - Feb 18
What Do You Think About Types?
Miklos Bertalan - Feb 18
Who's looking for open source contributors? (Feb 18th edition)
Ben Halpern - Feb 18
Last night my side project made one person happy, and someone else pissed off
Chris Dermody - Feb 18
Auth With Twitter
Auth With GitHub
Databases are designed to handle "a lot of requests". Your data model is the most important determinant of what database to use, not your throughput, and if you don't have any reasons not to stick with a relational database, the answer is probably Postgres. If your needs diverge from the relational model, this is a good starting point for your research into NoSQL offerings.
I guess it depends what a lot means.
I would err on the side of not overthinking this. Most mainstream databases are pretty damn good at what they do.
Weβve been more than happy with PostgreSQL.
As the others have mentioned, you'll be safe picking any of the four big relational databases (Oracle, MySQL, MS SQL, PostgreSQL). It's worth noting that, if you've really picked the wrong one, it's relatively easy to switch. With NoSQL, this is a bit harder as even with similar database models, there's often no shared query language.