[http://creativecommons.org/licenses/by/3.0/]
This work is licensed under a CC
Attribution 3.0 Unported License [http://creativecommons.org/licenses/by/3.0/]
@dret
on Twitter/GitHub
The promise of APIs is to decrease coupling between IT components, thereby allowing IT landscapes to evolve more dynamically and evolutionary. This helps components to be more adaptive to serve today's fast-changing business world. However, there is a crucial difference between working on individual APIs, and overseeing continuously evolving API landscapes. The latter is best served by an approach of continuous architecting, where the goal of the landscape is to observe how it is being used, to identify and promote emerging patterns and practices, and to support these as a way to make API product teams more effective. In this presentation we look at the path from individual APIs to API landscapes, and at the ways in which continuous architecting and supporting organizational structures help to deliver the promise of APIs as a good approach to manage IT complexity and velocity in modern organizations.
@MattMcLartyBC
[http://twitter.com/MattMcLartyBC]@mamund
[http://twitter.com/mamund]@medjawii
[http://twitter.com/medjawii]@mitraman
[http://twitter.com/mitraman]@dret
[http://twitter.com/dret]Continuous API Management: Making the Right Decisions in an Evolving Landscape[https://www.amazon.com/Continuous-Api-Management-Decisions-Landscape/dp/1492043559]
APIs for Things)
Our Digital Transformation Initiative will turn us into the leader of the industry by allowing us to interact with our customers more easily, and more frequently. By increasing the number of customer touchpoints and using the resulting feedback to quickly and relentlessly adapt and improve our offerings, we will be able to outperform our competition and turn into the market leader within the next three years.
proto-APIsfrom integration projects
Product as APImindset across teams
let's pick a platformspirit of old-school SOA
local maximafor product value
global maximaacross all products
Whyexplains why a problem is a problem
Whatexplains a design to address the problem
Howexplains how to implement the solution
Testprovides feedback to verify compliance
enforced/
encouraged
API APIs
API product labels
API as a Productneeds a strategy for DX and product management
Product as APIneeds a strategy for APIs as the new IT component
API Economyneeds a strategy for managing dependency and risk
dret.net/lectures/devday-2018
[http://dret.net/lectures/devday-2018]dret.net/netdret/
[http://dret.net/netdret/]linkedin.com/in/netdret
[http://www.linkedin.com/in/netdret]@dret
[http://twitter.com/dret]@APIacademy
[http://twitter.com/APIacademy]@StandardsDaily
[http://twitter.com/StandardsDaily]