undrgrnd Cliquez ici NEWNEEEW nav-sa-clothing-shoes Cloud Drive Photos FIFA16 cliquez_ici Rentrée scolaire Shop Fire HD 6 Shop Kindle Paperwhite cliquez_ici Jeux Vidéo
Commencez à lire RESTful Web APIs sur votre Kindle dans moins d'une minute. Vous n'avez pas encore de Kindle ? Achetez-le ici Ou commencez à lire dès maintenant avec l'une de nos applications de lecture Kindle gratuites.

Envoyer sur votre Kindle ou un autre appareil

 
 
 

Essai gratuit

Découvrez gratuitement un extrait de ce titre

Envoyer sur votre Kindle ou un autre appareil

Désolé, cet article n'est pas disponible en
Image non disponible pour la
couleur :
Image non disponible
 

RESTful Web APIs [Format Kindle]

Leonard Richardson , Mike Amundsen , Sam Ruby
5.0 étoiles sur 5  Voir tous les commentaires (1 commentaire client)

Prix conseillé : EUR 23,74 De quoi s'agit-il ?
Prix éditeur - format imprimé : EUR 42,44
Prix Kindle : EUR 16,62 TTC & envoi gratuit via réseau sans fil par Amazon Whispernet
Économisez : EUR 25,82 (61%)

App de lecture Kindle gratuite Tout le monde peut lire les livres Kindle, même sans un appareil Kindle, grâce à l'appli Kindle GRATUITE pour les smartphones, les tablettes et les ordinateurs.

Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.

Formats

Prix Amazon Neuf à partir de Occasion à partir de
Format Kindle EUR 16,62  
Broché EUR 41,95  

Concours | Rentrée Kindle des auteurs indés - Participez au premier concours organisé par Kindle Direct Publishing et et saisissez votre chance de devenir le nouveau coup de cœur littéraire sur Amazon !



Les clients ayant acheté cet article ont également acheté

Cette fonction d'achat continuera à charger les articles. Pour naviguer hors de ce carrousel, veuillez utiliser votre touche de raccourci d'en-tête pour naviguer vers l'en-tête précédente ou suivante.

Descriptions du produit

Présentation de l'éditeur

The popularity of REST in recent years has led to tremendous growth in almost-RESTful APIs that don’t include many of the architecture’s benefits. With this practical guide, you’ll learn what it takes to design usable REST APIs that evolve over time. By focusing on solutions that cross a variety of domains, this book shows you how to create powerful and secure applications, using the tools designed for the world’s most successful distributed computing system: the World Wide Web.

You’ll explore the concepts behind REST, learn different strategies for creating hypermedia-based APIs, and then put everything together with a step-by-step guide to designing a RESTful Web API.

  • Examine API design strategies, including the collection pattern and pure hypermedia
  • Understand how hypermedia ties representations together into a coherent API
  • Discover how XMDP and ALPS profile formats can help you meet the Web API "semantic challenge"
  • Learn close to two-dozen standardized hypermedia data formats
  • Apply best practices for using HTTP in API implementations
  • Create Web APIs with the JSON-LD standard and other the Linked Data approaches
  • Understand the CoAP protocol for using REST in embedded systems

Détails sur le produit

  • Format : Format Kindle
  • Taille du fichier : 3611 KB
  • Nombre de pages de l'édition imprimée : 406 pages
  • Utilisation simultanée de l'appareil : Illimité
  • Editeur : O'Reilly Media; Édition : 1 (12 septembre 2013)
  • Vendu par : Amazon Media EU S.à r.l.
  • Langue : Anglais
  • ASIN: B00F5BS966
  • Synthèse vocale : Activée
  • X-Ray :
  • Word Wise: Non activé
  • Composition améliorée: Non activé
  • Moyenne des commentaires client : 5.0 étoiles sur 5  Voir tous les commentaires (1 commentaire client)
  • Classement des meilleures ventes d'Amazon: n°118.048 dans la Boutique Kindle (Voir le Top 100 dans la Boutique Kindle)
  •  Souhaitez-vous faire modifier les images ?


