(3) About Me

• Ph.D. in Communications Systems [http://dret.net/netdret/publications#wil97b] from ETH Zürich [http://www.ethz.ch/]
• Working on Web Architecture after writing the first Web Technology book [http://dret.net/netdret/publications#wil98]
• UC Berkeley (2006-2011), working on Service Models for Open Government [http://dret.net/netdret/publications#wil09g]
• EMC (2011-2014), working on transforming software products into service platforms
• Siemens (2014-2015), working on using IoT to build WoT (APIs for Things)
• Joined CA [http://www.ca.com/]'s API Academy [http://www.apiacademy.co/] in 2016 and now all about API Strategy and Design
• Active in the usual places such as Twitter [http://twitter.com/dret], GitHub [http://github.com/dret], my blog [http://dret.typepad.com/dretblog/], LinkedIn [http://www.linkedin.com/in/netdret], and flickr [https://www.flickr.com/photos/dret/]

(4) @dret on Twitter/GitHub

(5) API Academy [http://www.apiacademy.co/]

• Global Team working on API Strategy and Design topics
  • Matt McLarty [http://www.apiacademy.co/team_member/matt-mclarty/] (Vancouver): @MattMcLartyBC [http://twitter.com/MattMcLartyBC]
  • Mike Amundsen [http://www.apiacademy.co/team_member/mike-amundsen/] (Cincinnati): @mamund [http://twitter.com/mamund]
  • Mehdi Medjaoui [http://www.apiacademy.co/team_member/mehdi-medjaoui/] (San Francisco): @medjawii [http://twitter.com/medjawii]
  • Ronnie Mitra [http://www.apiacademy.co/team_member/ronnie-mitra/] (London): @mitraman [http://twitter.com/mitraman]
  • Erik Wilde [http://www.apiacademy.co/team_member/erik-wilde/] (Zürich): @dret [http://twitter.com/dret]
• Evangelizing ideas and technologies
  • Speaking (conferences, events)
  • Teaching (workshops, bootcamps)
  • Publishing (blogs, articles, books, podcasts [https://soundcloud.com/user-426834320])
  • Doing (side projects on API-related topics)
  • Standardizing (participating in specification work)

(6) Microservice Architecture

• Microservice Architecture: Aligning Principles, Practices, and Culture
• Authored by [http://www.apiacademy.co/microservice-architecture-the-oreilly-book/] API Academy [http://www.apiacademy.co/] members Irakli Nadareishvili, Ronnie Mitra, Matt McLarty, and Mike Amundsen
  • Get free electronic version courtesy of CA Technologies [http://transform.ca.com/API-microservice-architecture-oreilly-book.html]
  • Get a hardcopy version [http://shop.oreilly.com/product/0636920050308.do]

(8) 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 an autonomy-focused service-oriented landscapes
  • Rapid provisioning means that getting started is an easy task
  • Basic monitoring establishes visibility into service behavior
  • Rapid deployment increases the velocity of service landscape evolution

(9) 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

(10) Microservices Cargo Cult

(12) Systems of Systems

• Is a system of systems just a bigger system?
  • Possibly yes, if you see it as something integrated and clearly delineated
  • Possibly no, if you want it to exhibit the evolutionary nature of ecosystems
• Ecosystems have dynamics that systems do not have
  • Ecosystem fitness is driven by external factors and not just system design
  • There never is a complete or stable view of the entire ecosystem
  • Evolving/tuning the system is more reactive than active

(13) From How to What to Why

• How products get developed/delivered is a complex question
  • That's where all the details of CI/CD have to deliver a working solution
• What happens is that products can be evolved at their own pace
  • DevOps focuses on improving the effectiveness of software delivery
  • Microservices focus on radical independence on every possible level
• Why people are looking at it has two rather different drivers
  1. IT effectiveness can be improved when coupling is decreased
  2. Business fitness can be improved when businesses stop being systems

(14) Programming in the Loose

• Programming often is seen as two distinct scopes
  • Small means how to develop individual components
  • Large refers to how to integrate components into a system
• Maybe we need more attention for Programming in the Loose
  • Traditional practices apply to components in the ecosystem
  • The explicit goal is to assemble them into an ecosystem
  • The explicit non-goal is to integrate then into a system

(16) Ecosystem Engineering

• In some scenarios people want to design/build ecosystems
• Ecosystems require different component behavior
• Ecosystems require different engineering/management approaches

(17) Thanks! Questions?

• Slides online: dret.net/lectures/vss-2017 [http://dret.net/lectures/vss-2017]
• Slide sources: dret/lectures [http://github.com/dret/lectures/tree/master/vss-2017] on GitHub [http://github.com/]
• Me: http://dret.net/netdret/ [http://dret.net/netdret/]
• Twitter: @dret [http://twitter.com/dret]