- Paperback: 150 pages
- Publisher: O'Reilly Media; 1 edition (December 27, 2011)
- Language: English
- ISBN-10: 9781449308926
- ISBN-13: 978-1449308926
- ASIN: 1449308929
- Product Dimensions: 7 x 0.3 x 9.2 inches
- Shipping Weight: 11 ounces (View shipping rates and policies)
- Average Customer Review: 36 customer reviews
- Amazon Best Sellers Rank: #323,320 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
APIs: A Strategy Guide: Creating Channels with Application Programming Interfaces 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Frequently bought together
Customers who bought this item also bought
About the Author
Daniel Jacobson is Director of Engineering for the Netflix API, which is the primary distribution channel for getting movie and subscriber information to hundreds of Netflix-ready streaming devices. Prior to Netflix, Daniel led an engineering team NPR where he created the NPR API as well as the content management system that drives NPR.org, mobile platforms, and all other digital presentations of NPR content.
As CTO of Apigee, Greg Brail has led the Apigee technology team as it deployed its API management technology for scores of customers. Prior to joining Apigee, Greg led the technology behind BEA’s WebLogic JMS and Core Engine initiatives and developed the message-delivery infrastructure at TransactPlus.
Greg spent his formative years with transaction-processing pioneer Transarc, where he deployed production systems at JPMorgan and elsewhere. He has held positions at Citibank and at IBM. Greg holds a degree in Computer Science from Brown University.
Dan Woods is a seasoned CTO, author, speaker, and entrepreneur with experience in business, computer science, journalism, and publishing. He is CTO and Editor of CITO Research, a firm dedicated to creating content to improve the performance of CIO and CTOs. As an author, Dan has written or coauthored more than 20 books about business and technology, ranging from books about service-oriented architecture, open source, manufacturing, RFID, and wikis to the ideas driving the latest generation of enterprise applications, particularly in the face of Web 2.0's impact on the enterprise. Dan has written hundreds of white papers and conducted more than 1,000 interviews with experts in a variety of fields. He is also an invited speaker and moderator at international conferences.
As a CTO, Dan built technology for companies ranging from Time Inc. New Media to TheStreet.com. He has managed the product development cycle from initial requirements through sales for websites and software products designed for the publishing and financial services industries. At TheStreet.com, his systems supported the company's successful IPO and handled millions of daily page views while the number of subscribers tripled and new lines of business were launched. At CapitalThinking, Dan's software was purchased by the IT departments of large financial institutions including General Electric, JPMorgan Chase, and Citigroup.
Dan holds an M.S. from Columbia University's Graduate School of Journalism and a B.A. in Computer Science from the University of Michigan. Since July 2008, Dan has been writing a column for Forbes.com.
Try the Kindle edition and experience these great reading features:
There was a problem filtering reviews right now. Please try again later.
1. Why your company needs to have an API
2. How to design, secure and manage the API
3. What API strategies your company should adopt, including legal and operational considerations
4. How to measure the success of the API
5. How to drive API engagement
The authors have years of experience in the API space and I think they did a pretty good job distilling their collective wisdom and learned best practices in this "short and sweet" booklet (134-pages!) I think it is important for the success of any API initiative that *all* stakeholders read this book to get on the same page of what needs to take place to ensure the success of the initiative. It's hard to argue with the "tried and true" practices of which this book is rife.
If you're interested in getting into the nitty gritty technical details of how to build an API, I highly recommend RESTful Web Services Cookbook: Solutions for Improving Scalability and Simplicity as a technical companion read to this book. Read this book first, and then delve into the technical details with Subbu's book.
If you're an executive who's on the fence regarding APIs, you must read this book to get educated on the subject. It's important for your team to get your full support which they won't unless you fully understand the whats, hows and whys of APIs.
You need to learn how to speak API and this book will get you fluent in no time.
The front half of the book is advocacy: "You should have an API, here's why." Snooze. If you are reading this you probably get this already.
The back half boils down to probably about a condensed 5 pages of checklists on the subjects of metrics, security, user management, legal, and community engagement. This was more useful as it gave a more complete picture of all of the planning items on the table that don't have to do with technical execution of the API. This was all useful but not detailed enough.
I'm not saying that developers won't benefit from reading this book. The big-picture perspective and the examples of how organizations (e.g., NPR) are using and sharing their APIs are insightful and inspiring.