Benefits of blob storage for Events:
1) Events tend to be small, numerous, varying-sized and continuous. Blobs can be large and binary and support Events with varying number of key-values.
2) Event processing can become compute-oriented.
3) Storage of Events can scale while remaining globally accessible
4) Majority of Events don’t change much which leads to efficiencies in storage.
5) Even skip-level Events can be stored in object storage to make only the relevant web-accessible.
6) Events can be partitioned by source or sink or flow and this makes it easy to store them in object storage.
7) Events can be queried with no regard to their storage and object storage makes the nodes available over http.
8) Events are suitable for library which can be hosted on object storage
9) Events can have metadata and object storage facilitates tagging and adding metadata
Blobs and Events are mutually beneficial when data transfers between them are facilitated
Additionally, Event stores can be software defined and allow object storage to serve as tier 2 storage for the overlay. In this case, we can differentiate their products as different instances used and maintained independently. We don’t differentiate Event store and object store as different storage to the customers although they could be made side by side for supporting data transfers for different purposes.
Object storage facilitates storage classes. The use of dynamic assignments helps map Events to blobs which can then be assigned to different storage classes thus allowing secondary offline workflows that are independent from the primary create-update-delete oriented workflows associated with Events.