[erlang-questions] [ANN] CloudI 1.2.3 Released!

[Michael Truog]

Download 1.2.3 from http://sourceforge.net/projects/cloudi/files/latest/download

What is CloudI?
A Cloud at the lowest level!

CloudI (http://cloudi.org/) is a "universal integrator" using an Erlang core, with its actor model, to pursue efficiency, fault-tolerance and scalability.  The CloudI API provides a minimal interface to communicate among actors that are called services, so programming language agnostic, database agnostic, and messaging bus agnostic integration can occur.  CloudI currently integrates with the programming languages Erlang, C/C++, Java, Python, and Ruby, the databases PostgreSQL, MySQL, couchdb, memcached, and tokyotyrant, the messaging bus ZeroMQ and the internal CloudI service bus. HTTP is also supported for easy integration with cowboy. If anyone is willing to get involved, don't hesitate to contact me or start looking at the code. Thank you for all the suggestions and questions so far!

This release provides some minor fixes after the 1.2.2 release. The 1.2.2 loadtest results are summarized at https://github.com/okeuday/CloudI/raw/master/src/tests/http_req/loadtest/results_v1_2_2/201306_summary.pdf . The details are below:

June 8, 2013
  Version 1.2.3 (beta) released.
  * Added internal service purging when services are removed.
    The service module, or service application modules are purged after the
    service has been stopped, and the service applications (if any were used)
    has been stopped. The functionality works with modules, applications and
    releases (within a .script file). When applications are stopped and
    purged, only applications which are not dependencies for other running
    applications are removed.
  * Focused on bugs/fixes, mainly for OSX. The external service "local"
    protocol configuration option did not work properly on some installations
    of OSX, so the default CloudI configuration file now uses the "tcp"
    protocol configuration option (to be the same as releases before 1.2.2).
    The problem with the "local" protocol configuration option may be limited
    to slower machines (the problem is caused by execution spending too much
    time within a socket accept function call within an Erlang NIF).
    The "local" protocol configuration option on OSX will be addressed in a
    later release.

Please mention any problems, issues, or ideas!

Thanks,
Michael