Any set can be associated with many algebraic relations. You’re never going to find one that is “the” overall relation.

Who cares if you get events in a time order? Computers talk in sequences of bytes - so every set of events will come with an implicit ordering. Again, who cares? What matters is how the software uses the events; the use case imposes the set relations.

My advice: There are already terms for POSET (”POSET”) and TOSET (”TOSET”, “chain”). Let anyone who wants to use those terms, use them. Let stream and cloud revert to the IT based definitions that make sense.

But that fact is not useful in any way and the EPTS should have long ago removed POSET and TOSET from their definitions.

Oh that most certainly depends on many factors. Certainly cloud computing has its place in processing events, but I would not be so quick to classify it as low or high latency.

Hi Tim - good catch on terminology… per EPTS…
Event cloud: a partially ordered set of events (poset), either bounded or unbounded, where the partial orderings are imposed by the causal, timing and other relationships between the events.
Notes:
Typically an event cloud is created by the events produced by one or more distributed systems.
An event cloud may contain many event types, event streams and event channels.
The difference between a cloud and a stream is that there is no event relationship that totally orders the events in a cloud.  A stream is a cloud, but the converse is not necessarily true.
CEP usually refers to event processing that assumes an event cloud as input, and thereby can make no assumptions about the arrival order of events.

Han’s continues to make the mistake of stating that a clould of events (or event cloud) is simply “a bunch of streams”. This is technically incorrect and an oversimplification of complex systems.

Yours sincerely, Tim

A cloud of events is really a bunch of streams, maybe multiplexed and maybe distributed. You can’t use an event cloud, you always use one or more specific streams that are known a priori. And there are architecture considerations for every single stream that’s added to the cloud.

Contrast that to cloud computing where the idea is to have many identical computers, where you do not need to know a priori which one you will use. And adding one computer is the same as adding another (in theory).

And then the event cloud might be delivered by a computing cloud where you do not know in advance which computer will deliver events to a subscriber, but each subscriber knows which events they are looking for.