Event Management
The platform’s business-event stream — an append-only log that modules emit into and automation reacts to.
Business event stream.
Purpose
Whenever something meaningful happens — a scheduled job runs, an alert fires, a webhook signal arrives — a domain event is recorded. Events are the backbone the scheduler, alerts and notifications build on, and they carry a correlation id so you can trace a whole chain of activity.
The Event Management module provides a central business capability for capturing, publishing, routing and managing business events generated throughout the platform.
It enables business modules to communicate using standardised business events while remaining operationally independent.
The module serves as the foundation for event-driven business processes across MyAlgoGuru.
Objectives
The module will:
- Capture business events.
- Standardise event definitions.
- Publish business events.
- Route events to authorised consumers.
- Support event subscriptions.
- Maintain event history.
- Enable event-driven business workflows.
Functional Scope
The module includes:
- Event Definition
- Event Classification
- Event Publication
- Event Subscription
- Event Routing
- Event Processing
- Event History
- Event Search
- Event Monitoring
- Event Audit
Event Model
A business event represents the occurrence of a meaningful business activity within the platform.
Examples include:
- Strategy Generated Signal
- Order Submitted
- Order Executed
- Position Opened
- Position Closed
- Portfolio Updated
- Risk Limit Breached
- Market Session Started
- Market Session Closed
- User Logged In
Business events remains immutable after publication.
Each event will represent a completed business occurrence.
Event Classification
The platform will classify business events into standard categories.
Typical categories include:
- Market Events
- Strategy Events
- Order Events
- Position Events
- Portfolio Events
- Risk Events
- User Events
- System Events
- Notification Events
- Integration Events
The design will support additional event categories in future.
Event Publication
Authorised business modules will publish business events.
Typical publishers include:
- Live Market Data
- Strategy Deployment & Execution Engine
- Order Management
- Position Management
- Portfolio Management
- Risk Management
- Scheduler
- User Management
- Integration Services
Every published event will become part of the event history.
Event Subscription
Authorised business modules will subscribe to relevant business events.
Typical subscribers include:
- Scheduler
- Alert Management
- Notification Management
- Reporting
- AI Services
- Audit Services
- Portfolio Management
- External Integration Services
Subscriptions remains configurable.
Event Routing
The platform will route published events to subscribed business modules.
Routing will support:
- Single Consumer
- Multiple Consumers
- Conditional Routing
- Category-Based Routing
Event routing will preserve event integrity.
Event Processing
The platform will process published events.
Processing activities may include:
- Event Validation
- Event Classification
- Event Routing
- Event Delivery
- Event Status Management
- Event Recording
Event processing remains independent of business logic execution.
Event History
Historical business events is preserved.
Each historical record includes:
- Event Identifier
- Event Category
- Event Type
- Event Source
- Event Timestamp
- Event Status
Historical records remains immutable.
Event Search
Authorised users is able to search business events.
Typical search criteria include:
- Event Category
- Event Type
- Source Module
- User
- Instrument
- Strategy
- Portfolio
- Date Range
- Event Status
Search capability will support operational analysis and audit.
Event Monitoring
The platform will monitor business event activity.
Monitoring may include:
- Published Events
- Processed Events
- Pending Events
- Failed Events
- Processing Statistics
- Delivery Statistics
Monitoring will support operational visibility.
Business Rules
- Every event will have a unique identifier.
- Every event will belong to one event category.
- Every event will have one originating source.
- Events is immutable after publication.
- Event publication does not modify business data.
- Event routing will preserve event integrity.
- Historical events will never be deleted.
- Only authorised modules may publish business events.
- Only authorised modules may subscribe to business events.
Audit Requirements
The platform will maintain an audit trail for event activities.
Audit events includes:
- Event Publication
- Event Subscription
- Event Routing
- Event Processing
- Event Delivery
- Event Failure
- Event Archive
Audit records remains immutable.
Out of Scope
The following are outside the scope of this module:
- Strategy Execution
- Order Execution
- Market Data Processing
- Portfolio Valuation
- Notification Delivery
- External API Communication
These responsibilities belong to their respective business modules.