#CloudI 1.5.1

LICENSE

BSD License

ABOUT

What is CloudI?

(short answer) "An application server that efficiently integrates with many languages, many databases, and many messaging buses in a way 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, Java, JavaScript, Perl, PHP, Python, Ruby, and Erlang):

• 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) which may do processing for one or more external CloudI services (implemented C++/C, Java, JavaScript, 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.

INSTALLATION

Requirements

• Erlang >= R16 (erlang/Ubuntu, erlang/macports)
• C++ (g++/Ubuntu, libstdcxx/macports)
• Java >= 1.5 JDK (default-jdk/Ubuntu, (built-in)/OSX)
• Javascript >= 0.8.0 (nodejs/Ubuntu)
  • (node.js package)
• Perl >= 5.10 (perl/Ubuntu)
  • Compress::Zlib (cpan)
• PHP >= 5.3.6 (php5/Ubuntu)
• Python >= 2.7.0 (python+python-dev/Ubuntu, python27/macports)
• Ruby >= 1.9.0 (ruby1.9.1/Ubuntu, ruby19/macports)
• GNU MP library (libgmp3-dev/Ubuntu, gmp/macports)
• boost >= 1.36.0 (libboost-system-dev+libboost-thread-dev+libboost-dev/Ubuntu, boost/macports)

Optional (installed/linked statically, automatically):

• ZeroMQ >= 3.x.x or 2.x.x (use the "--with-zeromq" configure flag)
  • uuid-dev (uuid-dev/Ubuntu, ossp-uuid/macports)

Building

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

./configure
make
sudo make install

Running

Within the installation directory the cloudi script controls CloudI.

To start CloudI:

sudo cloudi start

To stop CloudI:

sudo cloudi stop

INTEGRATION

See the Quick Start Guide or the API documentation

Integration points:

• CloudI API (See src/api/README)
• HTTP with cloudi_service_http_cowboy and cloudi_service_http_elli
• ZeroMQ with cloudi_service_zeromq
• Supported databases
  • elasticsearch with cloudi_service_db_elasticsearch
  • Cassandra with cloudi_service_db_cassandra or cloudi_service_db_cassandra_cql
  • CouchDB with cloudi_service_db_couchdb
  • memcached with cloudi_service_db_memcached
  • MySQL with cloudi_service_db_mysql
  • PostgreSQL with cloudi_service_db_pgsql
  • Riak with cloudi_service_db_riak

Dynamic configuration uses the CloudI Service API (See src/service_api/README)

The default CloudI configuration runs many tests that can be used as examples of CloudI integration (see src/cloudi.conf.in).

CONTACT

Michael Truog (mjtruog [at] gmail (dot) com)