This seems like a really interesting approach. I've often wondered what it would be like to live in a world where almost everything could be wrapped in a transaction, and it seems like Cloudl sort of goes in this direction.
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 expected to die when errors occur within services (http://en.wikipedia.org/wiki/Transaction_processing_system). Instead, database usage through CloudI services (or within a CloudI service) provides persistent storage.
Comments
This seems like a really interesting approach. I've often wondered what it would be like to live in a world where almost everything could be wrapped in a transaction, and it seems like Cloudl sort of goes in this direction.
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 expected to die when errors occur within services (http://en.wikipedia.org/wiki/Transaction_processing_system). Instead, database usage through CloudI services (or within a CloudI service) provides persistent storage.