Skip to main content

· One min read

Do you want your production deployment to benefit from all amazing features introduced with Actyx 2.x and newer releases?

With the Actyx 2.3.0 release, we are excited to offer extensive migration tooling that will enable you to easily migrate to Actyx version 2.

If you want to find out more about how to migrate your production deployment, head over to the migration section of our how-to guides!

As always, we are keen on hearing your opinions and feedback. If you have any questions or run into problems during your migration, please don't hesitate to contact us on Discord or visit our Community Forum!

· 2 min read

Local-first software is magical in that it almost always works — at least locally. With Actyx this is possible because Actyx is partition tolerant, i.e. a network issue does not immediately take everything down.

This also means that twins and applications aren't always in sync. And sometimes it can get a little tricky understanding where nodes stand with regard to synchronizing with each other.

That is why we are now releasing Offset Diagnostics in the Actyx Node Manager.


Actyx Node Manager 2.4.0 introduces two new features to help you better understand what is happening:

  • Find out which event streams a node has synchronized, and up to where.
  • Easily see how event synchronization is progressing in a swarm of nodes.

· 5 min read
Benjamin Sieffert

With the release of Actyx V2, we are also shipping a new major version of the Pond: 3.0 is here.

The major features of this release are:

  • Compatible with shiny new Actyx V2!
  • Also compatible with ActyxOS V1
  • Hugely improved performance in the case of many active Fish, independent of which Actyx version is used

In terms of API changes, we have introduced as little breaking changes as possible. This should make it straight-forward to migrate an existing app to Pond 3.0 and thus be able to run it on Actyx V2!

Read on to learn all you need to know.

· 6 min read
Dr. Roland Kuhn

The main advantage of an event-based system like Actyx is that you have a lot of flexibility on how to make even more use of your data when adding new use-cases. This is achieved by combining the event streams of existing apps with new apps and new business logic. One issue that frequently arises in these scenarios is that further use, for example in business intelligence tools, exposes a phenomenon that we simply call “negative time spans”.

In this article I explain all about the how and why — the main takeaway is that you should make really sure to use NTP on all nodes.