How to set up a basic message bus in Go using this library?

The documentation provides a basic example where you create a bus instance, subscribe handlers to topics with `bus.Subscribe()`, and publish messages with `bus.Publish()`. It's designed to be minimal, often requiring just a few lines of code for initial integration.

message-bus vs Go channels: which is better for internal communication?

message-bus is higher-level and ideal for decoupling multiple components with pub/sub patterns across an application, while Go channels are lower-level and better for direct goroutine synchronization. Choose message-bus when you need asynchronous, topic-based messaging without tight coupling.

Does message-bus support wildcard topics or pattern matching?

No, the library uses simple string topics without built-in wildcard or pattern matching support, as indicated in the documentation. You may need to implement topic hierarchies manually for more flexible subscriptions.

How to handle errors in message-bus subscribers?

The library does not provide built-in error handling for subscribers, so you must implement error recovery within your handler functions, such as using panic recovery or logging errors, to prevent application crashes.

Is message-bus thread-safe for concurrent publishing?

Yes, benchmark tests use multiple CPUs, and the library is designed to be thread-safe for concurrent operations, as shown in the performance metrics, making it suitable for high-throughput scenarios.

Can I use message-bus in a microservices architecture?

message-bus is limited to in-process communication, so it's best used within individual microservices for internal decoupling. For inter-service messaging, you'd need a distributed message broker like NATS or RabbitMQ alongside it.

Open-Awesome

messagebus

MITJavaScriptv1.1.5

A simple asynchronous message bus library for Go applications.

Visit Website GitHub

287 stars48 forks0 contributors

What is messagebus?

message-bus is a Go library that implements a simple asynchronous message bus for in-process communication. It allows different parts of an application to communicate via publish-subscribe patterns without tight coupling, solving the need for scalable and maintainable event-driven architectures.

Target Audience

Go developers building applications that require decoupled component communication, such as microservices, event-driven systems, or modular monoliths.

Value Proposition

Developers choose message-bus for its minimalistic design, high performance, and ease of integration, offering a native Go solution without external dependencies for efficient async messaging.

Overview

Go simple async message bus

Use Cases

Best For

Implementing pub/sub patterns in Go applications
Decoupling components in microservices architectures
Building event-driven systems with async processing
Managing in-process communication without external brokers
Creating scalable Go applications with low-latency messaging
Simplifying inter-module communication in modular monoliths

Not Ideal For

Systems requiring distributed messaging across multiple services or nodes
Applications that need persistent message storage to survive crashes
Use cases demanding advanced features like guaranteed delivery or message ordering

Pros & Cons

Pros

High Performance Benchmarks

Benchmark results show publish operations at 250 ns/op with zero allocations, ensuring low latency and efficient memory usage for async handling.

Simple API Design

Offers an intuitive pub/sub interface that makes it easy to decouple components without complex setup, as highlighted in the documentation.

Zero External Dependencies

A pure Go library that avoids reliance on external brokers, simplifying deployment and keeping the dependency graph clean, per the project philosophy.

Comprehensive Documentation

Includes detailed examples and guides on the project website, facilitating quick integration and reducing the learning curve.

Cons

In-Process Limitation

Only supports messaging within a single Go process, so it cannot handle cross-service communication without additional tooling, limiting its use in distributed architectures.

No Built-in Persistence

Messages are handled in-memory and not persisted, leading to data loss on application failure, which is a risk for systems with high reliability requirements.

Minimal Feature Set

Focuses on core pub/sub without advanced capabilities like message ordering, dead-letter queues, or built-in error handling, requiring custom implementations for complex scenarios.

Frequently Asked Questions

Related Projects

Asynq

Simple, reliable, and efficient distributed task queue in Go

Stars13,546

Forks972

Last commit1 month ago

sarama

Sarama is a Go library for Apache Kafka.

Stars12,501

Forks1,851

Last commit18 hours ago

Centrifugo

Scalable real-time messaging server in a language-agnostic way. Self-hosted alternative to Pubnub, Pusher, Ably, socket.io, Phoenix.PubSub, SignalR. Set up once and forever.

Building event-driven applications the easy way in Go.

Stars9,810

Forks500

Last commit2 months ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub