Actyx builds on the local-first cooperation paradigm, where the autonomy of individual computing devices is of high importance: this is the foundation for creating a system that always works — as long as you have a running computer in your hand, that computer remains maximally useful.

Striving for this autonomy also poses some interesting questions: how do I know that someone else has received the information I just logged? Or the decision I just made? Working together requires two-way communication in many cases, which we explore in this article.

Today we are glad to announce the release of Pond version 2.5.0 on npm!

This release contains a whole new set of functions, which operate on events directly – no Fish required. Read on for a quick overview.

Want to keep track of and work with all fish of a specific type? Meet the RegistryFish pattern. (Updated version to Pond V2)

In event-sourced systems, state snapshots are used to alleviate the costs of computing state from event streams. Snapshots are essential to keep processing overhead and latency in check when working with long-lived and/or high traffic models.

The Actyx Pond ships with reasonable defaults for creating and retaining snapshots. However, in certain cases, snapshots may grow too large. This post outlines how to segment state and compress snapshots to avoid this.

Today, we are proud to announce the release of ActyxOS 1.1.0! With this release, we bring you significant performance improvements, many, many bug fixes and a couple of awesome features that will make working with ActyxOS an even better experience.

Today we are proud to announce the release of Pond version 2.4.0 on npm.

This release contains the following improvements:

• Improved exception handling capabilities
• observeAll – "Seed event" has succeeded "first event" terminologically. expireAfterFirst has been renamed to expireAfterSeed
• observeAll – The makeFish function is now allowed to return undefined, in order to ignore a given seed event
• Fixed an issue where moving a complex structure from an event into Fish state and later modifying that state could lead to data corruption
• Improved memory usage and time travel performance in some cases

On a related note, we have added technical documentation for observeAll and observeOne.

Happy hacking!