Jeremy will give a taste of how Apigee customers are using API Management to create compelling user experiences with incredible speed. We will quickly zoom through high level general principles like culture on our way to the architectural nitty gritty of why you should make a tailored API for every device you support.
http://idc2016.sched.org/event/6AyR/apigee-creating-compelling-user-experiences-through-apis
9. @tenfourty @Apigee #IDC16
New Reality: Two-speed Enterprise
DIGITAL
EXPERIENCE
SYSTEM OF
ENGAGEMENT
CRM
ERP
Data Warehouse
Database
SYSTEM OF RECORD
ESB /Integration
Data Lake
10. @tenfourty @Apigee #IDC16
From control to context
Processes "
guiding principles
interaction patterns
Roles
small x-functional teams
end-2-end responsibility
Communication
transparent and open
pull vs. push
12. @tenfourty @Apigee #IDC16
New Reality: Digital value chain
B2C
B2E
B2B
User
App
Developer
API
API Team
Backend
customers
partners
employees
13. @tenfourty @Apigee #IDC16
From an army of workers to a
network of makers
• customers activated
• users as product managers
CUSTOMERS
• ecosystem innovation
• extend and complement
PARTNERS
• on boarding & analytics
• x-company innovation
INTERNAL DEVELOPERS
• enterprise data at core
• unlock core value
SYSTEM OF RECORD
15. @tenfourty @Apigee #IDC16
New Reality: Digital scale
from millions of
users to billions
from limited data to
massive data
capture and usage
From connecting
humans to programs to
programs to programs
16. @tenfourty @Apigee #IDC16
Every Interaction Matters
availability @scale
Fault tolerance
Programs must function even
when errors occur
Continuous delivery
Bite-size
innovation
Monitor
Monitor across all "
programs
17. @tenfourty @Apigee #IDC16
Every Dollar Counts
Don’t wait "
around
Ride the "
demand curve
Automate, "
automate, automate
efficiency @scale
26. @tenfourty @Apigee #IDC16
General Principles for your REST APIs
• Be Pragmatic, not a RESTafarian – for the sake of other developers
• Only need 2 urls per resource
– Collection - /dogs
– Element - /dogs/1234
– POST, GET, PUT and DELETE -> CREATE, READ, UPDATE and DELETE
• Verbs are BAD, Nouns are GOOD
– /getsmalldogs vs /dogs
• Plurals are better
– /dogs
• We favour Data Oriented APIs over Service Oriented APIs
– Learn the data vs learn the services + the date
– Don’t design an API at all, just use REST
• We favour simple, flat JSON
• Versioning
– Don’t! but if you have to we have come to favour putting the version in the sub-domain (if you have to!) – the ‘no-
versioning’ strategy for versioning
• https://api.acmecorp.com/dogs/1234
• https://api2.acmecorp.com/dogs/1234
• Check out these resources:
– Web API Design ebook - https://pages.apigee.com/web-api-design-website-h-ebook-registration.html
– Newest thinking in this webinar - http://apigee.com/about/blog/technology/pragmatic-rest-next-generation
28. @tenfourty @Apigee #IDC16
4 Best Practices
• Create APIs by product and device type to reduce maintenance
• Create new APIs using existing components with API management to minimize work
from backend teams
• Integrate API Management with your existing CI tooling and processes
• Create an API Tier in front of your microservices to maximize performance
33. @tenfourty @Apigee #IDC16
Full Story: Belly Up to the Microservices Bar
• http://apigee.com/about/blog/
developer/belly-microservices-bar
• https://www.youtube.com/watch?
list=PLIXjuPlujxxz9oSr26Oii3-
HWhPZU1tvE&v=_-fKGzN-8tA