Your SlideShare is downloading. ×
0
Optimizing Developer Efficiency Through API Design
Optimizing Developer Efficiency Through API Design
Optimizing Developer Efficiency Through API Design
Optimizing Developer Efficiency Through API Design
Optimizing Developer Efficiency Through API Design
Optimizing Developer Efficiency Through API Design
Optimizing Developer Efficiency Through API Design
Optimizing Developer Efficiency Through API Design
Optimizing Developer Efficiency Through API Design
Optimizing Developer Efficiency Through API Design
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Optimizing Developer Efficiency Through API Design

771

Published on

Building an efficient and scalable API design can mean the life or death of your developer community. While technical efficiency is a key factor in proper optimization, following a pragmatist approach …

Building an efficient and scalable API design can mean the life or death of your developer community. While technical efficiency is a key factor in proper optimization, following a pragmatist approach to specification implementation and security can lead your API design down a path to certain doom.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
771
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • In the days of XML, when REST was in its infancy
  • Then REST came alongHey, my life doesn’t need to suck when I’m using other people’s stuff
  • Companies jumped on the bandwagon without understanding what they were talking about (yeah we support REST – GET / POST). If you say that you can march your ass right on home
  • As we redesigned our APIs, the REST standards became a guide for us. Developer ease became a guiding standardThat’s the point, you’re not tying to develop the perfect system, you’re trying to develop the perfect system for your users
  • Lowering percieved latency for developers
  • Use HTTP properly – standard request and response types
  • Building in automation, using HATEOAS
  • Offload complexity to the implementing provider
  • Transcript

    • 1. Optimizing Developer EfficiencyJonathan LeBlancHead of Developer Evangelism (North America)Github: http://github.com/jcleblancSlides: http://slideshare.net/jcleblancTwitter: @jcleblancThrough API Design
    • 2. In the beginning…there was SOAPSOAPIn the Beginning…there was SOAP
    • 3. Then the enlightenment happenedThen the Enlightenment Happened
    • 4. The natives got RESTlessAll Aboard the REST Train!
    • 5. The witch hunt never RESTedPeople began to treat REST like a religionPeople Treated it as a Religion
    • 6. The principles of REST are a guideREST Principles are a Guide
    • 7. Developer efficiency task 1Lowering perceived latency for developersLowering Perceived Latency
    • 8. Developer efficiency task 2Use HTTP properly – standard request andresponse typesUse HTTP Properly
    • 9. Developer efficiency task 3Building in automation – using HATEOASBuilding in Automation
    • 10. Developer efficiency task 4Offload complexity to the implementingproviderOffload Complexity

    ×