Awesome Open Source
Awesome Open Source

CloudI 2.0.0

Build Status CloudI IRC Project Stats


MIT License


What is CloudI?

(short answer) "A distributed application server that provides efficient messaging for many programming languages within a single service abstraction that is both scalable and fault-tolerant."

(shorter answer) "A rock-solid transaction processing system for flexible software development."

(shortest answer) "A Cloud at the lowest level."

Who would use CloudI?

Software developers that do not want to get locked into corporate vendors or frameworks that push for perpetual commercial support or licenses.

Why should CloudI be used?

CloudI makes software fault-tolerant and scalable, utilizing Erlang, even if the software is legacy source code. CloudI mitigates software development risk (delays or failures) when making software scale in non-Erlang programming languages, or during a conversion of a software system (fully or partially) to the Erlang programming language.

How should CloudI be used?

The CloudI API provides a simple set of functions for Service-Oriented Architecture (SOA) development in any supported language (currently C/C++, Go, Haskell, Java, JavaScript, OCaml, Perl, PHP, Python, Ruby, and Erlang/Elixir):

  • subscribe, unsubscribe, subscribe_count
  • send_async, send_sync, mcast_async (mcast_async == publish)
  • recv_async
  • return, forward

External communication that needs to scale (beyond 10,000 connections) can use an existing internal CloudI service (implemented in Erlang or Elixir) which may do processing for one or more external CloudI services (implemented in C/C++, Go, Haskell, Java, JavaScript, OCaml, Perl, PHP, Python, and/or Ruby)

Even if external communication doesn't need to scale, private cloud computing tasks (number crunching) can gain fault-tolerance and internal system scalability within CloudI.

Where should I find more information?

Please see the FAQ for more details.



  • Erlang >= 19.3 (erlang /Ubuntu)
  • C++ (g++ /Ubuntu)
  • boost >= 1.36.0 (libboost-system-dev libboost-thread-dev libboost-dev /Ubuntu)

Optional (default="yes"):

  • Java >= 1.5 JDK
    • (default-jdk /Ubuntu)
    • Use the "--enable-java-support=no" configure flag to disable
  • JavaScript >= 0.12.18
    • (nodejs /Ubuntu)
    • Use the "--enable-javascript-support=no" configure flag to disable
  • Perl >= 5.10 (with Compress::Zlib)
    • (perl perl-modules /Ubuntu)
    • Use the "--enable-perl-support=no" configure flag to disable
  • PHP >= 7.0
    • (php /Ubuntu)
    • Use the "--enable-php-support=no" configure flag to disable
  • Python >= 2.7.0
    • (python3 python3-dev /Ubuntu)
    • Use the "--enable-python-support=no" and "--enable-python-c-support=no" configure flag to disable
  • Ruby >= 1.9.0
    • (ruby /Ubuntu)
    • Use the "--enable-ruby-support=no" configure flag to disable
  • GNU MP library
    • (libgmp-dev /Ubuntu)
    • Used in the hexpi (C++) integration test only ("--with-integration-tests=no" configure flag to disable)

Optional (default="no"):

  • Go >= 1.6
    • (golang /Ubuntu)
    • Use the "--enable-go-support" configure flag to enable
  • Haskell (GHC >= 7.10.3 and cabal-install >= 1.22)
    • (ghc cabal-install zlib1g-dev /Ubuntu)
    • Use the "--enable-haskell-support" configure flag to enable
  • OCaml >= 4.03.0
    • (ocaml /Ubuntu)
    • Use the "--enable-ocaml-support" configure flag to enable


For configuration options, see FAQ: 3.2 - Installation Options.

cd src
sudo make install


Within the installation directory the cloudi script controls CloudI.

To start CloudI:

sudo cloudi start

To stop CloudI:

sudo cloudi stop


See the Quick Start Guide or the API documentation

Integration points:

Dynamic Configuration and Monitoring:


Maintained Services Excluded from this Repository:

Unmaintained Services Excluded from this Repository:

The default CloudI configuration can run the included integration tests if all the supported programming languages are enabled at configure time (they are by default) and the --with-integration-tests-ran configuration argument is used (to choose the src/ file).

If the --with-integration-tests-ran configuration argument is not used, the more minimal CloudI configuration will be used instead (in the src/ file) to support basic things like the Quick Start Guide, the Dashboard and any tutorials or examples.


Michael Truog (mjtruog at protonmail dot com)

Get A Weekly Email With Trending Projects For These Topics
No Spam. Unsubscribe easily at any time.
erlang (782
cloud (413
microservices (405
distributed-systems (264
reactive (254
concurrency (179
cloud-computing (58
scalability (55
actor-model (53
functional-reactive-programming (42
fault-tolerance (28
soa (20

Find Open Source By Browsing 7,000 Topics Across 59 Categories