Divide and conquer: Decoupling API provider and consumer lifecycles

Like any product, APIs and client apps that use APIs have their own lifecycles. They each experience their own Create, Publish, Realize, Maintain, and Retire phases. When things go well, services will experience important use (and re-use) and grow to maturity to provide significant contributions to your company’s performance. And client apps will use APIs that connect to one or more services and, in their own way, create their own cycle of growth and maturity to increase revenue and/or customer use in ways that also spells success for your organization.

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.

How to design message-driven and event-driven APIs

Asynchronous messaging is critical to creating a truly scalable system, where various services can communicate with each other easily, can scale up and down independently, and where one service failing won’t cause all the other services to fail. With the trend of microservices in full swing, this has become even more important. As Tim Bray from Amazon stated: “The proportion of services I work on where queues are absolutely necessary rounds to 100%.”

Event-driven architectures and the AsyncAPI specification

September 24 2019

0 comments

I’m at the Barcelona airport. It’s summer and I’m finally going to visit my family in Badajoz after a long period. The queue at the security checkpoint looks endless but I have time. The phone rings. It’s my mom, she’s excited that I’m visiting and is giving me an update on how things are there now.

Sustainable API migration with the S*T*A*R pattern

Use the star pattern for API migrations

A key element of any healthy API program is the ability to upgrade and migrate existing services in your ecosystem without causing fatal service disruptions. It takes a concerted effort to safely and successfully complete API migrations and, in my experience, organizations who can consistently upgrade their running systems share a common set of skills and employ similar techniques.

4 systems thinking lessons for APIs

Systems thinking for APIs

Hope: He’s in the system.
Luis: I’m in the system?
Dave: You’re in the system!
Luis: The system?
Hank: We’re doomed.

– Ant Man, 2015

“System” is one of the most overused and overloaded terms in technology. Data is stored in “the system”. Applications run on “the system”. Operators manage a distributed “system”. It has become so ingrained in the IT vernacular that we don’t even think about its meaning.

The many flavors of API coordination

wheel gear cogs

Software architects can often conflate the different types of API call coordination. To help address this pitfall, see the classification system I use.

Why an API strategy is critical for your DevOps environment in 2019

October 31 2018

0 comments
critical devops

As organizations plan their IT strategies for 2019, increasing attention is being given to DevOps.

Webinar: Keys of success in full lifecycle API management

apis

APIs are becoming critical to thriving in today’s digital economy. In our recent Connectivity Benchmark Report, we surveyed over 650 IT leaders and found that businesses across industries are realizing great benefits from APIs. This includes increased productivity (58%), increased innovation (48%), and increased employee engagement (43%).

Caching policy: API performance booster

apis

API response time is essential to providing the frictionless end-user experiences necessary for you to meet your API program’s KPIs and retention goals. One way to optimize performance is by having a caching layer in your API architecture. This layer allows you to deliver cached responses for common requests––thereby accessing data in a quick and inexpensive manner.