Table of Contents

KEFCore: Supported Backends

KEFCore is the Entity Framework Core provider for Apache Kafka™, based on KNet client-side features it allows to use Apache Kafka™ as a distributed database and more: KNet client-side features are also compatible with any broker that implements the Kafka wire protocol.

Kafka wire-protocol compatible brokers

Entity Framework Core provider for Apache Kafka™ use only the standard Apache Kafka™ client APIs: Producer, Consumer, Admin Client, and Kafka Streams. These APIs communicate with the broker exclusively through the Kafka wire protocol.

Any broker that fully implements the Kafka wire protocol is therefore compatible with the following KNet client-side features used from Entity Framework Core provider for Apache Kafka™:

  • Producer and Consumer APIs (KafkaProducer, KafkaConsumer, KNetProducer, KNetConsumer, KNetCompactedReplicator)
  • Admin Client API (KafkaAdminClient)
  • Kafka Streams / KNet Streams SDK (runs entirely embedded in the .NET process; the broker only sees standard topics)

Note on Kafka Streams: Kafka Streams runs entirely embedded within the application process. The broker is not aware of Streams: it only stores the standard topics that Streams creates and manages (state store changelog topics, repartition topics). No server-side Streams support is required from the broker.

Compatible brokers for client-side features

The following brokers declare full or substantial Kafka wire-protocol compatibility and are therefore compatible with all KNet client-side features:

Broker Type Compatibility notes
Apache Kafka™ Self-hosted Reference implementation, full compatibility
Redpanda Self-hosted / Cloud Declares full Kafka wire-protocol compatibility
Amazon MSK Managed Cloud (AWS) Kafka-native managed service, full compatibility
Confluent Platform / Cloud Self-hosted / Cloud Commercial Kafka distribution, full compatibility
Aiven for Apache Kafka™ Managed Cloud (multi-cloud) Kafka-native managed service, full compatibility
IBM Event Streams Self-hosted / Cloud Based on Apache Kafka™, full compatibility
WarpStream Cloud (S3-backed) Kafka-compatible, zero inter-broker network
AutoMQ Self-hosted / Cloud Kafka-compatible, S3-backed cloud-native
Azure Event Hubs Managed Cloud (Azure) Kafka endpoint available; partial compatibility — some Admin API features may not be supported
Apache Pulsar (KoP) Self-hosted Kafka-on-Pulsar translation layer; partial compatibility — verify Admin API and topic configuration support

Important: Entity Framework Core provider for Apache Kafka™ uses the official Apache Kafka™ Java client packages directly through KNet client-side features. Compatibility with Kafka-protocol-compatible brokers is therefore inherited from the Apache Kafka™ client libraries themselves, not from a custom implementation. Any broker compatible with the Apache Kafka™ client is automatically compatible with KNet client-side features.