-
Notifications
You must be signed in to change notification settings - Fork 107
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
Maybe support Kafka abstraction ? #96
Comments
Is your thought to support the Kafka protocol in the server or provide a high-level client that allows switching between Kafka and Liftbridge? Supporting the Kafka protocol would be really neat and would make adoption/migration really easy. My concern with that is there might be some impedance mismatch / leaky abstraction since, while conceptually similar, it's not an exact mapping and Kafka supports some features that Liftbridge doesn't currently. Providing a high-level wrapper that implements a lowest common denominator API between Liftbridge and Kafka would be easier. I think this is what you're suggesting? I also have plans to implement a Kafka bridge for Liftbridge, which would be a Kafka connector that maps topics in Kafka to streams in Liftbridge. This would allow Kafka users to start migrating to Liftbridge incrementally. |
I agree about the impedance mismatch. For me my use case is CDC from Cockroach dB and Yugabtye. These and tidb are pretty common Google spanner like databases. Of course there are probably 1000's of other systems that push to Kafka out there too for which liftbridge could offer a lifeline for where you don't want java. |
It would be super cool if Liftbridge could support the Kafka wire protocol. Adoption would become so much easier. I understand there could be feature imparity initially, but the initial development efforts could be to bridge precisely that. Many like myself find Liftbridge as a Kafka alternative after all. |
Closing this for now as there are currently no plans to support the Kafka protocol. |
Saw this https://github.com/matrix-org/naffka/blob/master/naffka.go
Its a golang lib wrapping samara, but it got me thinking about the idea of allowing golang devs to easily try Kafka or Liftbridge via a unified API.
See here for Context:
https://github.com/matrix-org/dendrite/search?q=naffka&type=Issues
The text was updated successfully, but these errors were encountered: