Share
Embed
API Summit Keynote - Web API take over the web
This is the slide deck I created for my keynote at the API Summit 2016 in Berlin.
Rainer Stropek
November 22, 2016
Transcript
23 slides
-
Saves the day. API Summit – Keynote Web APIs Rainer
Stropek software architects gmbh http://www.timecockpit.com [email protected] @rstropek übernehmen das Web Web Mail Twitter -
Your Host Rainer Stropek Developer, Entrepreneur MVP Microsoft Azure MVP
Development Technologies MS Regional Director Senior Consultant IT-Visions Contact software architects gmbh [email protected] Twitter: @rstropek -
Agenda (German) SaaS hat die Sichtweise vieler Kunden auf Software
verändert. Die Kombination verschiedener SaaS Lösungen ist selbst in kleinen Unternehmen heute gang und gäbe. Office 365 für Email, Slack für interne Kommunikation, Salesforce für CRM, time cockpit für Projektzeiterfassung – solche SaaS-Landschaften begegnen uns in der Praxis häufig. Damit das funktioniert, braucht es gute Schnittstellen. Kunden haben das mittlerweile verstanden. Die Integrationsmöglichkeit einer SaaS-Lösung in eine größere Systemlandschaft ist zu einem wichtigen Auswahlkriterium geworden. Wer als SaaS-Anbieter erfolgreich sein will, muss eine moderne Web API anbieten. In dieser Keynote spricht Rainer Stropek darüber, warum die Web API nicht nur ein unwichtiges Detail am Rande ist, sondern eine wichtige Produktfunktion sein muss, der genauso viel Aufmerksamkeit in Hinblick auf Gestaltung, Tests, Dokumentation, Support und Produktpräsentation zu widmen ist, wie anderen Programmteilen. Er berichtet anschließend darüber, welche organisatorischen und technischen Auswirkungen eine Öffnung von Web APIs nach außen auf SaaS Anbieter haben. -
Enterprises are Changing Digital Interdependence Digital ecosystem readiness “79% of
[…] top performers […] participate in a digital ecosystem” Interoperability External mindset Focus on managing interdependence BI/Analytics and Cloud Services Top two investment areas of top performers Source: 2017 CIO Agenda, Gartner Inc.; available at http://www.gartner.com/imagesrv/cio/pdf/Gartner_CIO_Agenda_2017.pdf -
Creative Commons, Source: Alan O'Rourke, https://flic.kr/p/ykLoWK Change shouldn‘t make you
nervous, the absence of change should! -
Channels Building Blocks of a Business Model Which customers do
you serve? What is the value that you deliver to your customers? Which communication, distribution, and sales channels do you use? How do you establish and maintain the relationship with your customer? How does your value proposition result in revenue? Value Proposition CRM Customer Segments Revenue Stream -
Channels What are the key resources that you need? What
are the key activities you have to perform? Which activities do you acquire from outside? How does your cost structure look like? Partners Resources Activities Cost Structure Value Proposition CRM Customer Segments Revenue Stream Building Blocks of a Business Model -
Channels Innovation Where does it come from? Customers might tell
us about areas where they need innovation New capabilities might enable new value propositions Different revenue or cost structures might open new markets Partners Resources Activities Cost Structure Value Proposition CRM Customer Segments Revenue Stream -
Channels External View Marketplaces Self-service Know your end customer Share
Economy New, digital products Value Proposition CRM Customer Segments Revenue Stream -
Agile Public/private cloud Pay-per-use Open New view on security Partners
Resources Activities Cost Structure Internal View -
Microservices Small, autonomous services working together Single responsibility principle applied
to SOA See also concept of Bounded Context Best used with DevOps and continuous deployment Enhance cohesion, decrease coupling, enable incremental evolvement Autonomous = deploy changes without affecting others Technology- and platform-agnostic APIs See also https://en.wikipedia.org/wiki/Microservices -
Microservices Microservices Modeled around business concepts Culture of Automation Hide
implementation details Decentralized Independently deployed Isolate failures Highly observable Fundamental ideas Works alongside many state-of-the-art approaches for software development Agile development techniques Continuous Integration/Delivery DevOps Cloud Computing Containers -
The converged DevOps lifecycle Develop + Test Plan + Track
Monitor + Learn Release Developers IT Ops -
Shift to DevOps Old World Focus on planning Compete, not
collaborate Static hierarchies Individual productivity Efficiency of process Assumptions, not data New World Focus on delivering Collaborate to win Fluent and flexible teams Collective value creation Effectiveness of outcomes Experiment, learn and respond -
Conway‘s Law „Any organization that designs a system will inevitably
produce a design whose structure is a copy of the organization’s communication structure” Organizational hurdles for Microservices Tightly-coupled organizations Geographically distributed teams Missing tools (e.g. self-service cloud infrastructure, CI/CD tools) Inappropriate security policies Unstable or immature service that frequently changes Missing culture of taking ownership (need someone to blame) Cope with many different and new technologies Source: Conway, How Do Committees Invent, Datamation magazine, April 1968 -
Modern Architects… …don‘t create perfect end products …help creating “a
framework in which the right systems can emerge, and continue to grow” …understand the consequences of their decisions …code with the team (“architects should code”, “coding architect”) …aims for a balance between standardization and freedom Build skills for a certain technology vs. right tool for the right job …create guiding principals and practices Example for principals (largely technology-independent): https://12factor.net/ Example for practices (often technology-dependent): .NET Core Coding Guildelines Recommended reading: Newman, Sam. Building Microservices, O'Reilly Media -
Summary Web APIs, Microservices & Co are enablers New products
and services Embrace open source development style Prepare for change Question old habits Become more agile with cloud computing Build trust Bimodal enterprise: Predictability and Stability, exploratory New view on security -
Saves the day. API Summit Q&A Rainer Stropek software architects
gmbh [email protected] http://www.timecockpit.com @rstropek Thank your for coming! Mail Web Twitter