En savoir plus sur les auteurs

Découvrez des livres, informez-vous sur les écrivains, lisez des blogs d'auteurs et bien plus encore.

Quels sont les autres articles que les clients achètent après avoir regardé cet article?


Commentaires en ligne

4 étoiles
0
3 étoiles
0
2 étoiles
0
1 étoiles
0
5.0 étoiles sur 5
5.0 étoiles sur 5
Commentaires client les plus utiles
5.0 étoiles sur 5 Excellent 16 juillet 2015
Format:Format Kindle|Achat vérifié
An excellent in depth description of how to design truly restful APIs. The author elaborates on the Fielding's constrains in practical use cases and describes the trade-offs involved.
Avez-vous trouvé ce commentaire utile ?
Commentaires client les plus utiles sur Amazon.com (beta)
Amazon.com: 3.9 étoiles sur 5  17 commentaires
49 internautes sur 51 ont trouvé ce commentaire utile 
4.0 étoiles sur 5 An "ideas" book 25 septembre 2013
Par Ammy_Evaluator - Publié sur Amazon.com
Format:Broché
This is an "ideas" book ... it is both implementation- and platform-agnostic, and there isn't a single line of code anywhere between its covers (except for HTML and JSON data structures.)

As expected from an "ideas" book, the text is peppered with first person thoughts, rhetorical questions, and very strongly held opinions (e.g., "REST beat SOAP" and "JSON beat XML".) If you buy into these, the book will feel natural and even inspired. If you don't, your hackles may get a workout.

Nevertheless, it ultimately does what any good "ideas" book should do - stimulates your thinking.

From a conceptual perspective, this book provides stellar explanations on topics that are must-knows for REST-practitioners. E.g., on the differences between protocol semantics and application semantics; and the relevance of HATEOAS when it comes to the semantic web.

A minor disappointment for me was that the "API" in the title was defined at a higher-level than I'd have liked. At its core, it merely proposes that a new API should not be a custom one-off, but instead should use standards whenever possible. As a result, it focuses on explanations of standards such as those that deal with collections, URI Templates, and hypermedia controls. However, it punts on the more prosaic elements of good REST API design - such as the identification of resources and operations, for a given domain.

This book's contents could also have benefited from better organization. Concepts were spread out geographically, and often needed a lot of paging back and forth to assemble a complete picture.

Despite these minor quibbles, I thoroughly enjoyed the read.

While this book could be read by a developer at any level, it would be most appreciated by a technical lead or architect who is already familiar with basic REST concepts. Beginners to this technology might be better served by Bill Burke's RESTful Java with Jax-RS - which also covers low level API design adequately. (Note that there is an updated edition due shortly.)

