Helping your business department untangle the IT spaghetti This is a blog I wrote for the monitoring tool that I am writing for Coliance - called "Opsis". Your Purchasing system may run using security gateways, messaging systems, an Enterprise Service Bus (ESB), an API Manager etc. Overlaying each individual piece of software is a layer of configuration that makes up the runtime for each specific business solution. i.e., security gateway policies, messaging systems queues, Enterprise Service Bus Flows, etc. When viewed like this, we can see that business solutions take ‘paths’ through ‘systems’. These paths are complex and vary depending on the business problem being solved. Sometimes, however, this is unattainable with your IT team kept busy monitoring whether machines are running, or if the software is generally operational. They spend much of their time examining individual artifacts on these systems such as queues and flows. Chances a
Posts
IBM and MuleSoft push towards no-code integration
- Get link
- Other Apps
IBM AppConnect Enterprise (IIB) as an API Micro-Gateway
- Get link
- Other Apps
MQ Configuration tools
- Get link
- Other Apps
Having worked in the MQ labs at IBM Hursley for many years I was always struck by how complex MQ appeared. As time has gone by little has changed my mind on this. Recently I was asked to create a solution for the customer that required repetitive creation of an MQ environment. We chose to create a tool using JSON as a configuration language. I'll describe the tool here and welcome feedback on it.
How to choose the right API Manager for you
- Get link
- Other Apps
A lot of my customers are currently deciding which API Manager to use in their estate. With so many of them to choose from and a confusion of terminology this is not an easy task. I see RFP with long lists of criteria but I often think that the choice should be based on some other, softer, questions. I'll outline here some of how I help my customers choose which API Manager is right for them.
API Security: More than just a throttling policy
- Get link
- Other Apps
API Management promises a nirvana of exposing data using well-known and simple techniques. Vendors focus on how easy it is to create the APIs and nearly always mention security as part of the API Lifecycle. Yet, we've all seen the headlines screaming the latest security breach so, what does Security really mean when it comes to API Management? In this post I try to differentiate the basic policies that all vendors discuss from the many other attack vectors that we need to be aware of.