Flow separation

With the Flow Separation feature, we have completely rethought event management. The flows are now divided into three distinct categories according to their origin:

• User: events triggered by users via the interface
• System: internal engine events (alarms, triggers…)
• External: events from connectors
  
  

Each has its own processor and a dedicated pool of “workers”, guaranteeing smooth execution and preventing one stream from blocking the others.

This redesign improves the system’s responsiveness, particularly for “user” actions, and removes obsolete configurations linked to publishQueue and consumeQueue queues.

New flags allow you to fine-tune the number of workers per event type for greater scalability.

For more technical information on flow separation and other Canopsis features, please refer to our documentation. If any unanswered questions remain, you can also contact our team via the contact form.