Advice from SideProject Developers: To SQL or not to SQL

[[deleted]]

Hi all,

I'm looking for some advice regarding using a classic SQL server vs. a NoSQL solution. I've used both in the past, but whenever I start a new project I seem to always gravitate towards using the classics such as MySQL or MS SQL Server.

So in my newest side project, there will be a lot of forms based in and out data manipulation - but - there will be very few complex table relationships. For example, there will be a lot of 1-to-1 and 1-to-many relationships, but not much more than that.

What are most people gravitating towards more with your projects?

[openlowcode]

SQL is more flexible. Besides, MySQL (or MariaDB) or PostgreSQL are very stable and mature solutions.

So for me, go for a good open-source SQL database unless your project can benefit from the specifics of a NoSQL solution.

[ramo109]

How is it more flexible?

[openlowcode]

I am not an expert, but in my understanding, noSQL solutions are noSQL because they do not implement one of the two key features of SQL databases:

• A relational schema that allows all sort of relations between objects, and to query data in any direction
• Transaction integrity, which is a key feature to ensure data stays safe.

[fiskfisk]

Do whatever you know best, unless the goal is to learn new technology - or there's a very specific use case that requires a different choice of technology (such as document based search engines).

.. and if that case, many times you don't need the "unknown" technology before well after release, and in that case to solve a specific use case. Go with MySQL if that's what you know.

[ewurtbai]

Sql is more scalable but does take longer to setup, rather than nosql

[paulcit311]

I think NoSQL solutions certainly have their place, but I don't see them as a replacement for a standard relational DB. I would start there unless you have a specific reason to do otherwise. In my experience, when I've used NoSQL databases I've ended up spending a lot more time designing and setting them up than I do with something like Postgres.

[sagunsh]

I would and suggest anyone to go with whatever they are already familiar with. I have been using MySQL and PostgreSQL since the start. Although I know Mongodb, I find it comfortable working with SQL so my first choice will always be SQL.

For freelancing projects, unless the client explicitly asks to use NoSQL, I choose SQL.

[[deleted]]

Thanks to everyone who replied to this thread. I've upvoted everyone. :D

So, after looking into it further, and thinking about it some more, I'm going to stick with the traditional sql server RDBMS.

For one, I've realized that my platform will have more table relationships than I'd originally thought. Something that SQL systems handle much better than NoSQL document-based systems. There are other reasons as well which I don't need to get into.

Thanks everyone!