Tubi-related customizations

This repo is a fork of akka/alpakka. The main branch was forked as upstream-main.

Rules for development:

• Always develop against the tubi-main branch, which is the default branch. All PRs are opened against this branch by default.
• To release a version, just tag the version you want to release as vX.Y.Z-tubi-A, where X.Y.Z is the alpakka version and A is the Tubi release version. Publish with codeArtifactPublish.
• To use these versions as dependencies, use "com.tubitv" %% "akka-stream-alpakka-kinesis" % "X.Y.Z-tubi-A" as a dependency instead of the one from Akka.

Contributing back to upstream:

• If you want to contribute back to the Akka repository, cherry-pick your commit to a branch based on upstream-main and open a PR against akka/alpakka/main.

NEVER MERGE tubi-main to upstream-main (the other direction is ok).

---

Alpakka

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 implements 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.

The Akka family of projects is managed by teams at Lightbend with help from the community.

Documentation

• Alpakka reference documentation

• Alpakka Kafka connector reference documentation

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

Community

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

• Forums: discuss.lightbend.com
• Issue tracker: github.com/akka/alpakka/issues

In addition to that, you may enjoy the following:

• The Akka Team Blog
• @akkateam on Twitter
• Questions tagged #alpakka on StackOverflow

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 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. If you're planning to implement a new module within Alpakka, look at our contributor advice.

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

License

Alpakka is licensed under the Business Source License (BSL) 1.1, please see the Akka License FAQ.

Tests and documentation are under a separate license, see the LICENSE file in each documentation and test root directory for details.