Provide client side intégration to Kafka with Dekaf
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 196
Description
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Is your feature request related to a problem? Please describe the problem.
Current Kafka intégration rely on Confluent.Kafka that itself rely on librdkafka using interop.
Dekaf is a pure .NET library implementing Kafka protocol client side and introduced 1/1 compatibility mapping with Confluent.Kafka api and config objects.
See https://github.com/thomhurst/Dekaf/issues/2317
### Describe the solution you'd like
An alternative client side intégration that use Dekaf.
### Additional context
_No response_
Contributor guide
Research direction
Start by locating Aspire's existing Confluent.Kafka integration and review Dekaf's compatibility mapping, including issue 2317. Determine the integration entry points, configuration surface, and expected client behavior; done means Aspire offers a documented Dekaf-based alternative without relying on librdkafka.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100