outboxer alternatives and similar packages
Based on the "Distributed Systems" category.
Alternatively, view outboxer alternatives based on common mentions on social networks and blogs.
-
Nomad
Nomad is an easy-to-use, flexible, and performant workload orchestrator that can deploy a mix of microservice, batch, containerized, and non-containerized applications. Nomad is easy to operate and scale and has native Consul and Vault integrations. -
go-zero
go-zero is a web and rpc framework written in Go. It's born to ensure the stability of the busy sites with resilient design. Builtin goctl greatly improves the development productivity. [Moved to: https://github.com/zeromicro/go-zero] -
rpcx
Best microservices framework in Go, like alibaba Dubbo, but with more features, Scale easily. Try it. Test it. If you feel it's better, use it! ๐๐๐ฏ๐ๆ๐๐ฎ๐๐๐จ, ๐๐จ๐ฅ๐๐ง๐ ๆ๐ซ๐ฉ๐๐ฑ! build for clound! -
ringpop-go
Scalable, fault-tolerant application-layer sharding for Go applications -
KrakenD
Ultra performant API Gateway with middlewares. A project hosted at The Linux Foundation -
dragonboat
A feature complete and high performance multi-group Raft library in Go. -
emitter-io
High performance, distributed and low latency publish-subscribe platform. -
Dkron
Dkron - Distributed, fault tolerant job scheduling system https://dkron.io -
glow
Glow is an easy-to-use distributed computation system written in Go, similar to Hadoop Map Reduce, Spark, Flink, Storm, etc. I am also working on another similar pure Go system, https://github.com/chrislusf/gleam , which is more flexible and more performant. -
gleam
Fast, efficient, and scalable distributed map/reduce system, DAG execution, in memory or on disk, written in pure Go, runs standalone or distributedly. -
Olric
Distributed in-memory data structure store. It can be used both as an embedded Go library and as a language-independent service. -
hprose
Hprose is a cross-language RPC. This project is Hprose for Golang. -
go-doudou
go-doudou๏ผdoudou pronounce /dษudษu/๏ผis a gossip protocol and OpenAPI 3.0 spec based decentralized microservice framework. It supports monolith service application as well. Currently, it supports RESTful service only. ไธญๆๆๆกฃๅฐๅ๏ผhttps://go-doudou.unionj.cloud -
go-health
Library for enabling asynchronous health checks in your service -
resgate
A Realtime API Gateway used with NATS to build REST, real time, and RPC APIs, where all your clients are synchronized seamlessly. -
arpc
More effective network communication, two-way calling, notify and broadcast supported. -
go-sundheit
A library built to provide support for defining service health for golang services. It allows you to register async health checks for your dependencies and the service itself, provides a health endpoint that exposes their status, and health metrics. -
sleuth
A Go library for master-less peer-to-peer autodiscovery and RPC between HTTP services -
Maestro
Take control of your data, connect with anything, and expose it anywhere through protocols such as HTTP, GraphQL, and gRPC. -
celeriac
Golang client library for adding support for interacting and monitoring Celery workers, tasks and events. -
drmaa
Compute cluster (HPC) job submission library for Go (#golang) based on the open DRMAA standard. -
go-pdu
Parallel Digital Universe - A decentralized social networking service -
flowgraph
Flowgraph package for scalable asynchronous system development -
dynatomic
Dynatomic is a library for using dynamodb as an atomic counter
Less time debugging, more time building
Do you think we are missing an alternative of outboxer or a related project?
Popular Comparisons
README
Outboxer
Outboxer is a go library that implements the outbox pattern.
Getting Started
Outboxer was designed to simplify the tough work of orchestrating message reliabilty. Essentially we are trying to solve this question:
How can producers reliably send messages when the broker/consumer is unavailable?
If you have a distributed system architecture and especially is dealing with Event Driven Architecture, you might want to use outboxer.
The first thing to do is include the package in your project
go get github.com/italolelis/outboxer
Initial Configuration
Let's setup a simple example where you are using RabbitMQ
and Postgres
as your outbox pattern components:
ctx, cancel := context.WithCancel(context.Background())
defer cancel()
db, err := sql.Open("postgres", os.Getenv("DS_DSN"))
if err != nil {
fmt.Printf("could not connect to amqp: %s", err)
return
}
conn, err := amqp.Dial(os.Getenv("ES_DSN"))
if err != nil {
fmt.Printf("could not connect to amqp: %s", err)
return
}
// we need to create a data store instance first
ds, err := postgres.WithInstance(ctx, db)
if err != nil {
fmt.Printf("could not setup the data store: %s", err)
return
}
defer ds.Close()
// we create an event stream passing the amqp connection
es := amqpOut.NewAMQP(conn)
// now we create an outboxer instance passing the data store and event stream
o, err := outboxer.New(
outboxer.WithDataStore(ds),
outboxer.WithEventStream(es),
outboxer.WithCheckInterval(1*time.Second),
outboxer.WithCleanupInterval(5*time.Second),
outboxer.WithCleanUpBefore(time.Now().AddDate(0, 0, -5)),
)
if err != nil {
fmt.Printf("could not create an outboxer instance: %s", err)
return
}
// here we initialize the outboxer checks and cleanup go rotines
o.Start(ctx)
defer o.Stop()
// finally we are ready to send messages
if err = o.Send(ctx, &outboxer.OutboxMessage{
Payload: []byte("test payload"),
Options: map[string]interface{}{
amqpOut.ExchangeNameOption: "test",
amqpOut.ExchangeTypeOption: "topic",
amqpOut.RoutingKeyOption: "test.send",
},
}); err != nil {
fmt.Printf("could not send message: %s", err)
return
}
// we can also listen for errors and ok messages that were send
for {
select {
case err := <-o.ErrChan():
fmt.Printf("could not send message: %s", err)
case <-o.OkChan():
fmt.Printf("message received")
return
}
}
Features
Outboxer comes with a few implementations of Data Stores and Event Streams.
- [Postgres DataStore](postgres/)
- [MySQL DataStore](mysql/)
- [SQLServer DataStore](sqlserver/)
- [AMQP EventStream](amqp/)
- [Kinesis EventStream](kinesis/)
Contributing
Please read [CONTRIBUTING.md](CONTRIBUTING.md) for details on our code of conduct, and the process for submitting pull requests to us.
License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details
*Note that all licence references and agreements mentioned in the outboxer README section above
are relevant to that project's source code only.