It's a decent book if you're a RESTful API beginner, but overlong and wordy if you have some experience。 I enjoyed the book, I just wish the author favoured brevity a little more。 It's a decent book if you're a RESTful API beginner, but overlong and wordy if you have some experience。 I enjoyed the book, I just wish the author favoured brevity a little more。 。。。more
Matt,
Great way to describe how to design APIs。 Builds from the purpose of the API, its key concepts, and from there into the detailed considerations impacting API design。 The specification examples included are useful and downloadable via the publisher's page for the book。Wish I had a copy of this when I started my current project! Great way to describe how to design APIs。 Builds from the purpose of the API, its key concepts, and from there into the detailed considerations impacting API design。 The specification examples included are useful and downloadable via the publisher's page for the book。Wish I had a copy of this when I started my current project! 。。。more
Serhat M。,
The book provides a broad view of the decision-making process of API design with rich visualizations and comprehensive content in a beginner-friendly tone。 However, it can also be useful for seasoned developers。 The book covers a wide range of topics, starting from HTTP and REST API basics, to more complex topics such as decision making between REST, gRPC, and GraphQL。 Inexperienced engineers can benefit from the book to strengthen their fundamental knowledge, and experienced engineers who are o The book provides a broad view of the decision-making process of API design with rich visualizations and comprehensive content in a beginner-friendly tone。 However, it can also be useful for seasoned developers。 The book covers a wide range of topics, starting from HTTP and REST API basics, to more complex topics such as decision making between REST, gRPC, and GraphQL。 Inexperienced engineers can benefit from the book to strengthen their fundamental knowledge, and experienced engineers who are often expected to prepare guidelines, define standards and pick best practices for various topics, such as APIs, can benefit from the book as a reference resource。Overall, I enjoyed it! 。。。more
Yura Zdyrko,
Great book。 Makes me appreciate APIs much more。
Tim Verstraete,
Really liked this one, it gave me a very good idea on how to tackle REST API's and how to start designing them。 I will definitely use this for my work 。。。 Really liked this one, it gave me a very good idea on how to tackle REST API's and how to start designing them。 I will definitely use this for my work 。。。 。。。more
Ioannis Papikas,
This is an excellent book to start designing your first RESTful API。 It includes a clear walkthrough from the initial goal setting methodology and gradually diving deep into RESTful API, resources, documentation, extensibility, readability, security and finally performance。The book is full of schematic representations and examples to help the reader understand each theory in practice using real case scenarios, although sometimes the scenarios are a bit more complicated from the banking world。
Marcin,
This book describes many aspects of REST API with some comparison to GraphQL and gRPC (but very little - a few paragraphs)。 In the book, you don't find any code。 Only OpenAPI schemas。 I expected more technical patterns, but I received a theory on how to build a good REST API。 There is a chapter about security, but no info about storing JWT Refresh Token in cookie。I think this is a good book for someone who has never created REST API to see which problems can occur, how to resolve them, and what This book describes many aspects of REST API with some comparison to GraphQL and gRPC (but very little - a few paragraphs)。 In the book, you don't find any code。 Only OpenAPI schemas。 I expected more technical patterns, but I received a theory on how to build a good REST API。 There is a chapter about security, but no info about storing JWT Refresh Token in cookie。I think this is a good book for someone who has never created REST API to see which problems can occur, how to resolve them, and what means good API。 。。。more
Viktor Lototskyi,
Good up-to-date book for beginners/intermediate level (as it states it is)。 Not a lot of advanced stuff if you already built several APIs and looking for in-depth topics。
José Fernando Cordova,
Wonderfull
Adam,
Way too verbose。 Not sure what's the target audience is, but the book is extremely basic even for non-technical folks like myself。 States the obvious on the loop - 350 pages of suffering。 Way too verbose。 Not sure what's the target audience is, but the book is extremely basic even for non-technical folks like myself。 States the obvious on the loop - 350 pages of suffering。 。。。more
Valentino Gagliardi,
A bit lengthy and verbose。 You won't find any code in this book, but this text is a must-read for REST API designers and implementers, full of practical advices and lesser known tricks。 A bit lengthy and verbose。 You won't find any code in this book, but this text is a must-read for REST API designers and implementers, full of practical advices and lesser known tricks。 。。。more
Chiranjivee Thakur,
Awesome book to learn API design。
Bartłomiej Falkowski,
I'm disappointed。 I expected much more content and technocratic knowledge。 I understand the idea of delivering technologically agnostic book but it's challenging task to do it and still deliver value。What I liked:- It's a good start for someone who wants to build a public api and has never done it beforeWhat I didn't like:- It's actually valuable position only for people who want to build public api。 - In the end it's an just extended description of REST principles ant restful api (+ OpenApi)- I I'm disappointed。 I expected much more content and technocratic knowledge。 I understand the idea of delivering technologically agnostic book but it's challenging task to do it and still deliver value。What I liked:- It's a good start for someone who wants to build a public api and has never done it beforeWhat I didn't like:- It's actually valuable position only for people who want to build public api。 - In the end it's an just extended description of REST principles ant restful api (+ OpenApi)- I understand the power of metaphore。 However, I felt a bit confused after another comparing software api to hardware devices apis (microwave, cooker, remote and so on)。 I was like "I got it, why are you still trying to convince me?"。 Metaphore is good but metaphore overdose is just annoying :) 。。。more
Alexander,
I was a bit tired by the author’s obsession with diagrams with excessive details。 Otherwise, quite a good content。
Mustapha Hadid,
This is a comprehensive, well-structured book covering almost every aspect of restful web APIs with occasional brief comparisons to well-known alternatives ‒ GraphQL and gRPC。 Although the book explains the concepts in a way that suits those with little or no prior experience/knowledge, there's a lot of knowledge and wisdom there even for experienced API developers。 The book uses OpenAPI specifications, with decent illustrations, to communicate the examples, the real-world examples。The book is d This is a comprehensive, well-structured book covering almost every aspect of restful web APIs with occasional brief comparisons to well-known alternatives ‒ GraphQL and gRPC。 Although the book explains the concepts in a way that suits those with little or no prior experience/knowledge, there's a lot of knowledge and wisdom there even for experienced API developers。 The book uses OpenAPI specifications, with decent illustrations, to communicate the examples, the real-world examples。The book is divided into three parts。 The first part introduces the fundamentals of web API design; you may skip it if you're familiar with web API principles。 The second part is where you learn how to design easy to understand API and the process of decomposing the requirements into web interfaces; I highly recommend this part regardless of your experience level。 The third part, the most valuable part for me, explains the contextual elements you need to consider to design a decent API ‒ things like breaking changes and extensibility, network communication concerns (compression, caching, and conditional requests), and choosing the best API style based on the context。 。。。more
Erlend,
This is a really thorough book on designing Web APIs。 It has all the information most people would want, but its examples and motivation sections can be a bit too long at times。
Jevgenij,
At the first glance this seems to be a very comprehensive book, covering all aspects of API design。 On closer inspection it has many problems:- Covers a lot of very very basic stuff, author writes for those who see a computer for the second time in their lives。- Very wordy, simple things are explained in many many words。- Idealistic in how the design is presented, it would take ages to design an API doing everything by the book, and no possible trade offs or practical considerations are presente At the first glance this seems to be a very comprehensive book, covering all aspects of API design。 On closer inspection it has many problems:- Covers a lot of very very basic stuff, author writes for those who see a computer for the second time in their lives。- Very wordy, simple things are explained in many many words。- Idealistic in how the design is presented, it would take ages to design an API doing everything by the book, and no possible trade offs or practical considerations are presented in the book。 。。。more
Alex,
I found this to be a very helpful reference for what it was。 It doesn't delve too deeply into technical specifics outside of the OpenAPI specification, but I think this is to its advantage。 There are plenty of resources online for working through an API implementation in whatever framework; this book instead focuses most of its time on broader design goals and why you might choose a given framework for a particular task。 I found this to be a very helpful reference for what it was。 It doesn't delve too deeply into technical specifics outside of the OpenAPI specification, but I think this is to its advantage。 There are plenty of resources online for working through an API implementation in whatever framework; this book instead focuses most of its time on broader design goals and why you might choose a given framework for a particular task。 。。。more
Beggie S,
Great book for REST API designers - from novice to expert。 I really liked the clean structure and the way the topics evolve: from REST API basics through security, evolution, lifecycle and efficiency。 As a probable flaw, I’d say I expected to find a deeper comparison of the value of webhooks vs sse vs grpc in real-life scenarios。 Still, the book provides a great frame of reference for the relevant building blocks of API management。
Alex,
An amazing and deep book which will teach you how to design, test, make secure and document RESTful APIs。
Eric Horesnyi,
I have helped 100s organizations build APIs for 5 years, and could find in this book not only principles but also a methodology to design APIs, holistic, obsessed with API user experience but also security and domains。 This is now the methodology I recommend for people to use whenever they consider their API as a product that need to bring value and differentiate。
Pranav Singh,
Great book for developers who work on planning, creating & modifying Open APIs or API that are exposed to other Third parties。Started with basics, it grows to all the way down to nitty-gritty of API management。 Good Read Indeed