Q4/19 Roadmap Update

September 18, 2019 by Oliver Stollmann and Dr. Roland Kuhn

We are excited to publish our first public roadmap update. Stay tuned for more.

Here’s what you can expect in terms of Actyx releases in the coming months. If you’re interested in using ActyxOS for your use-case and think you’ll need something that’s not on this list, please do get in touch.

  • First production release of the Actyx Pond and Event Service, allowing the development of fully decentralized business logic. While the Actyx Pond is TypeScript based, the Event Service comes with an HTTP API which allows usage from any programming language.
  • Local development on Windows, Linux, and Mac OS X with rapid test cycles, deploying to edge devices through ActyxOS on Linux and the Docker runtime, all with the help of the Actyx CLI.
  • Logging and metrics via the initial release of the Console Service.
  • Development of UI applications for mobile edge devices using the initial releases of ActyxOS on Android and the WebView runtime for Android.

Future work, most of which will not be released this year:

  • Improved ergonomics when using the Pond APIs in v2, together with the capability of delivering events in-order when for example writing to an ERP system (trading availability for consistency).
  • Operate and maintain remote deployments by checking logs and metrics in the cloud-based Actyx Console.
  • Match your production environment and test your application’s assumptions with the help of the Distributed TestKit.
  • Decentralized, content addressable storage for data of any kind (photos, documents, machine parameters) using the first production-ready Blob Service.
  • Keep the ever-growing storage size of the events under control by setting an expiry period for selected event streams.
  • Backup the data by extracting and archiving the events from the Event Service.
  • Deploy your apps to devices and handle the configurations remotely using the Actyx Console.
  • Integrate with ActyxOS by using the Actyx Runtime of your favorite language: we’re planning C# and JVM-based versions.
  • Use true lambdas and serverless on the edge by defining a deterministic computation that just runs wherever there is computational power available.