api360 – a how-to guide for enterprise apis - learn how to position your enterprise for long term...

February 10, 2015

© 2015 CA. All rights reserved.

API360 A Model for Enterprise API Success

Ma: McLarty Vice President, The API Academy CA Technologies @ma:mclartybc

2 © 2015 CA. ALL RIGHTS RESERVED.

Summit

Dallas, Texas

February 26, 2015

7 Keynote Speakers – 2 Expert Panels

Full Day – InteracTve – Free Admission

To register: h:p://apiacademy.co/api360

Featured Speaker: Eric Knipp, Gartner


What is a “Web API”?

Technical DefiniTon

• A network-‐addressable (usually by HTTP) interface that enables state transfer of data representaTons

Fielding, R. T. (2000). Architectural Styles and the Design of Network-‐based Socware Architectures. h:p://www.ics.uci.edu/~fielding/pubs/dissertaTon/top.htm

Cox, J.(2001). Network World. Jan. 29, 2001. Volume 18, No. 5. h:ps://books.google.ca/books?id=dBsEAAAAMBAJ


So what’s the big deal?


The Business Value of APIs

It’s not what they are, it’s what they enable


The API Academy


Common QuesTons

How can I be more like Amazon/Google/Salesforce?

How much can I do when I’m not a west coast startup?


Alignment & Usefulness

Engagement & Usability

Scalability & Evolvability

Manageability & Security

API360: An Enterprise Model for API Success



A company’s APIs should align with its business goals

A company’s APIs should be useful to a target audience


API Strategy AnT-‐Pa:erns

• For Open APIs, don’t assume that “if you build it they will come” Faith in the Long Tail

• Don’t start by trying to build the complete set of perfect APIs that will serve every possible consumer Service PerfecTonism

• Don’t start by picking languages, frameworks and socware components

Technological Obsession

• Don’t let single API consumer projects (e.g. mobile) put in long term barriers Tunnel Vision


Successful Strategy

Strategy = Goals + Plan + ExecuTon


h:p://www.amazon.com/The-‐Everything-‐Store-‐Bezos-‐Amazon-‐ebook/dp/B00BWQW73E

Alignment & Usefulness Case Study: Amazon


“We don’t make money when we sell things. We make money when we help customers make purchase decisions.”

Idealism Pragma6sm



Mandate to Amazon developers:

•  Data and funcTonality will only be exposed through APIs.

•  APIs must be designed for use by external developers.

•  If you don’t do this, you will be fired.

-‐ Paraphrased from Jeff Bezos memo, c. 2002 h:p://apievangelist.com/2012/01/12/the-‐secret-‐to-‐amazons-‐success-‐internal-‐apis/



Online retail of books

Resell books

Reinvent the book (Kindle)

Extend the reinvented book (Kindle Fire)

Resell anything (Marketplace) Fulfill anything

Online retailer of anything

Personalized online retailer Online idenTty

Online retail platorm

Online payments

Online platorm (AWS)



Alignment & Usefulness – Key QuesTons

What are my business goals, and how can APIs help me achieve them?

Do I have funded projects that could benefit from APIs?

How do I ensure the APIs I introduce enable future

value?

What are the gaps in my industry that can be exploited through APIs?

Who are the disruptors in my industry and how

are they using APIs?

What business model does my API enable or extend?


Alignment & Usefulness – Key Deliverables

API Roadmap and Project Cross Reference

OrganizaTonal Model

API Business Models and Business Cases

API Academy Strategy Assessment



A company should focus on engaging its API client consumers

APIs should be easy for these developers to use


Engagement & Usability Case Study: Twilio



CompeTTon in the communicaTon API marketplace



Keys to Success • Aggressive MarkeTng • First Mover Advantage • Focus on usability



• Developer registraTons • TTHW (Time to “Hello World”) • Developer community acTvity

API Usability Metrics:


Engagement & Usability – Key QuesTons

Who are the intended and expected

consumers of my APIs?

Who are the developers that will build clients for my

APIs?

How do I a:ract and retain the right consumers and developers?

How do I factor my API consumer needs into my API design?

How do I conTnually enhance the

developer experience (DX) for my API?

What tools does my developer community need to help them

use my API?


Engagement & Usability – Key Deliverables

Developer Program

API and DX Design Principles

API Consumer Toolkits

API Academy Workshop or Boot Camp


Sample API Workshop Design Topics

The Principles of API Design

Improving API AdopTon through DX (Developer Experience)

Designing APIs and SDKs for mobile, web and IoT

Building EffecTve API Management

Teams



APIs should be able to shrink and grow with the business

