You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.NET Aspire shows great promise in simplifying the development of distributed systems using .NET for cloud-native applications. However, the absence of support for Kafka (or even similar technologies such as Azure Event Hubs) poses a significant limitation to its broader adoption in the cloud-native ecosystem.
Kafka is central to a lot of modern architecture. It's used by >80% of the Fortune 100, and unlike other systems where there are a lot of vendor-specific alternatives, it's overwhelmingly the most popular option when you're trying to build an event-driven backbone with data in motion at scale.
I recognize the challenges involved in integrating Kafka support, including the absence of a first-party managed Kafka service on Azure and lack of a comprehensive first-party Kafka.NET client. Despite these hurdles, I believe that supporting Kafka could greatly enhance .NET Aspire's relevance in contemporary cloud-native architectures.
The text was updated successfully, but these errors were encountered:
* Add Aspire.Confluent.Kafka component
Contains APIs for both AddKafkaConsumer and AddKafkaProducer. As well as Kafka Hosting APIs to start a Kafka server container.
Update ConfigurationSchema.json using ConfigSchemaGenerator. Cannot be automated until dotnet/runtime#96652 is fixed, so using a local temporary solution for now.
Temporarily add Kafka OTel Metrics logic here until open-telemetry/opentelemetry-dotnet-contrib#1493 is available to use.
Kafka sample can be found in dotnet/aspire-samples#85.
* Address PR feedback
- Make Kafka Settings Config object non-nullable and not settable from user code.
- Use EventId 1 in Logging
- Log response body in Functional tests
* Adjust the initialization of the Settings Config properties because the type can be created publicly.
Fix#884
---------
Co-authored-by: Eric Erhardt <eric.erhardt@microsoft.com>
.NET Aspire shows great promise in simplifying the development of distributed systems using .NET for cloud-native applications. However, the absence of support for Kafka (or even similar technologies such as Azure Event Hubs) poses a significant limitation to its broader adoption in the cloud-native ecosystem.
Kafka is central to a lot of modern architecture. It's used by >80% of the Fortune 100, and unlike other systems where there are a lot of vendor-specific alternatives, it's overwhelmingly the most popular option when you're trying to build an event-driven backbone with data in motion at scale.
I recognize the challenges involved in integrating Kafka support, including the absence of a first-party managed Kafka service on Azure and lack of a comprehensive first-party Kafka.NET client. Despite these hurdles, I believe that supporting Kafka could greatly enhance .NET Aspire's relevance in contemporary cloud-native architectures.
The text was updated successfully, but these errors were encountered: