Observing appended events on distributed systems about cosmostore HOT 7 CLOSED

I guess this is blatant advertising but...

While the general process of deciding events to write, writing events, and doing (cached) reads is relatively generalisable... (see Equinox)

There are many more factors in play on the observing events... https://github.com/jet/propulsion's raison d'etre is exactly this - wrapping up the ways of doing such observations in appropriate ways. (The code originated in Equinox, but it quickly becomes apparent as you strt pulling on the thread that the concerns are different).

In general, Propulsion has minimal coupling to Equinox (PRs to completely decouple it are more than welcome)

If you want to discuss more, #equinox in the DDD-CQRS-ES slack is probably the best place.

The specific case of SqlStreamStore is unfortunately not yet covered, but would be a welcome addition:

• @Rajivhost started jet/propulsion#52, but I asked him to hold back as...
• @scrwtp has a simpler variant in the works (he's proving it in prod atm)...

from cosmostore.

I would for such case Queue (Azure Table Storage Queue or Service Bus) or Topic.

from cosmostore.

Hmmm. 🤔 Most likely not in near future. I think making these events observable as they are processed in store itself should be sufficient for most of scenarios. Of course, if you are on Cosmos DB, you can use change feed functionality, but not sure how is it with ordering of events.

from cosmostore.

There are some concerns regarding handling out of order messages, global ordering of events. Wondering would that be a part of this library in the future?

from cosmostore.

Cool thanks for letting know, I think this feature is a critical component for distributed applications or read instances in CQRS. I know SQLStreamStore has support for it, which I assume uses polling. Currently I use combination of redis streams for it and SQL for persistence.

from cosmostore.

I guess we can close this now

from cosmostore.

FWIW there's a generic SqlStreamStore projector that uses Propulsion.SqlStreamStore in jet/dotnet-templates#74 (the same proProjector template can consume from CosmosDB or EventStoreDB)

Happy to take PRs to Propulsion to enable tailing other sources...

from cosmostore.