[erlang-questions] [ANN] CloudI 1.5.3 Released!
Michael Truog
mjtruog@REDACTED
Fri Sep 16 03:20:52 CEST 2016
Download 1.5.3 from http://sourceforge.net/projects/cloudi/files/latest/download
(checksums at the bottom of this email)
CloudI (http://cloudi.org/) is a "universal integrator" using an Erlang core to
provide fault-tolerance with efficiency and scalability. The CloudI API
provides a minimal interface to communicate among services so programming
language agnostic and protocol agnostic integration can occur.
CloudI currently integrates with the programming languages
C/C++, Elixir, Erlang, Java, JavaScript/node.js, PHP, Perl, Python, and Ruby,
while including many reusable services that rely on the CloudI service bus.
The details for this release are below:
* services_update is a new addition to the CloudI Service API for
updating any service without downtime, i.e., module hot-code reloading
with internal services and OS process restarts with external services
while CloudI ensures service requests are not lost and service request
handlers are not interrupted in any of the service processes or threads
(see http://cloudi.org/api.html#2_services_update for more information)
* A Java user tutorial has been added based on the work of Bruce Kissinger
(http://cloudi.org/tutorial_java.html)
* The Java CloudI API can now use method references with Java 8
* New service configuration options were added or improved:
'directory', 'dispatcher_pid_options', 'init_pid_options',
'request_pid_options', 'info_pid_options'
(http://cloudi.org/api.html#2_services_add has more information)
* Many of the database services were removed with their dependencies,
from the main repository due to service development demonstrating that
failures remain isolated when using a database client locally within a
service (database services can help scale usage and make sure it is
fault-tolerant, but only after the service business logic is in a stable
state and excluding these services will help guide developers)
* cloudi_service_monitoring was improved:
* Any Erlang process can create or update metrics now
* cloudi.log output can be monitored with
aspects_log_before or aspects_log_after
* All CloudI service related metrics now have a static metric name,
identified with TYPE.FILENAME.INDEX instead of the service ID
as described in the ChangeLog file
* Erlang internal services now have two optional behaviour functions
(some services choose to use only one of the functions):
* cloudi_service_handle_request/11
* cloudi_service_handle_info/3
* Bugs were fixed and other improvements were added
(see the ChangeLog for more detail)
Please mention any problems, issues, or ideas!
Thanks,
Michael
SHA256 CHECKSUMS
cloudi-1.5.3.tar.gz (13856 bytes)
9163adb2c12a46909daca612f71603a0bcfff4f1fc5bee78cf5178ea7bef247e
cloudi-1.5.3.tar.bz2 (11352 bytes)
2e57b9b79123d482ab94b21edfa43df192122196c15179083c18fc347e12755a
More information about the erlang-questions
mailing list