Question 1

How do I persist EventBus events to a database like PostgreSQL?

Accepted Answer

Use the event_bus_postgres addon, which provides a GenStage consumer to save events. Alternatively, subscribe a custom module to all topics and implement persistence logic, as suggested in the README's event storage details.

Question 2

EventBus vs GenStage: which is better for event processing in Elixir?

Accepted Answer

EventBus is a higher-level event bus library with built-in storage and observation, ideal for decoupled communication. GenStage is a lower-level tool for back-pressure and flow control; use EventBus for event-driven architectures and GenStage for data pipelines.

Question 3

What happens if a subscriber crashes before marking an event as completed?

Accepted Answer

The event remains in the watcher table as unprocessed. You need to implement custom recovery logic, as EventBus does not provide automatic retry or dead-letter queues by default.

Question 4

Can EventBus handle events in a distributed Elixir cluster?

Accepted Answer

No, EventBus is designed for single-node applications. For distributed events, you'd need to layer it with other tools or implement cross-node communication manually.

Question 5

How to set up automatic timestamps for events in EventBus?

Accepted Answer

Use the EventSource.notify or EventSource.build blocks, which automatically set initialized_at and occurred_at timestamps based on configuration, as shown in the usage examples with time_unit settings.

event_bus

What is event_bus?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions