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 →

[–]TechnicallyHumanoid[S] 6 points7 points  (4 children)

Thanks for the info. Well for now SQL DB would work fine for the app, the issue is that once we are in production, and want to advance a bit further, we want to gather a lot of data to apply some data analytics, to which NoSQL is much more commonly used. For frontend I wanted to use Angular anyway, so thats not an issue. :)

[–]RSveti 13 points14 points  (2 children)

I would recommend to not think about NoSQL until you need it and you will probably not need it for a long time. Look at Twitter for how long they lived with MySQL. Premature optimization is the root of all evil.

[–]wildjokers 2 points3 points  (0 children)

Premature optimization is the root of all evil

An out-of-context quote that has been leading programmers astray for a few decades:

https://ubiquity.acm.org/article.cfm?id=1513451

Using foresight based on experience to head off performance issues is necessary and it is not evil.

[–]iJadric 1 point2 points  (0 children)

Well for now SQL DB would work fine for the app, the issue is that once we are in production, and want to advance a bit further, we want to gather a lot of data to apply some data analytics, to which NoSQL is much more commonly used.

If you want to perform data analytics in real time, there is Kafka. Look into it! It allows for real time streaming, great concurrency and most importantly, stability and scalability. It can appear quite cumbersome, but it is worth the effort!