Skip to main content
Version: 2.6

Tips for Development

Here you can find some tips for developing Reaktors.

Reaktor Structure​

When creating a Reaktor for a more complex workflow, it is important to think about the structure of the Reaktor. We advice to make a simple sketch of your workflow as a tree structure. This will help you to understand the dependencies between the Aktors and how to compose them.

See this example of a Reaktor Sketch:

This diagram shows a typical Reaktor structure where:

  • Green nodes represent complex Aktors that may contain nested Aktors
  • Pink nodes represent AktorFunctions that perform simple operations

When to use AktorFunctions vs Aktors​

Aktors should be used when you want to have a more complex Aktor tree. If you know that the Aktor's logic will be more complex and can even be reused in other Reaktors, you should use an Aktor. This helps to make your code more structured and reusable, as well as easier to maintain.

AktorFunctions should be used when you know that the Aktor's logic will be simple contains function calls that cannot be further structured into multiple parts. This includes REST calls, database calls, data transformations, etc.