InfoQ Homepage API Content on InfoQ
-
RESTful HTTP in practice
Gregor Roth overviews the basics of RESTful HTTP and discusses typical issues that developers face when they design RESTful HTTP applications, showing how to apply the REST architecture style in practice. Gregor describes commonly used approaches to name URIs, discusses how to interact with resources through the Uniform interface, when to use PUT or POST and how to support non-CRUD operations.
-
Communication Flexibility Using Bindings
In this article, we will look at an important feature of SCA - its support for a wide variety of communication protocols and how to use SCA bindings on services and references to decouple your business code from communication protocols. Finally we'll take a look at the SCA domain to see how bindings operate in and outside the domain.
-
Interview and Book Excerpt: Jaroslav Tulach's Practical API Design
Jaroslav Tulach's latest book Practical API Design covers the topic of API design of software projects. He brings his experience as the architect for NetBeans IDE project to the writing of this book. InfoQ spoke with Jaroslav about his new book, the main motivation for writing it and other topics. We are also making an excerpt from the book available for our readers.
-
Describing RESTful Applications
If servers control their own namespace without a fixed resource hierarchy, how do clients, and more importantly client developers, get to learn or discover URIs of resources? In a new article, Subbu Allamaraju discusses how to describe a RESTful API, focusing on using hypermedia instead of an out-of-band description format such as WADL or WSDL 2.0.
-
How to GET a Cup of Coffee
In this article, Jim Webber, Savas Parastatidis and Ian Robinson show how to drive an application's flow through the use of hypermedia in a RESTful application, using the well-known example from Gregor Hohpe's "Starbucks does not use Two-Phase-Commit" to illustrate how the Web's concepts can be used for integration purposes.
-
AtomServer – The Power of Publishing for Data Distribution – Part Two
In this article, Bryon Jacob and Chris Berry continue their description of AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera. The authors have created several extensions to the AtomPub specification, among them Auto-Tagging, Batching, and Aggregate Feeds.
-
Rationalizing the Presentation Tier
Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs. In this article, Ganesh Prasad and Peter Svensson explains how and why.
-
AtomServer – The Power of Publishing for Data Distribution
In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera. The authors spent the last year implementing an Atom Store for Homeaway, their employer, and are mnow making the Atom Store framework available as open source.
-
REST Anti-Patterns
In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them: tunneling everything through GET or POST, ignoring caching, response codes, misusing cookies, forgetting hypermedia and MIME types, and breaking self-descriptiveness.
-
David Nuescheler on JCR and REST
In this interview, Day CTO and JCR Spec Lead David Nuescheler discusses the benefits of JCR, the Java Content Repository standard, the difference between an API such as Atom/Atom Publishing protocol and JCR, JCR's connection to REST, and Apache Sling, a new kind of Web framework.
-
A RESTful ESB implemented using NetKernel
Jeremy Deane, Technical Architect at Collaborative Consulting, takes a look at writing a Restful ESB using NetKernel. He explains how commercial ESB's were considered and NetKernel was ultimately used to provide the implementation.
-
RESTful Services with Erlang and Yaws
In this article, Steve Vinoski explains how to build RESTful Web services using the Erlang programming language and the Yaws web server. While Steve considers most Web frameworks failures simply because they were a poor match to the problem, he believes Yaws and Erlang are a better match for RESTful development than many other language frameworks that were built specifically for that purpose.