Trigger a Microservice with an Event
Trigger a microservice to run when an event is published into SAP BTP, Kyma runtime.
Overview
You will learn
- How to trigger a microservice with an event
Prerequisites
Prerequisites
kubectlconfigured to kubeconfig downloaded from SAP BTP, Kyma runtime- Eventing and NATS modules enabled
- Kyma Eventing backend configured
- Deploy a Go PostgreSQL API Endpoint in SAP BTP, Kyma Runtime tutorial completed
- Deploy the SAPUI5 Frontend in SAP BTP, Kyma Runtime tutorial completed
- Deploy the Commerce Mock Application in SAP BTP, Kyma Runtime tutorial completed
Steps
Intro
This tutorial relies on the Commerce mock application to publish events into SAP BTP, Kyma runtime. After binding the commerce mock application to the dev namespace, we will create a service instance of the SAP Commerce Cloud - Events. The service instance will allow for any microservice or lambda function within the dev namespace to subscribe to these events by defining an event subscription. The subscription pairs an event source, the commerce mock application, and the event type, order.created, to a subscriber which in this case will be the Go PostgreSQL API microservice.
Choose the Code button and choose one of the options to download the code locally, or simply run the following command using your CLI at your desired folder location:
Shell/Bashgit clone https://github.com/SAP-samples/kyma-runtime-extension-samples
Open the
api-postgresql-godirectory in your local editor.Explore the content of the sample.
Within the
internal/api/events.gofile you can find the code that handles the consumption of the event data. This code expects to receive a JSON payload containing anorderCode. This function is exposed on the path/orderCodeEvent, which is defined incmd/api/main.go.Within the
k8sdirectory you can find theevent.yamlfile containing the event subscription definition which defines how an event will be consumed. The fields of interest include the following which would have to be altered if a different namespace or application name was used:
| Property | Description | Value |
|---|---|---|
| spec.filter.filters.eventType.value | The event source and version to subscribe to | sap.kyma.custom.mp-commerce-mock.order.created.v1 |
| spec.sink | The URI endpoint of the service that receives the event | http://api-postgresql-go.dev.svc.cluster.local:80/orderCodeEvent |
In this step, you will define an event subscription used to create an event subscriber. This allows you to specify that your api-postgresql-go API application, by referencing its service, should receive the payload of the order.created event.
Apply the subscription by running the following command in the CLI:
Shell/Bashkubectl -n dev apply -f ./k8s/event.yamlVerify that the subscription was created successfully by running this command:
Shell/Bashkubectl get subscription api-postgresql-go-event-sub -n dev -o yamlAfter the event subscription definition, find a status object indicating the status of the related resources:
YAMLstatus: conditions: - lastTransitionTime: "2021-05-06T14:54:50Z" reason: NATS Subscription active status: "True" type: Subscription active emsSubscriptionStatus: {} ready: true
With the configuration steps completed, you can now test the scenario to validate that it is working as intended.
Open the mock application in the browser by choosing Discovery and Network > API Rules from the menu.
Choose the Host entry for the commerce-mock APIRule to open it in the browser. This URL should be similar to:
https://commerce-mock.*******.kyma.ondemand.comChoose the Remote APIS tab.

Test the Scenario Choose the SAP Commerce Cloud - Events option.
For the Event Topics, choose order.created.v1.
Modify the
orderCodevalue as desired and choose Send Event.
Test the Scenario In Kyma dashboard, choose Discovery and Network > API Rules from the menu.
Choose the Host entry for the fe-ui5-postgresql APIRule to open the application in the browser. This should be similar to:
https://fe-ui5-postgresql.*******.kyma.ondemand.comYou should now see the data received by the event as shown below:

Test the Scenario
Resources
Discussion
Share feedback on this tutorial or join the conversation in SAP Community.