How API Ops is the next wave for DevOps John Musser @johnmusser GlueCon 2016
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
How API Ops is the next wave for DevOps
JohnMusser@johnmusserGlueCon2016
APIs can be great,but not always…
API Ops to the rescue
But what is API Ops?
API Ops => DevOps
Hmmm, but what is DevOps
anyway?
“DevOps isaculture,movementorpracticethatemphasizesthecollaborationandcommunicationofboth developersandITprofessionalswhileautomatingtheprocessofsoftwaredeliveryandinfrastructurechanges.
Itaimsatestablishingacultureandenvironmentwherebuilding,testing,andreleasingsoftware,canhappenrapidly,frequently,andmorereliably.”
Source:Wikipedia
Source:Wikipedia
DevOps = development
+
operations
API Ops = API development
+
API operations
Yeah, but aren’t they kinda the same thing?
Sort of. Same, but different…
People
Gateways
Debugging
Support processes
Testing processes
Monitoring
Rate limiting
SecurityUsage patternsTools
Standards
Design patterns
API Ops: what’s different?
Versioning
Infrastructure
Deprecation
CI/CD
Q: Why API Ops now? What’s changed?
1995
Why do we need a Web site?
2000 2005 2010
Of course we have a Web site
Of course we have an API
Why do we need an API?
1995
Why do we need a Web site?
2000 2005 2010
Of course we have a Web site
Of course we have an API
Why do we need an API?
You are here
A: Maturity10+ years of web APIs
Best practices, tools, conventions (and a couple standards)
A: UbiquityAPIs are everywhere now
Internally and externally
A: CriticalityAPIs matter more now
A lot more…
How do we know APIs matter more now?
TheRegister, 9/20/15
AlexiaTsotsis,TechCrunch, 2/3/12
API Ops:Design, build, test and releaseAPIs more rapidly, frequently
and reliably
Elephant in the room?Microservices
Doing microserviceswithout API Ops?
Doing microserviceswithout API Ops?
Good luck with that.
CultureLifecycle
Teams
CultureLifecycle
Teams
Remember theAPI culture wars?
Remember SOAP?
We all had aSOAP hangover
Which meant: REST good,
standards bad
But then…the hangover
subsided
Hmm, maybe standards
aren’t all bad…
Hmm, maybe specs
aren’t all bad…
Hmm, maybe API specs
aren’t all bad…
At the same time, API tools went to 11
API tools, the first generation
API tools, the second generation
Why all the tools?
CultureLifecycle
Teams
The API LifecycleRequirements
Design
Development
QA/Test
Deployment
Operations
The API LifecycleRequirements
Design
Development
QA/Test
Deployment
Operations1st generation API tools focused here
The API LifecycleRequirements
Design
Development
QA/Test
Deployment
Operations1st generation API tools focused here
But it turns-out now we need help elsewhere…
2016is the Year of the
API Lifecycle J
Back to specs…
specs are artifacts
artifacts are good
artifacts are glue
Requirements
Design
Development
QA/Test
Deployment
Operations
Requirements
Design
Development
QA/Test
Deployment
Operations
Requirements
Design
Development
QA/Test
Deployment
Operations
Collaborate,check-in,update,repeat
Requirements
Design
Development
QA/Test
Deployment
Operations
Generatecode,libraries
Requirements
Design
Development
QA/Test
Deployment
Operations
Generatetests,validatespec,load/perf testing
Requirements
Design
Development
QA/Test
Deployment
Operations
Usestd deploytools,smoketest,generatedocs
Requirements
Design
Development
QA/Test
Deployment
Operations
Manage,monitor,measure
Requirements
Design
Development
QA/Test
Deployment
Operations
Iterate,improve,update
Even you’re not “doing specs”
all these steps matter
it’sCI / CD for APIs
Continuous Integration / Continuous Deployment(same principles, same goals)
These all still work nicely for API Ops
These all will work nicely for API Ops
Is the future of APIs containerized?
APIs for API Ops:many layers of
meta
We can now use APIs to:Create APIsTest APIs
Deploy APIsManage APIsMonitor APIs
Or, it’s APIs all the way down…
CultureLifecycle
Teams
Integrated Siloed
Dev Test / QA
Prod / Ops
Dev Test / QA
Prod / Ops
APIs: Internal / External
API Ops:Design, build, test and releaseAPIs more rapidly, frequently
and reliably
Remember:APIs are a journey, not a destination
Thank You
@johnmusser@basho
basho.com
PhotocreditsElephant:https://www.flickr.com/photos/mobilestreetlife/4179063482Wave:https://www.flickr.com/photos/126928999Amplifier:https://www.flickr.com/photos/dankos/3059986305Containers:https://www.flickr.com/photos/russellstreet/4608648934BayeuxTapestry:https://www.flickr.com/photos/fogey03/9463752627Gears:https://www.flickr.com/photos/yospiff/3879736075Silos:https://www.flickr.com/photos/34106201@N00/7995999741Winding road:https://www.flickr.com/photos/matthewthecoolguy/7518274258
Related Documents
