Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Yes! You should provide a client library for yo...

Daniel Azuma
November 13, 2018

Yes! You should provide a client library for your API!

Presentation by Daniel Azuma at RubyConf 2018. Discusses API client libraries, what they should do, why they are useful, and how they can be created and maintained at scale. More information at http://daniel-azuma.com/rubyconf2018

Daniel Azuma

November 13, 2018
Tweet

More Decks by Daniel Azuma

Other Decks in Programming

Transcript

  1. API Client Library A Ruby gem providing a nice Ruby

    interface for calling a network API
  2. .rb .py .js .go .php .rb .py .js .go .php

    .rb .py .js .go .php .rb .py .js .go .php … … >10 languages >250 services
  3. log entry send request user app client library logging service

    receive response return log entry send request receive response return
  4. queue queue log entries log entries send batch send batch

    user app client library logging service
  5. .rb .py .js .go .php .rb .py .js .go .php

    .rb .py .js .go .php .rb .py .js .go .php … … >10 languages >250 services
  6. .rb

  7. Choose a spec standard How do I get started? +

    Write an API description Invoke an open source generator
  8. Choose a spec standard How do I get started? +

    Write an API description Invoke an open source generator Customize the generator
  9. Why to write a client library What should go in

    a client library How to write scalable client libraries
  10. Why to write a client library What should go in

    a client library How to write scalable client libraries
  11. Yes! You should provide a client library for your API!

    https:/ /daniel-azuma.com/rubyconf2018