A customer asked me recently how to setup multiple API gateways work in different locations/configurations while still being controlled from a centralized API Management deployment.

Today, I will explore another way to process content and emit data to Kafka environments, regardless of its complexity.

In my previous blog, I discussed about Red Hat Single Node Openshift and how to extend executing applications in a distributed computing framework. I will explore IBM Business Workflow Services in a Single Node Openshift deployment in this blog.

I had a discussion a few weeks ago with a client who wanted to mask error code and messages to avoid exposing internal information about backend services, such as the type of the error or service version.

I've been lately exploring Red Hat Single Node Openshift. It is a deployment option announced by Red Hat in 2021, aiming to support applications that won't require extensive hardware footprints, for example, edge computing.

You might end up using several Apache Kafka vendors/clusters to serve various projects in your organization, and now you plan to centralize some ..