EventRelay is a simple to use event storage and streaming platform.
- Foster a dynamic and engaged community and ecosystem.
- Deliver an exceptional developer experience.
- Facilitate minimal production administration.
Checkout Getting Started to get EventRelay setup locally.
After you have it setup locally take a look at Up and Running to publish your first event.
Subscribe to Postgres change events and stream them directly into EventRelay via a simple config.
An Elixir-based authorization package that generates an audit log and can optionally transmit it to EventRelay.
EventRelay allows your applications to both publish and consume events through a GRPC API. It employs a pull-based approach to event streaming, akin to projects like Kafka.
Utilize deliver once events to create worker queues via the GRPC API
Integrate EventRelay seamlessly into your debugging process by sending events in the same locations where you would typically log debug information. You are encouraged to log as much context to the event as possible because you never know in the future what might be importent. EventRelay enables you to easily filter and search events, aiding in the resolution of issues within your application.
Effortlessly send events to EventRelay and define your desired metrics.
Collect first party data and make data driven decisions.
Leverage EventRelay to record events every time you need to track user actions on specific resources within your system.
EventRelay includes built-in webhook support, eliminating the need to concern yourself with implementing retry logic or other complexities associated with sending POST requests.
Whether you're implementing a notification system, a chat application, or simply updating metrics on a dashboard, EventRelay effortlessly manages all aspects of websocket communication for you.
If you have changes in mind that are significant or potentially time consuming, please open a RFC-style PR first, where we can discuss your plans first. We don't want you to spend all your time crafting a PR that we ultimately reject because we don't think it's a good fit or is too large for us to review. Not that we plan to reject PRs in general, but we have to be careful to balance features with maintenance burden, or we will quickly be unable to manage the project.
Checkout the GitHub Project Board.