Kyma Eventing Subscription
The concept name was not provided and cannot be determined from the available source snippets. The sources cover topics such as managing subscriber workload with Max-In-Flight, subscribing to multiple event types, triggering microservices with events, and using Redis in SAP BTP, Kyma Runtime, but no specific concept is identified for definition. Please provide the concept name so an accurate definition can be written.
Tutorials that teach this
Docs explaining this concept
Prerequisites
- Concept Kyma Eventing NATS Backend The Kyma Eventing NATS backend is the messaging infrastructure used by the Kyma Eventing module to route and deliver events within a Kyma cluster, powered by the NATS messaging system. Developers rely on it to enable event-driven communication between services and functions deployed on Kyma. To ensure reliable event processing, operators can verify the health of this backend by checking [NATS module readiness and connectivity](https://help.sap.com/docs/btp/sap-business-technology-platform/8cdf63e7525444ceb951973aea78494b?locale=en-US&state=PRODUCTION&version=Cloud) using general diagnostics procedures.
- Concept Kyma Module Management The concept name was not provided, but based on the sources, the most prominent concept is **Kyma Modules**. With [Kyma's modular approach](https://help.sap.com/docs/btp/sap-business-technology-platform/db6b63f8a36543d985dd0dfa641273bb?locale=en-US&state=PRODUCTION&version=Cloud), developers can install only the modules they need instead of a predefined set of components. To use a Kyma module, a developer must first add it using [Kyma Dashboard](https://help.sap.com/docs/btp/sap-business-technology-platform/482ae2f53fa64568af28ba1349f5836c?locale=en-US&state=PRODUCTION&version=Cloud) or other available tooling. Modules can also be set to a managed or unmanaged state, giving developers control over how each module is maintained within SAP BTP, Kyma runtime.
- Concept Kyma APIRule Creation and Exposure The concept name provided is "undefined," and the available sources do not supply a clear, specific definition for a named SAP developer concept. Based on the sources, which cover topics such as Wildcard Host, Short Host Name, and deploying workloads in the [Kyma environment](https://help.sap.com/docs/btp/sap-business-technology-platform/fe4ba5b46f794037a4aee13df9df2d3c?locale=en-US&state=PRODUCTION&version=Cloud), no single coherent concept labeled "undefined" can be grounded. A developer uses an [APIRule](https://help.sap.com/docs/btp/sap-business-technology-platform/dec7a0b1573c474293d7e36412a4b9a8?locale=en-US&state=PRODUCTION&version=Cloud) in SAP BTP, Kyma runtime to configure routing and expose services, with options such as wildcard hostnames to route traffic from matching subdomains or short host names to simplify configuration.
- Concept Kyma Environment The concept name was not provided, so a precise definition cannot be produced from the available sources. Based on the source snippets, the **Kyma environment** is a platform-as-a-service offering within [SAP Business Technology Platform (SAP BTP)](https://help.sap.com/docs/btp/sap-business-technology-platform/15547f7e7ecd47ee9fa052b0e18c7b0a?locale=en-US&state=PRODUCTION&version=Cloud) that allows developers to build, extend, and run applications and services. It supports the consumption of SAP BTP services and uses availability zones to provide resilience and high availability for workloads.
- Concept NATS JetStream NATS JetStream is the persistence layer built into the NATS message-oriented middleware, enabling developers to store, replay, and reliably deliver messages beyond the fire-and-forget model of core NATS. On SAP BTP, developers interact with it through the [NATS Module](https://help.sap.com/docs/btp/sap-business-technology-platform/2c504f5391504b44800aa02c7fafb39f?locale=en-US&state=PRODUCTION&version=Cloud), which provides tooling to manage and configure the underlying NATS infrastructure.
- Concept Kyma Eventing Module The [Eventing module](https://help.sap.com/docs/btp/sap-business-technology-platform/07b2d1db518b441780d1ea981eb77bb9?locale=en-US&state=PRODUCTION&version=Cloud) enables event-driven communication between applications in a Kyma environment. Developers use it to publish and subscribe to events, choosing between two supported backends: [NATS or SAP Event Mesh](https://help.sap.com/docs/btp/sap-business-technology-platform/08dfcdcaf4ff4914b70c8173731a9188?locale=en-US&state=PRODUCTION&version=Cloud). The NATS backend relies on the NATS module, which manages and configures the message-oriented middleware layer underlying event delivery.
- Concept Event-Driven Microservice Triggering The concept name was not provided, so a specific definition cannot be written. Please supply a valid SAP developer concept name along with relevant source snippets that describe it, so an accurate and grounded definition can be produced.
- Concept kubectl apply with YAML Manifests The concept provided is `undefined`, and the single source snippet discusses a troubleshooting symptom related to a missing Resource CR in a cluster — it does not define or describe a distinct SAP developer concept. There is insufficient grounded information to write a valid reference definition.
- Concept Kyma External System Integration The concept name is missing or undefined, and the provided sources do not contain enough specific detail to identify or define a particular SAP developer concept. A valid concept name and richer source snippets are required to produce an accurate definition.
- Concept Kubernetes Basics