3/10/2023 0 Comments Graphql vs rest![]() ![]() Talk: YOW! 2017 Mike Amundsen - Twelve Patterns for Evolvable Web APIs However, Roy Fielding has defined the REST Architecture Style in his dissertation using a very objective set of constraints.Īccording to Phil Sturgeon, the GraphQL comparison makes no sense if you look at the real value and tradeoffs behind REST. Talk: "A no-nonsense GraphQL and REST comparison" by Phil SturgeonĮverybody talks about REST vs. The syntax for the language you use is irrelevant to understand the concept in this talk. The speaker uses XML, but you may as well achieve the same outcome with JSON. ![]() The implementation cost of REST is the same as any other API you are used to developing. The majority of the cost is on learning, which applies to everything related to programming and gets better with practice. Likewise, you may end up with defensive thoughts such as "This is XML, old and outdated, why would I care?". It's the perfect runnable example of how to apply the Hypermedia constraint of REST.Īfter watching this talk, you may end up with a few questions such as "What's the business cost of this?". He also shows some examples of how to optimize a client that makes too many HTTP requests into only one. In this talk, Jon Moore shows a practical example of how the server can upgrade without changing any code in the client. This one is only about clarifying the most common misconceptions. You'll get the answer to those questions and concerns in the following talks. Likewise, you may end up with a few defensive thoughts such as "the industry has evolved this old idea already!". You may end up with a few questions such as "how does a code using this look like?". The talk serves as an introduction to the topic. Stefan Tilkov clarifies the most common misconceptions about REST: It's not about pretty URLs it's not about HTTP verbs it's not about links. REST: I Don't Think it Means What You Think it Does.If you don't, then the conclusion won't make any sense - as much as the conclusion itself. I encourage you to watch all of them, in the same order, from the beginning to the end. In this post, I'll share with you all the talks along with a summary, plus a blog post and the original dissertation. The purpose of the workshop was to present an online talk every day at lunchtime. Likewise, there are some not so popular talks and blog posts with valuable content in this area that can explain their relationship. However, there are many popular talks and blog posts out there with incorrect information about Hypermedia and how it relates to REST. Roy Fielding on REST APIs must be hypertext-driven if the engine of application state (and hence the API) is not being driven by hypertext, then it cannot be RESTful and cannot be a REST API Roy Fielding, the creator of REST and earlier designer of the Web, has put it very clearly: Hypermedia is a mandatory constraint for you to apply the REST Architectural style. After we proved the practical business value of that Hypermedia system, this question still kept popping up: I worked in a company that successfully deployed and capitalized on the exponential value from a Hypermedia system in production. There are hanging flags between each pillar showing the features of the center. The entrance reassembles a classical architectural style with six pillars going from the ground up to the ceiling. A picture from the entry of Schermerhorn Symphony Center in Nashville. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |