How API standards underpin an effective API strategy

November 21 2019

0 comments

At MuleSoft, we’ve worked hard to develop programs and guidelines to help our customers and the market see APIs as more than just project outcomes. APIs are digital products, worthy of respect throughout their whole lifetime, and critical enablers of ongoing digital transformation.

That’s why I was really excited when we announced our API Strategy Workshops. They provide practical support to implement our API Strategy Blueprint.

Five stages of the API product lifecycle

api-product-lifecycle

Just like any product, APIs have their own lifecycle with distinct phases. And recognizing them means you can take advantage of them by focusing on the right aims and the proper convenance at each step along the way. This was one of the key lessons we focused on when we wrote the “Continuous API Management” book in 2018.

There are situations when you need to invest lots of time and effort to get an API product ready for consumption.

The blockers and catalysts of digital transformation – part 1

blockers-of-digital-transformation

How many have you heard that you need APIs for digital transformation? How about that this also requires cultural transformation? Let me guess: too many! Businesses are struggling when it comes to knowing what to look for, what actions to take, and how to make digital transformation work.

Digital transformation is more than just technology. Digital transformation prepares organizations to leverage the benefits of new technology to create business value.

API products, not API projects

dusk swarm

In order to continuously deliver software that is shaped by user feedback, it is better to think of the resulting solution as a long-living product than a time- and budget-bounded project.

5 traits of successful API products

5 traits API products

The web is littered with good API intentions gone wrong. Too many businesses have realized they “need APIs” and created them as a tick-the-box feature without thinking about their broader strategic value. One critical difference between the businesses that succeed and those that don’t is the underlying approach by which APIs are planned and conceived.  Put simply: Is the API a project or a product?

Your next integration project should be an API project

api integration project

During my time at MuleSoft, I’ve had a lot of conversations with people from other companies about their specific challenges and one recurring theme is almost always present: the conversation starts out talking about point-to-point integrations. It’s pretty natural when presented with two systems to want to draw a connection. The data here is needed there and, after that, we’re done because a problem was solved.