Implementing an event store on NATS: Design
In the first post, I introduced the primary requirements of an event store and the specific capabilities in NATS which
Implementing an event store on NATS: Introduction
An event store [https://en.wikipedia.org/wiki/Event_store] is a database
optimized for reading and transacting sequences of
Grokking NATS Consumers: Pull-based
In part one [https://www.byronruth.com/grokking-nats-consumers-part-1/] and two
[https://www.byronruth.com/grokking-nats-consumers-part-2/] of this series, we
studied
Grokking NATS Consumers: Push-based queue groups
In the previous article
[https://www.byronruth.com/grokking-nats-consumers-part-1/] I provided a quick
intro to JetStream and unpacked some of
Grokking NATS Consumers: Intro and push-based
The NATS team introduced the first preview of JetStream
[https://github.com/nats-io/jetstream#readme] in early 2020. It became
