Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial


Use cases for SQL vs NoSQL dbs?

Does anyone have some basic resources as to when to use which?

1 Answer

NoSQL is going to be better for changing data needs/structures or high throughput, and is generally better if your project will pull individual objects out at a time.

SQL is ACID compliant, but requires a pretty rigid data structure; if your project has a lot of data that can be smoothly stored in tables, and you will be querying a lot (1k+) of records per request, SQL is probably a better bet.

In terms of resources, you could check out this link which will provide a fair amount of information on both; if the project is really important, you can always try using one then the other to see what suits your needs most elegantly.

Hope that helps!