Implement Event Bus for Inter-Archon Communication #5

New Issue

allegro · 2026-04-02T20:06:33Z

allegro commented

2026-04-02 20:06:33 +00:00

Task Description

Create an Event Bus system to enable asynchronous communication between Archon components.

Requirements:

Design pub/sub architecture for internal messaging
Implement event types: CREATED, UPDATED, DELETED, SYNC
Add message persistence layer
Implement retry logic with exponential backoff
Create dead letter queue for failed events
Support event filtering by type and source archon
Write comprehensive tests
Add documentation in docs/event-bus.md

Technical Notes:

Can use Redis, RabbitMQ, or in-memory solution
Must support horizontal scaling
Events should be JSON-serializable

Acceptance Criteria:

Events can be published and subscribed
Failed events go to DLQ after max retries
Documentation is complete
All tests pass

## Task Description Create an Event Bus system to enable asynchronous communication between Archon components. ### Requirements: - [ ] Design pub/sub architecture for internal messaging - [ ] Implement event types: CREATED, UPDATED, DELETED, SYNC - [ ] Add message persistence layer - [ ] Implement retry logic with exponential backoff - [ ] Create dead letter queue for failed events - [ ] Support event filtering by type and source archon - [ ] Write comprehensive tests - [ ] Add documentation in docs/event-bus.md ### Technical Notes: - Can use Redis, RabbitMQ, or in-memory solution - Must support horizontal scaling - Events should be JSON-serializable ### Acceptance Criteria: - [ ] Events can be published and subscribed - [ ] Failed events go to DLQ after max retries - [ ] Documentation is complete - [ ] All tests pass

allegro commented

2026-04-02 20:07:19 +00:00

Worker Assignment

Assigned to: electra-worker-1

Instructions:

Design pub/sub architecture for internal messaging
Implement event types: CREATED, UPDATED, DELETED, SYNC
Add message persistence layer (Redis/RabbitMQ/in-memory)
Implement retry logic with exponential backoff
Create dead letter queue for failed events
Support event filtering by type and source archon
Write tests in tests/test_event_bus.py
Add documentation in docs/event-bus.md
Create PR when complete with reference to this issue

Acceptance Criteria:

Events can be published and subscribed
Failed events go to DLQ after max retries
Documentation is complete
All tests pass

Delegated by Electra (DELEGATOR)

## Worker Assignment **Assigned to:** `electra-worker-1` **Instructions:** 1. Design pub/sub architecture for internal messaging 2. Implement event types: CREATED, UPDATED, DELETED, SYNC 3. Add message persistence layer (Redis/RabbitMQ/in-memory) 4. Implement retry logic with exponential backoff 5. Create dead letter queue for failed events 6. Support event filtering by type and source archon 7. Write tests in `tests/test_event_bus.py` 8. Add documentation in `docs/event-bus.md` 9. Create PR when complete with reference to this issue **Acceptance Criteria:** - Events can be published and subscribed - Failed events go to DLQ after max retries - Documentation is complete - All tests pass --- *Delegated by Electra (DELEGATOR)*

gemini was assigned by allegro

2026-04-05 02:08:20 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: allegro/electra-archon#5