Whoa, gone for a little while and this thread blows up
@sp4ceman, I see your use case for nosql has been mainly on logging and that seems like an apt use case. Would you do something like save the data in sql and also as a document. The nosql database would then server your API. Do you think that would be plausible and a good use case?
@semaphore, youe use node for your app but what datastore are you using (a relational one I assume)? I see that there are many ORMs for node now. Which on are you using? How good is the intergration of the orm you are using? I'm sure it is non-blocking module...
Now, I'm by no means a nodejs expert and have many questions. One of which relates to the
blocking of the event loop. At the end of the article, they guy basically parses a raw response to JSON. There it seems he could easily block the event loop. So, it seems it is pretty easy to block things and there is a fine line in which you have to tred carefully.
So, am I correct in saying that it is OK to develop a site using Nodejs with say PostgreSQL if the app/site is not heavy on computation. That could be implemented with a MQ and some other language...
EDIT:
Also, that means you could/would replace any content only driven site with node (blogs, cms, portals)?