Lou Powell on integration in the enterprise: APIs Unplugged

For this installment of APIs Unplugged, Matt McLarty and Mike Amundsen sat down with ProKarma’s Lou Powell to talk about successful API integration efforts in the enterprise and his API IQ quadrant. Currently, a partner at ProKarma, an “experience engineering” company, Powell works closely with businesses to create pioneering experiences and accelerate outcomes, unlocking greater value and market leadership. He worked in advertising and digital marketing before launching his own business,

How to build a modern API as self-contained API

API management is the process of designing, publishing, documenting, and analyzing APIs in a secure environment. It provides users — like developers and partners — the ability to access an API, governed by a set of configurable policies. 

In this post, we will take a closer look at the benefits of using the basic endpoint approach to deploy a packaged API implementation along with a proxy as a self-contained application and examine the required steps for the API pairing within API Manager using the API autodiscovery concept.

8 challenges of API landscapes

One of the key tasks of supporting a vital API program for your company is dealing with change over time. In previous articles, I’ve talked about the importance of managing the entire API lifecycle and how to recognize important milestones in the life of an API. These milestones often signal that a change in the way the API is treated, measured, and managed needs to change. 

API governance: Asset approval process

In our previous blog, we covered the overview of governance posture for organizations. In this blog, we will take a deep dive into identifying the family of assets in the API ecosystem and their approval process. The aspects covered in this blog are highlighted in orange in the image below. As with any initiative an approval process spreads across different pillars and stages of the governance process as shown in the following matrix.

The 4 P’s of API governance

To many people, governance is a four-letter word. As vital as governance is to any organization’s strategy, the mere mention of the word can take the oxygen out of the room. One reason for this is that people often view governance as a burden that slows things down. However, when done effectively, governance can provide clear direction, remove obstacles, and allow different parts of the organization to function independently. The best way to implement this empowering style of governance is to keep strategic goals top of mind,

A practical guide for API governance in Mule for IT

Most organizations today have a governance strategy depending on their industry. Policies such as Sarbanes-Oxley, Gramm-Leach-Bliley Act, Health Insurance Portability and Accountability Act (HIPAA), or other acts influence a company’s governance strategy. However, these types of policies are often abstract and only provide mandates on “what” but not on “how” to govern an IT infrastructure and services. Organizations have recognized the need to enforce additional governance to derive uniformity, standards, best practices, and common operating procedures across teams.

How to improve API governance with distributed decision making

In 2017, Ronnie Mitra presented a talk at Nordic APIs entitled “Programming the People Platform: Beyond Conway’s Law.” In that talk, Mitra outlined a model for distributed decision making and how it can be used to improve API governance. The material from that talk made it into the book “Continuous API Management.” Here, Mitra explained in greater detail how to apply this model to match, and eventually evolve,