- Paperback: 232 pages
- Publisher: Manning Publications; 1 edition (September 30, 2016)
- Language: English
- ISBN-10: 1617292559
- ISBN-13: 978-1617292552
- Product Dimensions: 7.3 x 0.4 x 9.1 inches
- Shipping Weight: 1 pounds (View shipping rates and policies)
- Average Customer Review: 5 customer reviews
- Amazon Best Sellers Rank: #490,723 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.
Irresistible APIs: Designing web APIs that developers will love 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
All Books, All the Time
Read author interviews, book reviews, editors picks, and more at the Amazon Book Review. Read it now
Frequently bought together
Customers who bought this item also bought
From the Publisher
From the Preface
About this book
Irresistible APIs provides all the information needed to plan and manage creation of a Rest API. The book starts out with basic information about the technologies involved in web APIs—specifically Rest APIs—to help make sure that readers have a great basic understanding of API functionality. Industry best practices are covered, informing the reader about how to think about creating a new platform. The book then describes a comprehensive process for planning, designing, and managing development of web APIs, from business value through developer support.
Who should read this book
This book is intended to be accessible to anyone interested on the topic of creating APIs—spanning from an individual developer or technical lead, through product and project managers, and up to executives directing engineering organizations. With that in mind, here are some thoughts on qualifications: the reader should understand, at least at a rudimentary level, the processes surrounding software development—planning, development, testing, and releasing. The reader should be able to follow somewhat technical discussions about software process, including the associated vocabulary. There are chapters that are introductions to specific topics and technologies. Where this occurs, there will be links out to the best supplemental material.
How this book is organized
The first part of the book covers the technologies and best practices for API creation and design. Topics include a discussion of the overall goals and ideals for an excellent API program and the notion of developer experience, the main focus for any web platform that is successful and engaging. A high-level description of the technologies and techniques used for web APIs is presented, as well as best practices for excellent APIs.
Part 2 features an overall strategy for API design and creation. Topics include the steps you need to follow before starting API creation. This covers determining business value, creating powerful metrics, and understanding use cases. Once these details are covered, the book moves on to techniques for designing, developing and supporting your web services to ensure they begin and remain as A-list destinations for your customers.
- The figure on the cover of Irresistible APIs is captioned “The Conservatory Student.” The illustration is taken from a nineteenth-century edition of Sylvain Maréchal’s four-volume compendium of regional dress customs published in France. Each illustration is finely drawn and colored by hand.
About the Author
Kirsten Hunter is an API Evangelist with 10 years experience helping developers and business stakeholders understand, design, and deliver amazing APIs. She speaks frequently at industry conferences and gives workshops for API designers of all levels.
Top customer reviews
Irresistible APIs is not bad book per Se. However when sometime ago my friend experienced Java developer was surprised why book related to webAPI has so may pages, at that time I was thinking that he only concentrate at technical part and there the topic is not so narrow. After reading the book I see that he was right to some extent. First the author describes basics of REST API in quite nice way. Then book suddenly starts it prolonged advocacy part.
The book is not so technical, there are a lot advocacy in it and good arguments why approach API First is so important. And explanation why API added as extra feature is a very bad design decision. And also there are examples from business point of view describing how good and bad decisions had influence on companies like Netflix, Twitter etc. Of course it is very valuable from business point of view and advocacy. Agreeing with all of that I was reading next pages seeking when "the meat" part eventually will start. And it passed more than half of book with that advocacy style. Of course everything towards understanding how important creating of good API is. For companies for their third party clients and so on. I can agree with everything but it is pretty verbose.
Then author describes how to create good APIs and she proofs that using good user cases/stories is good approach, again agree. Then she introduces several designing API schemas tools like Open API (Swagger). In book there are several exercises which are intended to put reader hands on practical subject which is good. In case of using schema designing frameworks it lacks points where user is generating stubs and can use it.
Then authors starts to pack in a stuff which seems to be only to increase volume of book. So describing methodology like DDD, waterflow, agile and so on.
This is yet another book when I have impression that would be better if it had less pages, be less verbose and to the point. And I would like to have impression. Yes I spent a lot of time with book but I've learned a lot. I have grown.
Here from technical point of few there is a lot to add. From advocacy yes I've learned a lot of arguments why good API is crucial.
So if such arguments are very important for reader or maybe will be eye opener. Go ahead.
why not 5 stars? I felt that the book could have been shorter... the last two sections about DDD and types of def environments, dont belong in this book in my opinion... I mean wont hurt to know them, but if i want to learn about API, i should learn about it from this book and if I want to know more about DDD, i should get a book that covers DDD in detail. So this book should have been 140 pages max, if so.
I loved the emphasis of API first and how important is to account for business goals & metrics and the fact that you should always think that your API should be easy to use and satisfy/good experience for any developer.
You will read great examples of bad and good APIs designs from big companies such as Flickr, Twitter, Netflix and others.
Also, you'll have the opportunity to explore tools like RAML and OpenAPI
This book is one of my favorites! Be aware that this book doesn't tackle specific technologies to implement APIs. This book is intended to be accessible to anyone interested on the topic of creating APIs. So if you are an individual developer or technical lead, through product and project managers, and up to executives directing engineering organizations you will find valuable content on this book and start implementing Irresistible APIs!
Excellent approach of examples and then going into depth on the topic. This book has taken a very systematic and methodological approach to the subject and must be on the bookshelf of any developer looking at writing API's for the current web