zilla VS Java-Quarkus-Reactive-CQRS-EventSourcing

Hi gang, we’re building a multi-protocol, event-native edge/service proxy called Zilla. Zilla can abstract Kafka topics for web apps, IoT clients and microservices through user-defined REST, Server-Sent Events (SSE), MQTT, or gRPC APIs.

Hey folks, we’re working on Zilla, an open-source, event-native API gateway that provides a stateless, multi-protocol interface to Apache Kafka. I’m sharing that we’ve added support for another protocol — gRPC! You can find the full announcement HERE

Hey folks, I’m with Aklivity and we’re working on an open source project called Zilla. Zilla is a multi-protocol, event-driven API gateway that enables apps and services to use standard protocols, such as REST and SSE, to consume and produce Kafka event-streams.

There are projects that work to unify these two technologies so you can get the best of both worlds: https://docs.aklivity.io/zilla/

We’re building an open source event-driven API getaway called Zilla (https://github.com/aklivity/zilla). Zilla natively supports Kafka and enables you to create event-driven REST and SSE APIs that seamlessly expose Kafka topics and services to mobile and web clients.

Here’s a link to the project (it’s called Zilla): https://github.com/aklivity/zilla, and here is also a blog that talks about the differences between system-level and application-level Kafka-REST APIs: https://www.aklivity.io/post/bring-your-own-rest-apis-for-apache-kafka. Additional Zilla docs and getting started guide: https://docs.aklivity.io/zilla/get-started

We recently announced the launch of Zilla(https://github.com/aklivity/zilla), our open-source API Gateway for Apache Kafka. Zilla is designed to expose Kafka topics over various protocols and APIs, including HTTP and REST.

We just launched Zilla (https://github.com/aklivity/zilla) — an open source API gateway for event-streaming and are curious to get some of your thoughts and feedback on the project.

Source code you can find in GitHub repository. The main idea of this project is the implementation of Event Sourcing and CQRS using Java, Quarkus with reactive Vertx, Postgresql and Kafka. Previously have written same articles where implemented the same microservice using Go and EventStoreDB, and Spring,as written before, repeat here, think EventStoreDB is the best choice for event sourcing, but in real life at some projects we usually have business restrictions and for example usage of the EventStoreDB can be not allowed, in this case, think postgres and kafka is good alternative for implementing our own event store. Didn't write in this article about Event Sourcing and CQRS patterns, the best place to read is microservices.io,blog and documentation of this article is very good too, and as written in the previous article, highly recommend Alexey Zimarev "Hands-on Domain-Driven Design with .NET Core" book and also his blog.