As part of the API first approach, the first step is to design these APIs before actually implementing them. Apicurio Studio is an environment which allows one to collaboratively work on API specifications - today this is not a managed service - but will be offered as a managed service in the near future.

Even before the implementation starts, the various stakeholders come together to define the API specs. The API are defined for the existing catalogue service as well.

This designer provides a graphical way of designing all the aspects of an OpenAPI - had different paths, datatypes and canned responses. For instance - <show example here> Which can then be later used to mock out those services.

It also allows you to work in both a graphical way of doing things and also with the source. The OpenAPI can be viewed as both a YAML and a JSON document.

Once the API design is complete, and we have the first version of the API, this can now be published in a schema registry. Red Hat OpenShift Service Registry allows us to publish the OpenAPIs, makes it accessible, and manages the OpenAPI from within the Red Hat’s cloud console

You can upload new artifacts, new versions, view the metadata, download the specs, view documentation and view the content as well. Through Content rules one can validate new versions of the APIs against the existing specs to ensure validity and backward compatibility.

We can also build mocks for the APIs using the same OpenAPIs.

Microcks is a tool which allows one to upload the same OpenAPI spec, and to build mocks for the APIs. This is for use of the teams who will actually consume the APIs and they can use these mocks to develop their pieces of code even before the APIs are completely implemented

Each of the mocks that are created out of the OpenAPI’s examples has its own URL which can be invoked to provide a realistic response. This allows front end and mobile app developers to develop against the OpenAPIs specs without waiting for the final implementation of the backend services.

We use the managed Red Hat OpenShift API Management platform here to publish, manage and secure the backend APIs.

Each API can be configured to be secured using a number of ways. In this case, the APIs are secured with an API key which should be passed through http request header. The OpenShift API Management platform allows you to have various application plans. Developers can subscribe to those APIs and can access APIs through an assigned API key securely. You can monitor the APIs and also track usage

As a developer, you would like to build functionality around the APIs. There is also a Development Portal which is currently under, well, development. You can sign in as a developer here. This developer has already subscribed to the API and is given an API key which should be used in all API calls to ensure the calls are authenticated by the API management platform.

The devportal allows viewing Live documentation as well, which is another view of the OpenAPI specs. Developers can try it out to see what kind of responses they can get back. The developers can also view statistics for their account in a graph format

Red Hat OpenShift Streams for Apache Kafka is a fully hosted and managed Kafka cloud service. This serves the requirement of Globex who did not want to install and maintain a streaming platform. This service can be very easily consumed and used by developers.

There are a number of topics created for Globex. The globex.tracking topic is one which ingests the activity events. This is then consumed by the Recommendation Engine which is a Kafka Streams application which then builds a list of Top 10 most popular products with most user interest.

This is a managed service and security is very important. The service allows fine grained access controls based on user accounts and service accounts. You can define what each account is allowed to do.

With all this tooling in place as part of App modernization, GitOps, Continuous integration, deployment in staging. This means that Business can easily follow progress at different points of building the functionality which you can see here

The new homepage of the Coolstuff store displays the top currently featured products.

The featured projects are displayed as a carousel in the page displaying the paginated list of products. Visitors can drill down to view product details, add products to the cart, view and edit catt, and also like their favourite products

Each of the activities generates a continuous stream of events which is then used to recommend the top 10 products to be featured.

<generate more records now> Kafdrop is a tool through which you can view this continuous stream of events. Kafdrop will point to the managed instance. We can view the topics and messaged easily as part of the development process

The Kafka streams application creates a number of other topics for data aggregation, and pushes the aggregated products list as events into the product-score-aggreated topic