Google Git
Sign in
apache / incubator-pekko-connectors / refs/heads/seglo/artifact-id-rename
commit93c09682698217e340c60da591f30d2320b96034[log] [tgz]
authorSean Glover <sean@seanglover.com>Tue Dec 27 23:35:30 2022 -0500
committerSean Glover <sean@seanglover.com>Tue Dec 27 23:35:30 2022 -0500
treef6df37f4939bf78d66fcf80fef40beb79b14f8ab
parented276f6eb60bdbabd649a7ebff8c17732237d84d [diff]
cleanup
2 files changed
tree: f6df37f4939bf78d66fcf80fef40beb79b14f8ab
  1. .github/
  2. amqp/
  3. avroparquet/
  4. aws-event-bridge/
  5. awslambda/
  6. azure-storage-queue/
  7. cassandra/
  8. couchbase/
  9. csv/
  10. csv-bench/
  11. doc-examples/
  12. docs/
  13. dynamodb/
  14. elasticsearch/
  15. file/
  16. ftp/
  17. geode/
  18. google-cloud-bigquery/
  19. google-cloud-bigquery-storage/
  20. google-cloud-pub-sub/
  21. google-cloud-pub-sub-grpc/
  22. google-cloud-storage/
  23. google-common/
  24. google-fcm/
  25. hbase/
  26. hdfs/
  27. huawei-push-kit/
  28. influxdb/
  29. ironmq/
  30. jms/
  31. json-streaming/
  32. kinesis/
  33. kudu/
  34. mongodb/
  35. mqtt/
  36. mqtt-streaming/
  37. mqtt-streaming-bench/
  38. orientdb/
  39. pravega/
  40. project/
  41. reference/
  42. s3/
  43. scripts/
  44. simple-codecs/
  45. slick/
  46. sns/
  47. solr/
  48. spring-web/
  49. sqs/
  50. sse/
  51. testkit/
  52. text/
  53. udp/
  54. unix-domain-socket/
  55. xml/
  56. .asf.yaml
  57. .gitattributes
  58. .gitignore
  59. .jvmopts
  60. .scala-steward.conf
  61. .scalafmt.conf
  62. build.sbt
  63. CONTRIBUTING.md
  64. contributor-advice.md
  65. docker-compose.yml
  66. LICENSE
  67. README.md
  68. RELEASING.md
README.md

Alpakka scaladex-badge maven-central-badge CI on GitHub actions

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.

Documentation

TODO add documentation links

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

Community

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.

Contributing

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.

Code of Conduct

Apache Pekko is governed by the Apache code of conduct. By participating in this project you agree to abide by its terms.

License

Apache Pekko is available under the Apache License, version 2.0. See LICENSE file for details.

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.