Persistent channels

[ses]

The messaging / concurrency features in loop are a nice abstraction and I like the syntax. However one thing that is currently lacking, which other messaging technologies and frameworks supply is the ability to choose the storage medium for channels, and the messages within them. The ability to store the channels on the file system or in a database would allow tolerance against app downtime, giving guaranteed persistent message delivery. As I read more about current design and architecture trends, I feel these kind of features are becoming increasingly fundamental to applications. What do you think?

[Charles Forsyth]

I've always built that rather complex infrastructure on top of (ie, using) processes and channels.

It's "complex" not just because you might want different storage methods (eg, file system, or this or that database),

but providing fault-tolerance through replication on top of that (say) is much easier built using Loop and its abstractions than

having it in the run-time system. The algorithms for fault-tolerance using (say) the replicated state machine approach

are not huge, but they are non-trivial and relatively intricate.