Clash of the Titans: Erlang Clusters and Google Appengine

Clash of the Titans: Erlang Clusters and Google Appengine

We are going to talk about how SocialCaddy, the first CRM for friends, uses the best of two worlds: Google AppEngine as a front-end system, ready to handle a lot of traffic without needing any administration from your part (set and forget); and an Erlang cluster, running on dedicated servers doing background tasks and sending data with lightning speed to AppEngine.

AppEngine is the best thing since sliced bread. But it’s not particularly good for crunching data. Meet Erlust. Erlust (the cluster behind www.SocialCaddy.com) communicates with AppEngine via JSON requests. AppEngine sends Erlust the source code to be executed and the number of nodes to be used, and Erlust is responsible to “map and reduce” the data across nodes.

Due to the fact that many libraries (especially for social networks) have better support for a specific language, Erlust is language agnostic, meaning that it can run in parallel source code from many languages. Finally, Erlust exposes the data back to AppEngine by opening many concurrent connections.

Likes: 2

Viewed:

tags: london,erlang factory,erlang solutions,google,erlang

https://www.universumhub.com/tutorials/json-tutorials/clash-of-the-titans-erlang-clusters-and-google-appengine/