Chris Phillips’ Blog - API, Integration and Governance

be back soon

This blog has not been updated for a while as I am sitting by a pool with no laptop or iPad.

Just an iPhone SE and a broken keybaord

During npm install you my recieve an Undefined symbols for architecture x86_64: like below. In order to get around this you must install librdkafka.

“IBM Event Streams is a high-throughput message bus built with Apache Kafka. It is optimized for event ingestion into IBM Cloud and event stream distribution between your services and applications” Taken from https://cloud.ibm.com/catalog/services/event-streams

Today I sat down and installed Bind9 to act as a local DNS server. As this took me far to long I have attached a config similar to my home one explaining the changes I made from the default.

Today I updated the API Connect WhitePaper to 1.0.9 with some very minor changes. This can be downloaded from the same location as before, https://www.ibm.com/downloads/cas/30YERA2R

When designing your enterprise API Connect environment there are a number of different patterns that can be followed. In the API Connect WhitePaper I present two common patterns. This article is a third pattern that I will propose to put into a future release of the WhitePaper.

Helm is the de facto standard for deploying to Kubernetes. OpenShift does not ship with helm but instead provides their own system called Templates. Thus far I have never used OpenShift Templates and so I focus on helm. This article does not go through the differences but just shows how to get helm v2 up and running.

VMWARE ESXI is a free VMWare hosting system. The primary differences between this and the full vSphere are support, limit to one host and no of supported cpus.

TLDR : Use (Rufus)[https://rufus.ie] on Windows not DD or anything else.

WARNING: What is covered in this article is not supported. It is recommended that this is only used for a POC where Helm 2.x cannot be used.