Skip to content
Alpakka Kafka connector - Alpakka is a Reactive Enterprise Integration library for Java and Scala, based on Reactive Streams and Akka.
Branch: master
Clone or download
szymonm and ennru Add ListenerCallbacks.apply to remove code duplication (#746)
Small refactoring before adding a synchronous listener for rebalance event
Latest commit a8a8268 Mar 20, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github More detailed issue templates (#709) Jan 22, 2019
.travis Build paradox and api docs with sbt-site (#662) Feb 20, 2019
benchmarks/src
core/src/main
docs
project Paradox project-info improvements (#724) Feb 21, 2019
scripts Log to file instead of stdout Oct 1, 2018
testkit/src/main Use JUnit5 (#691) Jan 16, 2019
tests/src AssignmentSpec: Produce end marker to the other partition Mar 20, 2019
.gitignore gitignore .tmpBin Mar 16, 2016
.jvmopts-travis
.scalafmt.conf Add Scalafmt 1.5.1 (#489) Jun 7, 2018
.travis.yml Merge pull request #723 from 2m/wip-latest-jabba-2m Feb 21, 2019
CODE_OF_CONDUCT.md Readme - Welcome to Alpakka (#439) May 7, 2018
CONTRIBUTING.md Add Scalafmt 1.5.1 (#489) Jun 7, 2018
LICENSE
OLD_README.md move documentation for old API to OLD_README.md Sep 9, 2016
README.md Change Scaladex links to alpakka-kafka Nov 29, 2018
RELEASING.md
build.sbt
docker-compose.yml Set Kafka brokers' replication factor for offsets topic (#588) Oct 4, 2018

README.md

Alpakka Kafka Connector scaladex-badge maven-central-badge travis-badge gitter-badge

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 Alpakka project is an open source initiative to implement stream-aware, reactive, integration pipelines for Java and Scala. It is built on top of Akka 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. Akka 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 Alpakka Kafka connector. Which lets you connect Apache Kafka to Akka Streams. It was formerly known as Akka Streams Kafka and even Reactive Kafka.

Akka Stream connectors to other technologies are listed in the Alpakka repository.

Documentation

To keep up with the latest Alpakka releases check out Alpakka releases and Alpakka Kafka connector releases.

Community

You can join these groups and chats to discuss and ask Akka and Alpakka related questions:

  • Forums: discuss.lightbend.com
  • Chat room about Akka and Alpakka: gitter: akka/akka
  • Chat room about Alpakka Kafka connector: gitter: akka/alpakka-kafka
  • Issue tracker: github: akka/alpakka-kafka

In addition to that, you may enjoy following:

The Kafka connector was originally created as Reactive Kafka by SoftwareMill logo.

Contributing

Lightbend is committed to Alpakka and has an Alpakka team working on it.

Contributions are very welcome! The Alpakka team appreciates community contributions by both those new to Alpakka and those more experienced. Alpakka depends on the community to to keep up with the ever-growing number of technologies with which to integrate. Please step up and share the successful Akka Stream integrations you implement with the Alpakka community.

If you find an issue that you'd like to see fixed, the quickest way to make that happen is to implement the fix and submit a pull request.

Refer to the CONTRIBUTING.md file for more details about the workflow, and general hints on how to prepare your pull request.

You can also ask for clarifications or guidance in GitHub issues directly, or in the akka/dev chat if a more real time communication would be of benefit.

Caveat Emptor

Alpakka components 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.

Support for the Alpakka Kafka connector is available via Lightbend subscription.

You can’t perform that action at this time.