Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Amazon AWS kinesis support #32

Open
gianluca-sabena opened this issue Dec 11, 2024 · 2 comments
Open

Add Amazon AWS kinesis support #32

gianluca-sabena opened this issue Dec 11, 2024 · 2 comments

Comments

@gianluca-sabena
Copy link

Use uForwarder to abstract the back-end

In this scenario I propose to add a second back-end system: Amazon AWS Kinesis

I see different approaches:

  • add AWS Kinesis in this repository as a first class back-end
  • create a AWS Kinesis module in a separate repository limited to the back-end part (usable as a plugin/module to this project)
  • fork the repository (I prefer to avoid this solution because it duplicates a lot of code)

Thank you

@yangy0000
Copy link
Collaborator

Thanks for the proposal. I'm not very familiar with AWS Kinesis. Could you put down a rough proposal for the change?

@ericzhifengchen
Copy link
Contributor

ericzhifengchen commented Jan 2, 2025

Kinesis is AWS offer of kafka, there are similar concept but there is no API compatibility. Uforwarder is open to support different types of streaming backend if there is actual use case.
If we want to support different types of back-end. My proposed direction is to make different back-end plug-able into uForwarder. of course it will need some refactoring. Kafka and Kinesis can be two different implementations of backend.
Is there actual plan to use uforwarder on kinesis?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants