helyOS® follows an event-driven architecture pattern. In helyOS®, the end-user features are composed of one or several microservices triggered according to the user-machine interaction.
The developer will register these microservices in helyOS® dashboard according to the application goal.
A software developer has built a web app for remote vehicle control. They registered three microservices in the helyOS® dashboard: one for maps (Map Service), one for path calculations (Trucktrix® Path), and one for cooperative planning (Trucktrix® Coop).
When a web app user starts a mission that requests two vehicles to drive to a specified region, the following events are triggered:
- The GUI sends the request for mission.
- helyOS® breaks down the mission in requests for the three microservices.
- In the first microservice, helyOS® retrieves the latest obstacle map data.
- The second microservice uses the map data to calculate the driving paths.
- The third microservice updates the driving paths to avoid collisions between the two vehicles.
- The results are collected.
- The final result is encapsulated and ready for the vehicles.
- The vehicles get their missions via AMQP at the right moment.