onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
PackagePackagetypeA library you install and call yourself.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →

com.sap.cds:cds-feature-kafka

A CAP Java feature that connects a CAP messaging service to Apache Kafka for intra-application messaging, through the Apache Kafka client library rather than a managed SAP messaging service.

Connects a CAP messaging service to Apache Kafka for intra-application messaging, one of the optional application features that build on the CAP Java runtime. It ships as a Maven dependency and pulls in the Apache Kafka client library to talk to a Kafka broker directly, rather than through a managed SAP messaging service. Beyond the one line in SAP's own module list, capire does not document configuration or behaviour specific to this feature.

Homepage
Docs

Facts

LicenceSAP DEVELOPER LICENSE AGREEMENT for CAP

Where it sits

Lives in
CAP
Provides
Event MeshCAPEvent MeshcapabilityEmitting and consuming business events across systems through brokers, including subscriptions and mapping application events to broker topics. Work that must survive a request, including deferred processing and retries, belongs to [async processing](capability:async-processing).
Flavors
Java
Optional
Apache KafkaApache Kafkaoutside the atlasA messaging service is configured to use Apache Kafka for intra-application messaging.message broker

What it declares

Every artifact

Type
Package
Origin
By SAP
Runtime
Java

As a package

Where it runs
does not say
Distributed through
does not say

Tasks this contributes to1Beta

Event Mesh1
Receive messages from an Apache Kafka topicRecords that another system writes to a topic on an Apache Kafka cluster reach a handler in the application, which processes each one as an event.Node.js, JavaAssessed, not knownbroker client
What it does

SAP's list of CAP Java modules gives this feature one line, intra-application messaging with Apache Kafka, and its POM depends on the Apache Kafka client library. capire's Java messaging page documents Maven dependencies and a kind for SAP Event Mesh, SAP Cloud Application Event Hub, advanced event mesh and Redis, and none for Kafka. Whether the feature subscribes to a topic that another system writes to, and how it is configured to do so, is not documented.

Remaining work

Not established. The configuration would have to be read out of the module itself.

All options on the Event Mesh page →

Connections2

Where it sits in your app

Download
Your CAP applicationdocumentedmay needif A messaging service isconfigured to use Apache Kafkafor intra-application messagingApache Kafka, systemApache Kafkasystemcom.sap.cds:cds-feature-kafka, modulecom.sap.cds:cds-feat…
SAPnot SAP's, or the project's ownunder a condition

Others providing19

Compare all 20 on the Event Mesh page →
Event Mesh
  1. SAP Integration Suite, advanced event meshEvent streaming and management platform in Integration Suitefrom BTP/BAIP
  2. SAP Cloud Application Event HubDistributes business events between SAP cloud applicationsfrom BTP/BAIP
  3. Event MeshManaged queues and topics over AMQP, MQTT and RESTfrom BTP/BAIP
  4. SAP Integration Suite, Event MeshEvent broker inside SAP Integration Suitefrom BTP/BAIP
  5. com.sap.cds:cds-feature-advanced-event-meshCAP Java plugin for SAP Integration Suite, advanced event meshfrom CAP
  6. com.sap.cds:cds-feature-enterprise-messagingConnects CAP Java messaging to SAP Event Meshfrom CAP
  7. com.sap.cds:cds-feature-event-hubConnects CAP Java messaging to SAP Cloud Application Event Hubfrom CAP
  8. com.sap.cds:cds-feature-redisBeta connector from CAP Java messaging to Redis Pub/Subfrom CAP
  9. com.sap.cds:cds-services-bomMaven bill of materials pinning CAP Java module versionsfrom CAP
  10. @cap-js/advanced-event-meshCAP integration with SAP Integration Suite advanced event meshfrom CAP
  11. @cap-js/asyncapiExports AsyncAPI documents for a CAP service's eventsfrom CAP
  12. @cap-js/event-brokerConsumes events from SAP Cloud Application Event Hub in CAPfrom CAP
  13. cds-kafkaKafka adapter exposing topics as a CDS messaging servicefrom CAP
  14. cesar-sap/abap_kafka_rest_proxyABAP connector to Kafka through the Confluent Kafka REST Proxyfrom ABAP
  15. cds-event-monitoringStores, browses and resends messages a CAP service receivesfrom CAP
  16. gregorwolf/AWS_SNS4ABAPICF handler receiving Amazon SNS notifications in an ABAP systemfrom ABAP
  17. INVIXO/abapMQMQTT 3.1.1 client implemented in ABAPfrom ABAP
  18. MQBAMQTT publish/subscribe in ABAP with an external broker bridgefrom ABAP
  19. @sap/cdsCAP Node.js runtimefrom CAP

Details

Sources1
Added by handdiscovered herechecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesjava
discovered viaAdded by hand
first seen in the atlas
ecosystem and domaincap, integration-and-messaging
Flavors1
Java
“Kafka Messaging feature for CDS Services Java” — com.sap.cds:cds-feature-kafka — POM (5.1.1)checked
History in the atlas2
  1. Connects a CAP messaging service to Apache Kafka for intra-application messaging, using the Kafka client library directly rather than a managed SAP broker.
  2. First seen.
For your agent
Ref
artifact:cap-java-cds-feature-kafka
JSON
/artifacts/cap-java-cds-feature-kafka.json
MCP
Connecting an agent