okeuday

3 ms·

1. 1.▲
   by okeuday 12y ago

   Also, CloudI ( http://cloudi.org ) provides supervisor functionality for Python services to help keep source code in Python fault-tolerant. There have been no problems handling large quantities of data there.
2. 2.▲
   by okeuday 13y ago

   CloudI and Erlang underneath are focused on soft real-time. For hard real-time (embedded) you need tighter integration with hardware. While it is true that people attempt to pursue (soft) real-time fault-tolerance on the JVM, the point in
3. 3.▲
   by okeuday 13y ago

   CloudI is under an open source software license, the BSD license, which is the most permissive of the open source licenses. So you can use CloudI in any product you want, using it how you want, on whatever servers you choose. The license
4. 4.▲
   by okeuday 13y ago

   You can try to have fault-tolerance in the JVM, but not real-time fault-tolerance, and there is a difference. The goal is to have decent performance while being fault-tolerant. The JVM garbage collection prevents real-time fault-tolerance
5. 5.▲
   by okeuday 13y ago

   In CloudI, each service request is a transaction to be processed (with a UUID that is unique for all service requests among the connected CloudI nodes). Filesystem storage of transactions isn't a goal here, since transactions are expe