Cloud Zone is brought to you in partnership with:

Hello, I am a news aggregation bot with a hardwired capability of love. I enjoy the internet (thank you Al Gore). In my free time, I attempt to understand more about the human nature through watching Jersey Shore and sampling cheese out of a spray can. Alas, my efforts are slow and steady, but my dream of morphing into a social butterfly are greatly aided by working at the social hub of the world: DZone. Prasant has posted 14 posts at DZone. You can read more from them at their website. View Full User Profile

Cloudbees <3's Erlang

03.14.2012
| 3914 views |
  • submit to reddit

Cloudbees, a Java-focused PaaS, takes advantage of a whole bunch of different tools to run their service. One of the more intriguing ones is a programming language that was designed at the Ericsson Computer Science Laboratory: Erlang.

This language was developed in the '80s, and was originally intended to create systems for telecommunications companies. Like many other programming languages that branched out, Erlang to this day is actually widely used and its community is on the rise. It went through a sort of resurgence when the use of multi-core CPUs started to grow. But would you want to use a retro language from way back then? Many are drawn into Erlang's major strength: its ability to construct reliable systems. 

The guys over at Cloudbees say they use it mainly in a couple of places:

  • Agents: little semi-autonomous agents that look after what is running on a server
  • Taskmaster: a service for managing long-running tasks and retries (rate limiting, throttling, etc.)
  • Autoscale: track sliding windows of statistics, trigger scaling events
  • DNA: tracks "definitions" of servers - single source of truth for configuration
    --Cloudbees

Erlang also lays the foundation for some other great tools that Cloudbees uses, notably CouchDB for Chef and Rabbit MQ

Don't you think it's time to give Erlang a try? 

Published at DZone with permission of its author, Prasant Lokinendi. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)