APIs should be able to change and adapt over Tme


Good Enterprise Architecture

DO

• Focus on the horizon • Synthesize mulTple perspecTves

• Impose appropriate constraints

DO NOT

• Obsess about standardizaTon

• Only care about technology

• Favour model over reality


Why Enterprise IniTaTves Fail

•  Inclusive vs. exclusive insTtuTons

•  CreaTve destrucTon •  Virtuous vs. Vicious Cycles •  De-‐centraliza6on vs.

Centraliza6on vs. Empowerment

“Culture eats strategy for breakfast” – Peter Drucker

See h:p://whynaTonsfail.com/


SOA, APIs & Microservice Architecture (μSA)

Decompose systems into

reusable services. That’s good!

Respect the human element. That’s new!

Be good at change, be prepared for failure.

That’s novel!


Scalability & Evolvability – Key QuesTons

What factors will affect the design Tme scalability of

my APIs?

What about runTme?

How should I version my APIs?

What are the technology trends I need to consider for my APIs?

What are the organizaTonal

constraints that will affect my success?

How can I leverage my exisTng assets

for APIs?


Scalability & Evolvability – Key Deliverables

API Architecture Standards

API Development and Deployment Methodology

Technology Roadmaps

API Academy Workshop or Boot Camp


Sample API Workshop Architectural Topics

Usable, Scalable and Evolvable APIs API Style SelecTon

Managing the lifecycles of APIs

ProtecTng APIs from threats, exploits and

a:acks



It should be easy to see and control an API’s acTvity

An API should only give the right data to the right consumers


Manageability & Security – Key QuesTons

What operaTonal metrics do I need for

my APIs?

What business metrics do I need for

my APIs?

How can I use these metrics to increase business agility?

How can I control access to my APIs without puwng up new barriers?

Who are the principals involved in my APIs and how can I protect privacy?

What new threats do I need to protect against for APIs?


Manageability & Security – Key Deliverables

API AnalyTcs and ReporTng

API IdenTty and Security Model

API Infrastructure and OperaTons

API Management Platorm


The Five Pillars of API Management

From h:ps://www.ca.com/us/collateral/ebooks/na/5-‐pillars-‐of-‐api-‐management.aspx


Summit

Dallas, Texas

February 26, 2015

7 Keynote Speakers – 2 Expert Panels

Full Day – InteracTve – Free Admission

To register: h:p://apiacademy.co/api360

Featured Speaker: Eric Knipp, Gartner


For more informaTon…

• h:p://apiacademy.co API Academy Website

• h:p://www.infoq.com/arTcles/Web-‐APIs-‐From-‐Start-‐to-‐Finish InfoQ Web APIs Series

• h:p://history.apievangelist.com/ Kin Lane’s History of APIs

• h:p://brad-‐stone.com/book/ The Everything Store

• h:p://transform.ca.com/REST-‐API-‐Design-‐Guide.html A Guide to REST


Q & A


Thank You!

h:p://apiacademy.co


Copyright © 2015 CA. All rights reserved. All trademarks, trade names, service marks and logos referenced herein belong to their respecTve companies. No unauthorized use, copying or distribuTon permi:ed.

THIS PRESENTATION IS FOR YOUR INFORMATIONAL PURPOSES ONLY. CA assumes no responsibility for the accuracy or completeness of the informaTon. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENT “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. In no event will CA be liable for any loss or damage, direct or indirect, in connecTon with this presentaTon, including, without limitaTon, lost profits, lost investment, business interrupTon, goodwill, or lost data, even if CA is expressly advised of the possibility of such damages. The informaTon and results illustrated here are based upon certain users’ unique experiences with the referenced socware product in a variety of environments, which may include producTon and nonproducTon environments. Past performance of the socware products in such environments is not necessarily indicaTve of the future performance of such socware products in idenTcal, similar or different environments.

Certain informaTon in this presentaTon may outline CA’s general product direcTon. This presentaTon shall not serve to (i) affect the rights and/or obligaTons of CA or its licensees under any exisTng or future wri:en license agreement or services agreement relaTng to any CA socware product; or (ii) amend any product documentaTon or specificaTons for any CA socware product. The development, release and Tming of any features or funcTonality described in this presentaTon remain at CA’s sole discreTon.

Notwithstanding anything in this presentaTon to the contrary, upon the general availability of any future CA product release referenced in this presentaTon, CA may make such release available (i) for sale to new licensees of such product; and (ii) in the form of a regularly scheduled major product release. Such releases may be made available to current licensees of such product who are current subscribers to CA maintenance and support on a when and if-‐available basis.