Systems don't come alone. In the modern world of microservices and cloud deployment, new components must interact with legacy systems, making integration an important key to success. Reactive Streams give us a technology-independent tool to let these heterogeneous systems communicate without overwhelming each other.
The Apache Pekko Connectors project is an open source initiative to implement stream-aware, reactive, integration pipelines for Java and Scala. It is built on top of Apache Pekko Streams, and has been designed from the ground up to understand streaming natively and provide a DSL for reactive and stream-oriented programming, with built-in support for backpressure. Pekko Streams is a Reactive Streams and JDK 9+ java.util.concurrent.Flow-compliant implementation and therefore fully interoperable with other implementations.
This repository contains the sources for the Apache Pekko Kafka Connector. Which lets you connect Apache Kafka to Pekko Streams.
Pekko connectors to other technologies are listed in the Pekko connectors repository.
The Apache Pekko Kafka Connector is a fork of Alpakka Kafka 3.0.1, prior to the Akka project's adoption of the Business Source License.
TODO add documentation links
You can join these forums and chats to discuss and ask Pekko and Pekko connector related questions:
- GitHub discussions: for questions and general discussion.
- Pekko dev mailing list: for Pekko connectors development discussions.
- GitHub issues: for bug reports and feature requests. Please search the existing issues before creating new ones. If you are unsure whether you have found a bug, consider asking in GitHub discussions or the mailing list first.
The Apache Pekko Kafka Connector was originally created as Reactive Kafka by 
Contributions are very welcome. If you have an idea on how to improve Pekko, don't hesitate to create an issue or submit a pull request.
See CONTRIBUTING.md for details on the development workflow and how to create your pull request.
Pekko Connectors are not always binary compatible between releases. API changes that are not backward compatible might be introduced as we refine and simplify based on your feedback. A module may be dropped in any release without prior deprecation.