InfoQ Homepage REST Content on InfoQ
-
Best Practices For HTTP API Evolvability
As the title suggests, in Best Practices For HTTP API Evolvability, Benjamin Carlyle, set out to define priciples and practices for designing systems, that are built around HTTP API’s. Systems, that are extensible and can evolve over time.
-
REST API or Graph API? Can changing the name help?
Steve Jones, Global Head of Master Data Management at Capgemini and a SOA practitioner, thinks that Facebook's recent announcement about deprecating their REST API in favour of what they call a 'Graph API', is actually a good step for REST in that it may offer a way to cut through the "religious fundamentalism" that often surrounds it.
-
eBay Announces ql.io
After a teaser with clues last week, Subbu and the engineering team at eBay have unveiled ql.io, a SQL inspired dsl to enable frictionless composition of web API's with a SQL like syntax.
-
Restfuse 1.0.0 - A Library For Easy REST/HTTP Integration Tests
EclipseSource has released the first stable version for an open source JUnit extension that automates testing of REST/HTTP services supporting both synchronous and asynchronous calls.
-
APIs Can Be a Pain
In his new post Subbu Allamaraju discusses some of the problems with current APIs usage and suggests the introduction of an additional layer responsible for aligning APIs to the client requirements.
-
Analysis Of Web API Versioning Options
Refering to a questions over versioning conventions used OpenStack Api, Mark Nottingham provides an analysis of the various strategies for versioning Web API in the cloud.
-
Making Sense of the Social Web with Microsoft Social Analytics (Vancouver)
Microsoft is making available a cloud service called Social Analytics for users interested in analyzing Twitter, Facebook, Blogger, YouTube, etc. in order to get insight on the trends on the social web.
-
Does NoSQL have an impact on REST?
Statelessness has been a central principle of RESTful design and implementation. However, with the advent of NoSQL implementations, Ganesh Prasad wonders whether that is no longer true and suggests that REST+NoSQL offers a way to remove this restriction, providing stateful sessions, scalability and fault tolerance.
-
Architectural Mirages
We have lived through many unfounded architectural promises. In his recent post William Vambenepe discusses another one – sharing a single API amongst many UI/Ajax consumers.
-
Is it Difficult to Write REST Clients?
Adam DuVander, from the Programmable Web, reported last week on a survey of API experiences which raised some of the largest problems developers encounter in consuming Web APIs, including the most popular APIs.
-
Mashery Redefines API Documentation with Interactive I/O Docs
Mashery introduces a new generation of API documentation tooling with I/O Docs. I/O Docs takes the drudgery out of verbose API docs and enlivens the experience through live API calls within the documentation. In this news item, we talk to Neil Mansilla to understand the motivation for building this tool, its current state and its future.
-
The Diary of a REST “Convert”
In his new article ZapThink’s Ronald Schmelzer tries to explain why REST is a better option for implementing SOA.
-
unREST as the new REST?
In a recent article Jean-Jacques Dubray discusses why we should be looking beyond REST and perhaps agreeing that it is not applicable to many areas in which it is being used. In an attempt to illustrate where he believes we should be moving, he proposes unREST, which is 3 simple rules for designing successful APIs.
-
Add Spelling and Grammar Checking to Any Online Application for Free
After the Deadline is a free REST based service that provides Spelling, Style, and Grammar checking support to any application that has Internet access. For personal use developers may use the free online server hosted by After the Deadline. Commercial users need to host their own server, the software for which is being offered under the GNU General Public License.
-
On Building Evolvable Systems
In a recent post Mike Amundsen writes about building evolvable systems where he expands on his presentation "Beyond REST : An approach for crafting stable, evolve-able Web applications". The question he hopes to answer in the presentation is "How can we design and implement distributed network solutions that remain stable and flexible over time?"