Optimizing Developer Efficiency Through API Design
•
1 gostou•1,165 visualizações
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.
Recomendados
Mais conteúdo relacionado
Semelhante a Optimizing Developer Efficiency Through API Design
Semelhante a Optimizing Developer Efficiency Through API Design (20)
Mais de Jonathan LeBlanc
Mais de Jonathan LeBlanc (20)
Último
Último (20)
Optimizing Developer Efficiency Through API Design
- 1. Optimizing Developer Efficiency Jonathan LeBlanc Head of Developer Evangelism (North America) Github: http://github.com/jcleblanc Slides: http://slideshare.net/jcleblanc Twitter: @jcleblanc Through API Design
- 2. In the beginning…there was SOAP SOAP In the Beginning…there was SOAP
- 3. Then the enlightenment happened Then the Enlightenment Happened
- 4. The natives got RESTless All Aboard the REST Train!
- 5. The witch hunt never RESTed People began to treat REST like a religion People Treated it as a Religion
- 6. The principles of REST are a guide REST Principles are a Guide
- 7. Developer efficiency task 1 Lowering perceived latency for developers Lowering Perceived Latency
- 8. Developer efficiency task 2 Use HTTP properly – standard request and response types Use HTTP Properly
- 9. Developer efficiency task 3 Building in automation – using HATEOAS Building in Automation
- 10. Developer efficiency task 4 Offload complexity to the implementing provider Offload Complexity
Notas do Editor
- 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