In this episode, Mike and Matt are joined by special guest Stephen Fishman, Regional Vice President of Customer Success Architecture at MuleSoft and longtime API product expert. Stephen shares insights on product-oriented approaches to API design, development, and lifecycle management. Topics range from API discoverability to launch strategies to a relentless focus on API consumers. Have a listen here:
Statue in Kipling, Saskatchewan, Canada commemorating the red paperclip that Kyle MacDonald used to start a series of trades that led to him obtaining a house in that town.
In a previous blog post, I explained how Clayton Christensen’s “jobs to be done” theory can be used to identify innovation opportunities that are enabled by API products. The CURE methodology from that blog post is the basis for the group exercise in the API Strategy Workshops we deliver worldwide.
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,
Following the technological trends discussed in Episode 1, Mike Amundsen (MuleSoft API Strategy Advisor) and Matt McLarty (MuleSoft Global API Strategy Leader) discuss API-related business and organizational trends they see for 2020 in Episode 2 of the APIs Unplugged podcast. These trends range from product design and product management thinking being applied to API development, to an increase in market maturity for external APIs, to a greater level of decentralization in organizations building and supporting API products.
As we enter a new decade, APIs are involved in many current technology trends. Web APIs are common in microservices, service mesh, public cloud platforms, machine learning, and smart devices. In this inaugural episode of the APIs Unplugged podcast, Mike Amundsen (MuleSoft API Strategy Advisor) and Matt McLarty (MuleSoft Global API Strategy Leader) discuss the most significant technical trends related to APIs for 2020.
It was inevitable! With such euphoria greeting the concept of microservice architecture in 2014, it was only a matter of time before the trough of disillusionment swallowed the hype. What started with blogs like “What are microservices?” and “Reducing technical debt with microservices,” peaked with articles like “Can microservices save U.S. Retailers?” and “Why microservices are the foundation to a digital future,” has now come crashing down with pieces like “Goodbye microservices” and “Monoliths are the future.” Where did it all go wrong?
API New Year! Before jumping headlong into the new decade, I want to take a moment and revisit some of the API strategy highlights in 2019. I covered several topics on the MuleSoft blog last year, but here are some of the bigger non-blog items worth giving a second — or first — look.
Let’s face it: digital transformation isn’t about digitizing. Every company is already using digital information and software applications, and those who are converting paper records and processes to digital ones are hardly getting ahead of the curve. Digital transformation is about surviving and thriving in the digital economy. Where the 20th century industrial economy was relatively stable for successful corporations, this century’s economy is volatile. There is money to be made, but each coin has an opportunity on one side and a threat on the other.
It is finally happening. After ten years of prophecies, preaching, and product launches, the API economy has crossed the chasm. And it’s happening worldwide.
GraphQL offers a new style of API design intended to provide API consumers with unified access to back-end data and services. In spite of this seemingly universal aim, GraphQL has created a schism in the API community between those who believe it is superior to state of the industry RESTful API design and those who believe it is naively re-introducing solved API design problems. This blog examines GraphQL,
