(3) Digital Transformation

(4) Digital Transformation: The Global Challenge

(5) APIs are a Pattern

(7) API Driver #1: Push

• Many environments change at increasing velocities
  • Economics change
  • Incentives change
  • Technologies change
• Organizations are pushed to better handle change
  • They have to become better at reacting to external changes
  • They have to become better at executing internal changes
  • They have to become better at embracing changing

(8) API Driver #2: Pull

• External: Participating in the API economy becomes increasingly beneficial
  • Interfacing with customers/partners becomes easier
  • The number of API-ready customers/partners keeps increasing
  • The network effect [https://en.wikipedia.org/wiki/Metcalfe%27s_law] guarantees for the trend to continue
• Internal: Being able to plan and execute changing quickly improves fitness
  • Traditionally, IT is perceived as sluggish and heavyweight
  • Increasingly, IT becomes the lube for the organizational machinery
  • Additionally, IT can allow completely new classes of business models

(9) API Driver #3: Follow

• Having an API strategy becomes increasingly important
  • Organizations have executed on this for a long time (Amazon API memo: 2002)
  • Organizations share experiences and tooling around API strategies
• Using APIs becomes less of an if and more of a how
  • Business pushes IT to make sure strategy can be executed quickly
  • IT can leverage others as justification and leaders

(10) Two Views of API Scope/Focus

• Internal: Using APIs to break up monolithic systems
  • Focus on systems/software engineering and better modularization
  • Turn a system into an ecosystem.
  • Use Private APIs as a way to reduce tight coupling
• External: Using APIs to build up ecosystems
  • Focus on distributed/decentralized systems and better connectivity
  • Enable an ecosystem by loosely coupling systems.
  • Use Public APIs as a way to (better) interface with partners/public
• Both views are complementary and mostly a difference in perspective

(11) One Management Lifecycle

(13) Traditional IT

(14) Business Agility

(16) The Web Works

• MSA is about service autonomy in service-oriented landscapes
  • Developer autonomy is the freedom to choose the best tools for the job
  • Operations autonomy means that every service is operated standalone
• MSA is also about effectiveness in autonomy-focused service-oriented landscapes
  • Rapid provisioning means that getting started is an easy task
  • Basic monitoring establishes visibility into service operations
  • Rapid deployment increases the velocity of service landscape evolution

(17) The Web, Industrialized

• MSA applies Web Architecture's loose coupling [http://dret.net/netdret/publications#pau09a] to the API space
  • Build services with no hidden dependencies
  • Choose the best tool for the job
  • Decouple service provisioning from delivery architecture
  • Monitor service state and usage
  • React quickly when customers or market demand change
  • Experiment ruthlessly and keep experimentation cost low
• MSA is all about being webby while minimizing the cost

(18) Digitalization Dividends [http://queue.acm.org/detail.cfm?id=2956643]

1. Permissionless Innovation
2. Enable Failure
3. Disrupt Trust (replaced by autonomy and accountability)
4. You Build It, You Own It
5. Accelerate Deprecations
6. End Centralized Metadata
7. Concentrate the Pain
8. Test Differently

(20) The Path to Microservices [http://martinfowler.com/articles/microservices.html]

1. Componentization via services
2. Organized around business capabilities
3. Products not projects
4. Smart endpoints and dumb pipes
5. Decentralized governance
6. Decentralized data management
7. Infrastructure automation
8. Design for failure
9. Evolutionary design

(21) Microservices for the Masses?

• Microservices are an investment and not a default choice
  • The cost is the need for advanced infrastructure and teams
  • The return is increased flexibility and agility
  • Cost/benefit for microservices is targeted at long term capabilities
• What are the prerequisites for considering microservices? [http://martinfowler.com/bliki/MicroservicePrerequisites.html]
  1. Rapid Provisioning: Automated process to quickly create server infrastructure
  2. Monitoring: Multi-level monitoring from service health to business-level logic
  3. Rapid Deployment: Automated ways to quickly move from code to running services
• Moving to MSA is a transition process and not one Big Bang
  • Just like the Web is never complete/final, neither is a microservices landscape

(23) Thanks!

• Slides online: dret.net/lectures/www-2019 [http://dret.net/lectures/www-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/]