|author||Sean Glover <firstname.lastname@example.org>||Tue Dec 27 23:35:30 2022 -0500|
|committer||Sean Glover <email@example.com>||Tue Dec 27 23:35:30 2022 -0500|
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.
Pekko connectors is a fork of Alpakka 4.0.0, 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:
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.
Apache Pekko is governed by the Apache code of conduct. By participating in this project you agree to abide by its terms.
Apache Pekko is available under the Apache License, version 2.0. See LICENSE file for details.
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. If not stated otherwise, the Lightbend subscription does not cover support for Alpakka modules.
Our goal is to improve the stability and test coverage for Alpakka APIs over time.