Start by defining the roles and actions you want the software to enable. This helps you focus on the goal that you’re trying to achieve, unlike conventional software, which focuses on the application’s infrastructure.
We use flows to model the steps that need to be executed when an action is triggered. These steps can be pulled from the library or simply be placeholders. Flows map out the logic of how your system needs to work, using branches, loops and ‘races’.
Once you’ve modeled your software needs, your team can then add more detailed steps, either configured from the library - or custom coded. Writing code within the model maintains the flow’s context, and will highlight any dependencies affected by your changes.
At every step in the process, whether you’re modeling or building, anyone can run any flow to check its behavior is as expected. This allows you to do Test Driven Development, defining the success criteria up front. You can also watch and debug the flow execution in real time, logging all data.
As you model and build, the Trixta platform autonomously creates the system architecture, and, based on this, spins up the infrastructure in the background. Each space becomes a Docker Container managed by Kubernetes, with your roles and actions becoming like REST API or web socket endpoints. It is run on BEAM, the super powerful Erlang virtual machine - providing unmatched resiliency and scalability.