search

akka / alpakka

Alpakka is a Reactive Enterprise Integration library for Java and Scala, based on Reactive Streams and Akka.
https://doc.akka.io/libraries/alpakka/current/
Other
1.26k stars 645 forks source link

Clarify introduction in documentation #58

Closed patriknw closed 5 years ago

patriknw commented 8 years ago

What is required of an Alpakka connector?

The connectors in the alpakka repository must have an Akka Streams api (for java and scala). External connectors must have Akka Streams or Reactive Streams api.

skhatri commented 8 years ago

Hello Patrik, Would also be good to specify what you would want to take as part of core alpakka components and what you would like to see as external contributions.

Also, will you have a "core" module with ref implementation of some EAI Patterns, much like Camel's.

patriknw commented 8 years ago

Would also be good to specify what you would want to take as part of core alpakka components and what you would like to see as external contributions.

The purpose of external connectors is if the connector is maintained in another github repository.

Otherwise it can be accepted as core Alpakka component if it has an Akka Streams api and is considered useful and in scope of the integration domain.

Also, will you have a "core" module with ref implementation of some EAI Patterns, much like Camel's.

Yes, that is the purpose of the currently empty http://developer.lightbend.com/docs/alpakka/latest/patterns.html section of the documentation.

A pattern can be a GraphStage or combination of existing stages exposed as a Flow or other shape. It can also be just documentation of how to solve a specific integration scenario.

ennru commented 5 years ago

With the current state of Alpakka it is quite well defined what is required from an Alpakka connector.