Architectural Overview

At the heart of Zenoo Platform, Hub is a workflow engine. Each DO process is defined by a workflow using a custom DSL (Domain Specific Language). The workflow engine is used for orchestrating the corresponding DO process, i.e. a series of pages (routes), external calls, etc. This approach makes it possible to change a DO process configuration on-the-fly without rebuilding and redeploying the Zenoo Hub.

The Zenoo stack consists of several components:

• Hub Client: renders DO pages using common best-practice components, uses Hub Backend API for processing Customer input and DO process orchestration (what to do next), a Hub Client is implemented as a web or mobile app
• Hub Backend: provides API for Hub Clients and Admin UI, orchestrates DO processes, handles monitoring and logging
• API Gateway: handles API rate limiting, security and load balancing