i\'m interesting in concurrency开发者_开发技巧 technics which are relatively easy to implement and they are suitable for scaling (multiple nodes).
I\'ve been reading as much as I can about how to write a scalable MySQL schema but I\'m still not sure if this is a good idea.
We have a web project, there are some multiple-choice questions and the registered users answer them...
In my rails app, I\'m using the SendGrid pa开发者_如何转开发rse API which posts mail to my server. Every now and then SendGrid\'s Parse API submits the same email twice.
开发者_运维知识库 It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical andcannot be reasonably answered in its current for
I keep hearing that one of the ways to architect a scalable website is to not use joins. How is the world do you do that since most data is relational?
If you were creating a site, with similar functionality to youtube (this isn\'t another clone, it just has a segment with similar functionality).What stack would you use to be able to develop and allo
Part A: Erlang has a lot of success stories about running concurrent agents e.g. the millions of simultaneous Facebook chats. That\'s millions of agents, but of course it\'s not milli开发者_C百科ons
We have a requirement to be able to access resources on a mobile device. the mobile device must act as a server. it must be available no matter how the phone is connected (wifi, 3g, behind firewall, e
We are building a SaaS application that will be multi-tenant and is envisaged to have heavy user traffic. The solution will be hosted on Liferay Portal. Liferay out of the box has great support for To