messagebus alternatives and similar packages
Based on the "Messaging" category
-
NATS Go Client
A lightweight and high performance publish-subscribe and distributed queueing messaging system -
NATS
A lightweight and highly performant publish-subscribe and distributed queueing messaging system. -
Mercure
Server and library to dispatch server-sent updates using the Mercure protocol (built on top of Server-Sent Events). -
Gollum
A n:m multiplexer that gathers messages from different sources and broadcasts them to a set of destinations. -
emitter
Emits events using Go way, with wildcard, predicates, cancellation possibilities and many other good wins. -
mangos
Pure go implementation of the Nanomsg ("Scalable Protocols") with transport interoperability. -
guble
A messaging server using push notifications (Google Firebase Cloud Messaging, Apple Push Notification services, SMS) as well as websockets, a REST API, featuring distributed operation and message-persistence. -
Commander
A high-level event driven consumer/producer supporting various "dialects" such as Apache Kafka. -
jazz
A simple RabbitMQ abstraction layer for queue administration and publishing and consuming of messages. -
rmqconn
RabbitMQ Reconnection. Wrapper over amqp.Connection and amqp.Dial. Allowing to do a reconnection when the connection is broken before forcing the call to the Close () method to be closed.
Do you think we are missing an alternative of messagebus or a related project?
Popular Comparisons
-
messagebusvsmangos
-
messagebusvsCentrifugo
-
messagebusvsstructured pubsub
-
messagebusvszmq4
-
messagebusvsEventBus
|
SaaSHub - Software Alternatives and Reviews
View more from us
|
README
π message-bus
Go simple async message bus.
π ABOUT
Contributors:
Want to contribute ? Feel free to send pull requests!
Have problems, bugs, feature ideas? We are using the github issue tracker to manage them.
π Documentation
For documentation (including examples), visit rafallorenz.com/message-bus
For GoDoc reference, visit godoc.org/github.com/vardius/message-bus
π HOW TO USE
π Benchmark
Time complexity of a Publish method is considered to be linear time O(n). Where n corresponds to the number of subscribers for a given topic.
CPU: 3,3 GHz Intel Core i7
RAM: 16 GB 2133 MHz LPDDR3
β message-bus git:(master) β go test -bench=. -cpu=4 -benchmem
goos: darwin
goarch: amd64
pkg: github.com/vardius/message-bus
BenchmarkPublish-4 4430224 250 ns/op 0 B/op 0 allocs/op
BenchmarkSubscribe-4 598240 2037 ns/op 735 B/op 5 allocs/op
π« Basic example
package main
import (
"fmt"
"sync"
"github.com/vardius/message-bus"
)
func main() {
queueSize := 100
bus := messagebus.New(queueSize)
var wg sync.WaitGroup
wg.Add(2)
_ = bus.Subscribe("topic", func(v bool) {
defer wg.Done()
fmt.Println(v)
})
_ = bus.Subscribe("topic", func(v bool) {
defer wg.Done()
fmt.Println(v)
})
// Publish block only when the buffer of one of the subscribers is full.
// change the buffer size altering queueSize when creating new messagebus
bus.Publish("topic", true)
wg.Wait()
}
π³ Docker service
pubsub - gRPC message-oriented middleware on top of message-bus, event ingestion and delivery system.
π [License](LICENSE.md)
This package is released under the MIT license. See the complete license in the package:
*Note that all licence references and agreements mentioned in the messagebus README section above
are relevant to that project's source code only.