Genome Orchestrator
Axon Async Asynchronous Notification Delivery System
Manage SMS, email and mobile push notifications asynchronously in message queues; deliver them with dynamic templates and retry guarantees without straining your main applications.
- Message broker queues
- SMS, email and push
- Retries and dead-letter queue
Overview
Do not make notifications wait, do not make transactions wait: every message in a queue, every event on record.
In modern enterprise architectures, external API calls such as sending email or delivering SMS OTPs create bottlenecks because of network latency. Axon, the asynchronous notification backbone of Genome, moves these loads into message broker queues to protect the speed of the main application.
Working with SMS gateways and corporate SMTP servers, Axon runs everything from approval notices to OTP codes asynchronously, and prepares multilingual, tenant-specific output with its dynamic template engine.
Message broker
Notification requests build up in secure queues and workers consume them in balance.
Three channels
SMS OTP, corporate email and mobile push through FCM / Expo on one backbone.
Retries
When a gateway drops, no message is lost: it is retried and kept in the dead-letter queue.
Domain events
Modules publish events and Axon listens; business logic stays apart from delivery detail.
Message bus
Publish an event: queues, workers and delivery flow in real time.
Publish the domain events your modules raise; Axon spreads them across SMS, email and push queues and the workers consume them. OTP codes land on the phone screen. Cut the SMS gateway to see retries and the dead-letter queue.
SMS gateway
Message broker lanes
Waiting for a message
- Queued
- 0
- Delivered
- 0
- Dead-letter queue
- 0
Inside the console
Four screens of the notification backbone
Each tab shows one Axon screen with its sample data.
Message queue and bus management
Buffer every notification request in secure queues on the message broker. Distribute them in balance through the worker architecture without losing any, even at peak traffic.
- Message broker pipelineSMS and email operations that create external network load are routed to the queue and consumed asynchronously in the background.
- Error handling and retryIf the target gateway drops briefly, messages are retried on set schedules without being lost.
- Horizontal scalabilityWhen load grows, add workers to process thousands of notifications per second.
| Queue | Active messages | Workers | Throughput | Status |
|---|---|---|---|---|
| sms.otp | 12 | 4 | 120 msg/s | Active |
| mail.orders | 340 | 2 | 45 msg/s | Consuming |
| push.alerts | 0 | 3 | 210 msg/s | Idle |
| mail.invoices | 85 | 2 | 65 msg/s | Consuming |
Why Axon
Six advantages that keep your system light
Axon makes your communication layer asynchronous with queues, keeping the enterprise system fast.
Message broker architecture
A durable message bus that safely buffers all external API requests.
Fast SMS gateway
SMS OTPs and order notices reach recipients within milliseconds.
Dynamic template compiler
Email and SMS content is compiled at run time to the recipient's locale.
Zero-wait user experience
The main application never waits for mail delivery; the user's action is saved at once.
Fault tolerance and recovery
During brief outages messages wait in the dead-letter queue and are recovered with retry policies.
Multi-tenancy integration
Each organization manages its own mail and SMS gateway settings independently.
FAQ
What to know about the Axon Notification System
Answers to common questions. For more, get in touch with us.
Axon is the asynchronous messaging and notification layer of the Genome ecosystem. It delivers communication that creates external network latency, such as email, SMS and mobile push, by compiling it in background queues without straining web applications.
When a user acts (e.g. approves an order), the email or SMS request is written to a background queue instead of being sent straight to the recipient, and the action finishes immediately. The queue layer consumes the message in the background, so the user never waits for the mail server.
Axon builds email and SMS content with a dynamic template compiler. Templates with HTML and text fields are merged with the user's data at run time, producing personalized content in the recipient's language.
Axon talks directly to SMS gateways and corporate email servers. Thanks to multi-tenancy, each group company can set its own username, password, API key or mail server.
Events raised in the domain layer are written to the queues as asynchronous events through the Axon integration. Modules finish their own business processes and stay independent of notification delivery detail.
Glossary
Terms used on this page
- Message broker
- Queueing infrastructure that carries messages between applications asynchronously without losing them.
- Message bus
- The communication backbone that lets services in the system message each other asynchronously and safely.
- Template engine
- A compiler that merges static template files with user data at run time to produce HTML or text output.
- Dead letter queue
- A special queue that collects messages that could not reach their target or failed during processing, so none are lost.
- OTP
- One-Time Password: a single-use, short-lived verification code.
- Spam filter validation
- Security standards that prove sent mail is authorized by your domain so it lands in the inbox.
LET'S START
Put your notifications in queues with Axon.
Let our team show you Axon live on your own events, channels and gateway setup.
