|Name||Modified||Size||Downloads / Week||Status|
|Totals: 3 Items||32.5 MB||3|
(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."
Software developers that do not want to get locked into corporate vendors or frameworks that push for perpetual commercial support or licenses.
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.
The CloudI API provides a simple set of functions for Service-Oriented Architecture (SOA) development in any supported language (currently C++/C, Java, Python, Ruby, and Erlang):
External communication that needs to scale (beyond 10,000 connections) can use an internal CloudI service (implemented in Erlang) which may do processing for one or more external CloudI services (implemented C++/C, Java, 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.
Please see the FAQ for more details.
The default CloudI configuration runs many tests that can be used as examples of CloudI integration (see src/cloudi.conf.in).
Optional (installed/linked statically, automatically):
For configuration options, see FAQ: 3.2 - Installation Options.
./configure make make install
Within the installation directory the "bin/cloudi" script controls CloudI.
To start CloudI:
To stop CloudI:
Dynamic configuration uses the CloudI Job API (See src/job_api/README)
Michael Truog (mjtruog [at] gmail (dot) com)