concept Erlang in category rabbitmq

appears as: Erlg, Erlg
RabbitMQ in Depth

This is an excerpt from Manning's book RabbitMQ in Depth.

  • Open source— Originally developed in a partnership between LShift, LTD, and Cohesive FT as RabbitMQ Technologies, RabbitMQ is now owned by Pivotal Software Inc. and is released under the Mozilla Public License. As an open-source project written in Erlang, RabbitMQ enjoys freedom and flexibility, while leveraging the strength of Pivotal standing behind it as a product. Developers and engineers in the RabbitMQ community are able to contribute enhancements and add-ons, and Pivotal is able to offer commercial support and a stable home for ongoing product maturation.
  • 1.1.1. RabbitMQ and Erlang

    As a highly performant, stable, and clusterable message broker, it’s no surprise that RabbitMQ has found a home in such mission-critical environments as the centerpiece of large-scale messaging architectures. It was written in Erlang, the telco-grade, functional programming language designed at the Ericsson Computer Science Laboratory in the mid-to-late 1980s. Erlang was designed to be a distributed, fault-tolerant, soft real-time system for applications that require 99.999% uptime. As a language and runtime system, Erlang focuses on lightweight processes that pass messages between each other, providing a high level of concurrency with no shared state.

    Erlang’s design, which focused on concurrent processing and message passing, made it a natural choice for a message broker like RabbitMQ: As an application, a message broker maintains concurrent connections, routes messages, and manages their states. In addition, Erlang’s distributed communication architecture makes it a natural for RabbitMQ’s clustering mechanism. Servers in a RabbitMQ cluster make use of Erlang’s inter-process communication (IPC) system, offloading the functionality that many competing message brokers have to implement to add clustering capabilities (figure 1.1).

    Figure 1.1. RabbitMQ clusters use the native Erlang inter-process communication mechanism in the VM for cross-node communication, sharing state information and allowing for messages to be published and consumed across the entire cluster.

    Despite the advantages RabbitMQ gains by using Erlang, the Erlang environment can be a stumbling block. It may be helpful to learn some Erlang so you’re confident in managing RabbitMQ’s configuration files and using Erlang to gather information about RabbitMQ’s current runtime state.