The Event Gateway solution by excellence
⚠️Still under development, it didn't reach v1.0.0 and therefore is not suitable for production use yet.
AsyncAPI Event Gateway (name is subject to change) is the Event Gateway solution by excellence.
Based on traditional API Gateways, it intercepts all incoming messages moving them into a pipeline of middlewares and handlers such as:
- Message validation
- Message manipulation
- Message aggregation
- Message filtering
- Monitoring (including tracing)
It supports all the protocols AsyncAPI supports through bindings.
This Event Gateway is also compatible with the HTTP protocol, natively or through an external provider like Krakend.io.
1. Performance-first while ensuring message delivery
The Event Gateway it's a stateless solution that ensures messages are delivered as fast as possible using a minimal resource footprint. Delivering messages as a top priority means no data loss should happen.
2. Transparent usage.
No change in the user's code is needed. The service acts as a proxy between the client and the final broker(s). Messages infer the protocol based on the shape of the input network packet.
3. Fully configurable.
The service is entirely configurable, and the user can specify the settings for all protocols as well. For example, consumers' and producers' settings.
The service provides an API for uploading AsyncAPI specs, allowing the user to update their message validation, among others, very quickly. It could even be an automated task whenever you update your specs.
The Event Gateway can extend its functionality via middlewares written by the community. A catalog of middlewares made by the community is also available.
The idea is to keep iterating and support all the protocols AsyncAPI supports through bindings.
However, we reduced the scope for the first versions, so we can give support to the most used protocols.
For the first version, only Kafka protocol will be supported.
Install from Docker
Install from pre-compiled binaries
Install from source
- Clone this repository.
make build. The binary will be placed at
Please refer to /docs/config.
Read CONTRIBUTING guide.
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!