All projects
Alva Hub
Event layer over the Omie API with retries, dead-letter, circuit breaker and idempotency.
Internal system, no public access.
About the project
A service that centralizes communication with the Omie API and delivers events to the company's other systems.
It was designed to fail well: tasks with retry limits and dead-letter, event replay from the admin, a circuit breaker for Omie API outages, rate limits and tokens per destination, an idempotency key and a sequence number on every delivery.
Queues are isolated per ERP account, so a problem in one account doesn't stall the others, and the team gets an email when an event lands in the dead-letter.
Read the article: FilasWhat shipped
- max_retries and dead-letter on every task
- Replay of dead-lettered events from the admin
- Global circuit breaker for systemic Omie failures
- Rate limit and auth token per destination
- Idempotency (X-Delivery-ID) and sequence_number on deliveries
- Queues isolated per ERP account
How it works
- Omie API
- Celery tasks
- Retry and dead-letter
- Circuit breaker
- Idempotency
- Sequencing
- Rate limit per destination
- Internal systems via webhook