Library to make easier to dispatch your outbox-pattern data from database to SQS, SNS and/or HTTP(S) gateways
PostgreSQL storage implementation for oxide-outbox using sqlx
CQRS/ES framework for Rust using Plain Old Rust Structs — append-only events, replay, snapshots, outbox, service bus, and pluggable infrastructure
Transactional outbox pattern primitives for the Hexeract messaging framework
PostgreSQL backend for the Hexeract outbox via deadpool_postgres
SQL backends for the Hexeract outbox via sqlx with postgres, mysql and sqlite feature flags
Core traits and logic for modular transactional outbox pattern in Rust
CQRS/ES framework for Rust using Plain Old Rust Structs — append-only events, replay, snapshots, outbox, service bus, and pluggable infrastructure
Kafka transport implementation for the oxide-outbox
Redis-based idempotency provider for the oxide-outbox
Bidirectional relay binary for pg_tide — bridges outboxes/inboxes with NATS, Kafka, HTTP webhooks, Redis, SQS, RabbitMQ, and more
The 6-dimension Rust messaging framework: opt-in feature flags expose the outbox, bus, mediator and macros families.
The Outboxable Gem is tailored for Rails applications to implement the transactional outbox pattern. It currently only supports ActiveRecord.
A service that uses a relational database inserts messages/events into an outbox table as part of the local transaction.
A Transactional Outbox implementation for ActiveRecord
Transactional outbox pattern implementation in ruby
Twilio API wrapper for Outbox, a generic interface for sending notificatons.
Transactional inbox/outbox, as a Rails engine.
An implementation of transactional outbox pattern to be used with Rails.
Bandwidth API wrapper for Outbox, a generic interface for sending notificatons.
MSG91 API wrapper for Outbox, a generic interface for sending sms notificatons.
Active Record based outbox for Ruby Event Store
Transactional-Outbox for Rails
Even delivering email to the local machine may take too long when you have to send hundreds of messages. ar_mailer allows you to store messages into the database for later delivery by a separate process, ar_sendmail. This fork stores the email in the database for easy inspection and tracking.