Hi Guarav, on question nr. 1 I know that ArangoDB has been pushing their .js abilities as a application server replacement but I would keep these roles separate. You should keep them separate mainly because you will, potentially, need more application nodes/instances than db nodes/instances.
The Asynchronous / non-blocking IO approach of NodeJS can be found elsewhere but is not fully supported by OrientDB yet (I think). Regardless of that, the SOA approach, the Actor Model approach or a mixture of the two are much better suited for real scalability. I'm not sure that you will find the answer here and I honestly believe that there are other communities better suited for that discussion. Best of luck, -Stefán On Sunday, 1 June 2014 11:24:40 UTC, Gaurav Dhiman wrote: > > Hi, > > Need to know opinion of other developers on below points considering the > development of large scale cloud based SaaS app > > 1. Are OrientDB JS functions strong enough to replace the need of > NodeJS/PHP kind of app server ? Do you see any limitations of using > OrientDB JS functions in place of NodeJS -- Async calls, multi-threading, > connection pool etc > > 2. In distributed mode (master-master), who receives the client request as > JS functions will be available on all machine instances. My questions might > be silly one, but correct me if I am wrong. > > Regards, > Gaurav > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
