Are RESTful Web Services really RESTful APIs? – InfoQ.com

Stay ahead of the tech that matters: Attend in-person QCon London (April 4-6, 2022), or online QCon Plus (May 10-20, 2022). Register Now
Facilitating the spread of knowledge and innovation in professional software development


The Continuous Documentation methodology is a useful paradigm that helps ensure that high-quality documentation is created, maintained, and readily available. Code Walkthroughs take the reader on a “walk” — visiting at least two stations in the code — describe flows and interactions, and often incorporate code snippets.
Microservices to be a pattern of ‘decoupled services’ managed to get the best out of it (the underlying understanding of the pattern (‘small’ vs ‘decoupled’) forces developers to take certain design decisions that are consistent with these objectives. In this article discuss we will discuss well and poor implementations: ‘small-services’ vs ‘decoupled-services’ or ‘Letter’ vs the ‘Spirit’.
In the podcast, Meenakshi Kaushik and Neelima Mukiri from the Cisco team speak on responsible AI and machine learning bias and how to address the biases when using ML in our applications.
In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Carol McEwan and Greg Woods from iObeya about the use of Obeya spaces and the culture of transparency they encourage in organisations.
Tammy Bryant Butow covers practical lessons learned in the SRE Apprentices program, things she’d change and shares how to create and roll out such a program.
Learn from practitioners driving innovation and change in software. Attend in-person on April 4-6, 2022.
Your monthly guide to all the topics, technologies and techniques that every professional needs to know about. Subscribe for free.
Uncover emerging trends and practices from software leaders. Attend online on May 10-20, 2022.
InfoQ Homepage News Are RESTful Web Services really RESTful APIs?
This item in japanese
Mar 20, 2011 2 min read
by
Mark Little
Recently Leonard Richardson, co-author or RESTful Web Services, has been wondering why people no longer appear to be referring to Web Services anymore …
Now it is stretching things to say that "nobody uses the term" any more, when in fact there are still lots of occurrences, ranging from Cloud and mobile, through Cloud IDEs and including Social Networking. But Leonard’s point is that the term is perhaps not being used as much as it once was.
He wonders if this subtle change is indicative of something more fundamental and important going on within the industry? It is also true that the term "web service" used by REST proponents was never the same as the SOAP use of the same words. So is this something that is applicable only to the REST community? Is the apparent drop in use of the term in the SOAP community simply tied to the apparent downturn in the use of WS-*?
But Leonard wonders if this change is a problem?
So is it really true that the term "web service" is dying out and being replaced by "API"? If so, why and what are the potential implications? Does this lead to poorer implementations due, presumably, to confusion arising around the term "API" as it applies to the Web? As one of the commenters on his original article states:
So it’s obviously not so black and white. But is there something going on within those shades of grey?

Watch the GraphQL conference for developers and leaders, on-demand.
A round-up of last week’s content on InfoQ sent out every Tuesday. Join a community of over 250,000 senior developers. View an example

We protect your privacy.
You need to Register an InfoQ account or or login to post comments. But there’s so much more behind being registered.
Get the most out of the InfoQ experience.
Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p
by Gerald Loeffler,
by Boris Lublinsky,
by nina j,
by Gerald Loeffler,
Your message is awaiting moderation. Thank you for participating in the discussion.
Firstly, i take issue with extreme case formulations like “nobody uses”, “died out”, “stopped saying […] around 2007”: it’s obviously not like that, so why overload one’s message by taking it to the extreme?

Secondly, if indeed “API” is being used more often in places where “web service” used to be (and i don’t know if it is) then i think this just shows a different perspective on the same problem and a normalisation of the use of web services as a technology and architectural style:

In many discussions it’s just not terribly interesting or relevant that an API is implemented in terms of web services: it’s analogous to the shift from using the term “class library” to, well, “API”. And for the cases where it matters (say in discussions of WS-* vs CICS ws REST 😉 i’m sure that the more specific terms are being used.

I don’t think there’s anything more significant going on than the establishment of a normalised canon of technologies and architectural styles, with “web services” being an established element of that.

cheers
gerald

www.gerald-loeffler.net
by Boris Lublinsky,
Your message is awaiting moderation. Thank you for participating in the discussion.
This once again shows how freely we are using terms that technically make no sense.
Web Services, for example, is a technology and as such can’t have APIs, no can they be replaced with the term API, which according to Wikipedia “is a particular set of rules and specifications that a software program can follow to access and make use of the services and resources provided by another particular software program”. The services, that are exposed using Web Services technologies, on another hand, can have APIs implemented using Web Services technology.
Another example is RESTful Web Services. Here there is even more contradiction of term. First Web services is a specific technology (typically associated with SOAP), which has nothing to do with REST, second – REST has nothing to do with services.
So how can we seriously use these terms?
by nina j,
Your message is awaiting moderation. Thank you for participating in the discussion.
The change of term usage pattern may be related to shifting the focus from a technology (web services) to the functionality (application programming interface). APIs have existed long before networked services, but then the meaning of the term was closer to a “library of function calls” (e.g. OpenGL API).
Now the internet connectivity is almost taken for granted, and the focus is not anymore on “how the services are offered” (via web protocols), but what do they offer (application functionality).

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

A round-up of last week’s content on InfoQ sent out every Tuesday. Join a community of over 250,000 senior developers. View an example

We protect your privacy.
QCon, the international software development conference, is returning (in-person and online) in Spring 2022.
QCon brings together the world’s most innovative senior software engineers across multiple domains to share their real-world implementation of emerging trends and practices.
Find practical inspiration (not product pitches) from software leaders deep in the trenches creating software, scaling architectures and fine-tuning their technical leadership to help you make the right decisions.
Attend in person at QCon London, (April 4-6) or online at QCon Plus (May 10-20). Save your spot now!
InfoQ.com and all content copyright © 2006-2021 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we’ve ever worked with.
Privacy Notice, Terms And Conditions, Cookie Policy

source