Question 1

How do I handle events asynchronously with Bus?

Accepted Answer

Since Bus delivers events synchronously, you must implement async processing within handlers—e.g., by spawning goroutines or pushing to channels. The README strongly recommends this but leaves the concurrency strategy to you.

Question 2

Bus vs. Google Pub/Sub for Go event handling?

Accepted Answer

Bus is for in-process, internal decoupling within a Go app, offering zero-allocation performance. Google Pub/Sub is a cloud service for distributed, cross-service messaging. Choose Bus for internal components; use external brokers for scalable, multi-service architectures.

Question 3

Can Bus be used for event sourcing or CQRS?

Accepted Answer

No, Bus lacks built-in persistence, replay, or snapshot features. It's designed for transient internal events, so you'd need to integrate external storage for event sourcing, making it less suitable out-of-the-box.

Question 4

How to test event-driven code with Bus?

Accepted Answer

Test by mocking the Bus instance or using dependency injection to isolate handlers. Since events are synchronous, you can capture emitted events in tests, but ensure handlers are decoupled for unit testing.

Question 5

What's the performance cost of regex matchers in Bus?

Accepted Answer

Regex matching adds overhead; for high-throughput systems, use simple patterns or pre-compile regexes. Bus allows flexibility, but optimize matchers to avoid bottlenecks in critical paths.

Question 6

Is Bus thread-safe for concurrent emits?

Accepted Answer

Yes, the package is designed for safe concurrent use in Go, but always check documentation for guarantees. Benchmarks imply it handles concurrency, but implement proper synchronization in handlers if needed.

Bus

What is Bus?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions