• Save
Optimizing Developer Efficiency Through API Design
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Optimizing Developer Efficiency Through API Design

  • 1,126 views
Uploaded 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......

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.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,126
On Slideshare
1,122
From Embeds
4
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
0
Likes
1

Embeds 4

http://eventifier.co 4

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