What type of database should i Use?

Might look into a NoSQL solution like MongoDB or CouchDB. They let you store documents in Json. CouchDB is pretty easy to get started with.

MySQL & Postgres are both great choices, any relational database will work well. I would not recommend someone new to databases use a NoSQL database. CouchDB (and MongoDB) solve some very particular problems, such as for a website that has 5 million daily views.

Here's an interesting take on the pro's and con's of scalability of NoSQL vs relational databases.

First learn SQL and the relational paradigm.

SQL represents 40 years of experience designing general data stores that work for the widest set of applications. SQL databases solve many very hard problems which you are probably not aware of.

If you jump into NoSQL first you will be implementing SQL features in your application code, and doing a shitty job of it because you have experience with data stores that actually solve these problems well.

The reason for the existence of so many NoSQL databases is the rise of web applications and the need to scale massively. However the majority of apps will never need to scale beyond a single well-tuned database server anyway. By the time they do you will have had problems to solve regardless of what data store you used.

The advantage of SQL is that it's a fantastic hedge on the evolution of your data usage patterns because it is designed to support ad-hoc queries well, and the schema prevents bad application code from trusting your data into chaos at the first occurrence of a small bug.

Realistically if you knew you had to build an app for 5 million daily users, and you knew exactly what it was going to do, then an SQL database very well might be the wrong choice.

But in the real world you have a long road ahead before you hit that scale, and you'll have real data to determine what kind of alternate data stores can best handle your load. Personally I'm a huge fan of redis, and its ability to scrape bottlenecks off a MySQL database in a piecemeal fashion.

Source: https://news.ycombinator.com/item?id=1636551

I agree James, SQL is great for a lot of things. I suggested a possible NoSQL solution because it is simpler to learn how to send a Json POST or PUT to a server than it is to learn an entire new language like SQL.

Also, from my experience administering CouchDB and Redis is a lot simpler than administering MySQL and PostgreSQL. Just because NoSQL databases can scale to millions doesn't mean they have to ;-).

Heh, just read the first comment in the link you shared:

NoSQL isn't just about scale. Sometimes, modeling data relationally is a real bitch, and a document store makes more sense.

That's pretty much my thought when considering the database needs for an application. SQL is good though, I don't mean to hate ;-).

Party On!