!A_E!
28 internautes sur 29 ont trouvé ce commentaire utile 
3.0 étoiles sur 5 The best I could find.... 7 janvier 2014
Par Tim - Publié sur Amazon.com
Format:Format Kindle|Achat vérifié
... But still not great, unfortunately. The author puts a lot of effort into discouraging people from creating their own media types, link relations, etc. then spends half of the time telling us why we should use two "standard" formats that the author himself has created (Collection+JSON and ALPS). Constantly switching between JSON and XML, various scheme/profile formats are also confusing. Finally, the book is a bit condescending and too futuristic for its own good: Facebook, Flickr, Twitter, etc. have got it all wrong, and the author is going to tell us how to do things "right". Except that no examples, beyond a trivial maze game, are given of how to do things he way the author believes is correct.
10 internautes sur 10 ont trouvé ce commentaire utile 
4.0 étoiles sur 5 REST Concepts 16 octobre 2013
Par IADev - Publié sur Amazon.com
Format:Broché
Only having a basic understanding of REST, this book introduced many new concepts and topics to me. For example, I had never heard of the ColIection+JSON standard or JSON-LD. Hypermedia was also a topic that I had barely heard about but was introduced to in this book. I thought it was interesting how the author called out a short process for how to add hypermedia to an existing API as well as if it was worth the effort. These are important questions to ask rather than just suggesting everything needs to be rewritten to be new. Also, standards are mentioned and referred to in this work, which I am guessing is due to the writer's experience as noted on the back cover. Not a negative to include that information, but I was not used to seeing specification notes in many of the traditional tech books I have read recently. The material for me was overall about how to talk about and work with REST concepts correctly. Semantics are addressed as well as when you would probably use this over that, etc. Guidance also seems helpful in sections such as "What Hypermedia Is For". I do appreciate code from the book being out on Github as well as on the book's website. While the examples are in Node.js at this time - it looks like the website is asking for different programming language ports-so examples have the potential to be added/ported over time. In summary, this book is for those looking to really take time and think about their APIs and if they are working with proper (or I guess one could only say proper in the authors' experience) REST techniques. If you need a quick tutorial to get from zero to done fast, this probably is not the material for you. As a side note, I found Appendix A and B as useful and quick references for HTTP codes and headers, but ymmv.

Overall conclusion: I would see this being a good fit for a REST fan who is trying to get even deeper into the proper way to complete their work.
Disclaimer: I got a copy of this book for review as part of O'Reilly blogger program.
8 internautes sur 9 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 Great book on the future of the web 5 décembre 2013
Par Omar Diab - Publié sur Amazon.com
Format:Format Kindle|Achat vérifié
Fantastic book about hypermedia, a potential future for the web! I think this should be required reading for all API designers and consumers. It might not strike those who play fast and loose with code as very interesting, as its focused on good design rather than getting products out in record time, but I think it's something we should all follow.

It's very clearly written and accessible, and doesn't require too much knowledge to dive into. For reference, I started learning programming around 3 years ago through my current college major.

Here's the Cliffs Notes version:

The problem that the author approaches is that APIs these days are not consistent with one another or even with themselves. This causes several issues:

1) APIs are inflexible. Once you release them, it's very difficult to change them. This is ironic, since HTTP and the web is powerful because of its flexibility.
2) APIs are not machine-readable. You have to read prose documentation to figure out how they work, and every API is different. At the same time, API documentation is often not up to date or non-existent, and it's unscalable to expect all API developers to maintiain complete documentation for all the APIs that they ever work.
3) People create novel, non-standardized APIs for the same general tasks over and over again. There's a staggering amount of repeated work.

The hope is that following standards and imposing structure and metadata in your APIs will one day allow API clients to bridge what the author calls "the semantic gap," which amounts to making an API self-document itself by using standardized idioms and good RESTful web practices, a pattern that the author calls "hypermedia."

The book lays out the problems, solutions, and process of following good API practices clearly, as well as the kind of work that needs to happen to flesh out hypermedia. In this day and age I think anyone who is writing APIs should read this book first, for the betterment of all—programmers, users, and businesses alike.
3 internautes sur 3 ont trouvé ce commentaire utile 
3.0 étoiles sur 5 Is decent reading, but not a very good reference 11 juin 2014
Par Cresten St.Clair - Publié sur Amazon.com
Format:Broché
How exactly does one write a book about complex relations between different resources, tell you to draw link relations, etc., yet fail to provide a single complete example of what he is talking about?

The maze example used throughout the book is contrived and confusing. It's useful for about the first few chapters, and quickly becomes too simple to reference.

I'm currently in the process of writing a web api, and it would be tremendous if I could have some more complete documents to refer to while I"m writing it.

The content is good, but it i severely lacking concrete illustrations / examples. Some complete examples in the appendix would be very nice.
Ces commentaires ont-ils été utiles ?   Dites-le-nous
Rechercher des commentaires

Discussions entre clients

Le forum concernant ce produit
Discussion Réponses Message le plus récent
Pas de discussions pour l'instant

Posez des questions, partagez votre opinion, gagnez en compréhension
Démarrer une nouvelle discussion
Thème:
Première publication:
Aller s'identifier
 

Rechercher parmi les discussions des clients
Rechercher dans toutes les discussions Amazon
   


Rechercher des articles similaires par rubrique