(3) Bezos Mandate: The Rules [https://gist.github.com/chitchcock/1281611]

• Famous small set of SOA design rules
  • Teams must expose functionality through services (no backdoors)
  • Communications are done through service interfaces
  • There are no hard guidelines for service design
  • Internal/external service is a matter of policy, not one of design
• Going against the let's pick a platform spirit of old-school SOA
  • Focusing on the what and leaving the how as implementation detail

(4) Bezos Mandate: The Consequences [https://plus.google.com/+RipRowan/posts/eVeouesvaVX]

• With more freedom comes more responsibility
  • Monitoring and metrics are necessary for finding root causes
  • All APIs must be hardened against DoS attacks
  • Automated QA is necessary to really understand service health
  • Services must be documented and registered so that they can be discovered
  • Debugging becomes harder because of service dependencies
• Sophisticated tooling required to manage the new SOA landscape
• Much easier in today's technology landscape than 17 years ago

(6) Digital Transformation

(7) Digital Transformation: The Global Challenge

(8) Digital Transformation Chasm [https://devops.com/7-big-digital-transformation-trends/]

(9) Digital Transformation is Hard

• The two hardest things about digital transformation
  • It needs to look at the organization and not just be an IT initiative
  • It is a perpetual feedback cycle and not a one-time effort
• Only looking at technology will miss important pillars [http://dret.net/lectures/api-days-zurich-2019/]
  • Technology is necessary for digitalized value chains
  • Business needs to embrace technology to realize value
  • Organizational teams must be enabled and empowered to work differently

(10) Digital Transformation Status

(11) APIs: Necessary, but not Sufficient

• APIs are necessary (but not sufficient) for digital transformation
  • Good plumbing does not mean that you are building valuable things with it
  • Bad plumbing means that whatever you are building will have problems
• APIs are the delivery of the value created by capabilities
  • Business needs to understand delivery concepts and impacts
  • IT needs to make sure capability value is delivered robustly
• Digital transformation needs (more than just) APIs

(12) The Wonders of APIs

(14) Value and Delivery

(15) API 101

(16) APIs and Integration

• Are APIs just another name for integration?
  • Integration is 1:1 and requires bilateral effort every single time
  • Interconnection is n:m and is designed to easily scale up
• APIs are just integration is a good litmus test for API effectivity
  • If it is true → APIs could be used more effectively
  • Existing integrations are a great starting point for API archaeology
  • Loose coupling [http://dret.net/lectures/api-days-finland-2019/] is one of the critical API properties

(17) Many API Consumers

(18) Consuming Many APIs

(19) API Complexity

(20) API Value Duality

• Partners/Public API use enables API economy participation
  • Exposing APIs expands the footprint of available products
  • Using APIs allows building value chains across organizations
  • The business can expose a platform to the outside
• Private APIs fulfill the goal of business-level agility
  • Every capability is designed and built to be used individually
  • Managing APIs becomes synonymous with managing business capabilities
  • Business itself becomes platform-driven

(21) API Challenges

• Challenges from the business perspective
  • Balance risk/cost and necessary investments in business agility
  • Start making API thinking (i.e., agility) part of business culture
• Challenges from the organizational perspective
  • Enable and empower teams by reducing command-and-control structures
  • Start building feedback structures for observing/supporting teams
• Challenges from the technology perspective
  • Enable and empower developers to adjust to the ecosystem approach
  • Move architecture from "how" to "what" and practice loose coupling

(23) From Integration to APIs

1. Understand the existing landscape of proto-APIs and their genesis
2. Understand the existing culture of teams for their integration tasks
3. Your API strategy starting point is the sum of all these parts
4. Drive change through communications and support (establish API culture)

(24) Understanding the Past

Archaeology is the practice of unearthing artifacts, and understanding them in the context of their origins in time and location. That exact concept can be applied to APIs as well. API Archaeology thus is the practice of finding integrations, understanding why and how they were created, and documenting them as a way to better understand the history and structure of complex IT landscapes. Practicing 'API Archaeology' in organizations can be extremely valuable in terms of finding out about existing ways in which IT components interact (in some shape or form).

[Continuous API Management: Making the Right Decisions in an Evolving Landscape [http://www.oreilly.com/catalog/0636920201755]]

(25) Sharing and Scaling

• Most organizations have proto-APIs from integration projects
  • One-off integrations not intended or designed for reuse
  • Unearthing and documenting help with analysis and improvement
• API culture is about establishing API practice in the organization
  • Cultivate Product as API mindset across teams
  • Build experience around design, implementation, and operations
• API Landscapes focus on sharing and scaling the API practice
  • Empowerment and enlightenment of teams
  • Enterprise IT as managing ecosystems of autonomous components
  • Identify and remove bottlenecks to make teams more effective

(27) APIs Power Digital Transformation

• APIs are the plumbing for digital transformation
• Aligning APIs and business maximizes API value
• Cultivate API landscapes for an agile business
  • API products encapsulate valuable capabilities
  • API consumption helps with loose coupling
  • API landscapes represent complex business landscapes
  • API strategy formulates what the platform should look like
  • API program supports building and evolving the platform

(28) Thanks!

• Slides online: dret.net/lectures/oreilly-sa-ca-2019 [http://dret.net/lectures/oreilly-sa-ca-2019]
• More information about myself:
  • Twitter: @dret [http://twitter.com/dret]
  • LinkedIn: linkedin.com/in/netdret [http://www.linkedin.com/in/netdret]
  • Web page: dret.net/netdret/ [http://dret.net/netdret/]