3 ms·
With the rise of realtime applications I'd argue that the situations for using NoSQL for the common project are growing. I think the author of the post has mad
by ppj606 12y ago
With the rise of realtime applications I'd argue that the situations for using NoSQL for the common project are growing.
I think the author of the post has made a good point, that many seem to forget - it is always a trade-off whichever tool you use.
- moe 12y agoWith the rise of realtime applications What does "realtime" have to do with the datastore?
- ppj606 12y agoThe usage and access of data in your data store when building a realtime application. If you were building a chat-app these days you are given a number of very easy to adopt (minimal complexity/edge cases) NoSQL solutions - Firebase, Parse, RethinkDB. Whereas with SQL you have the option of using cache layers (which you could say is NoSQL anyway), message queues, naive timely polling and log monitoring. With NoSQL the solutions are just simpler. For example Firebase has a tutorial for creating a real-time chat [1] - it takes 5 minutes. [1] https://www.firebase.com/tutorial/#example/chat https://www.firebase.com/tutorial/#example/chat