I personally go the nodejs way, the asynchronous way, but that's because I need raw metal level performance. The event based programming model of nodejs is hard to get right, dealing with concurrent activities is probably harder than it is already with threads.
PostgreSQL comes preinstalled with Erbix. I hence assume that it is fair to call Erbix an SQL JavaScript platform.
However, according to the FAQ, "transactions" are not supported yet, this is puzzling, how is synchronization handled?
I saw no mention of Comet either.
So, I do like the idea but the lack of Comet and SQL transactions seriously limit the range of addressable applications.
If I were Erbix, I would brand this "alpha" rather than "beta" and implement Comet & SQL transaction before going to "beta" stage.
However there is value in the "release early, release often" motto, so maybe I am wrong or maybe I missed something and synchronization issues are dealt with in some magical way?