BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage REST Content on InfoQ

  • Using DNS for REST Web Service Discovery

    Service Discovery is an essential aspect of service orientated architecture because it avoids early binding of clients to particular service instances. In this article, Jan Algermissen explains the need for discovery of RESTful services, and explains how the existing Domain Name Service (DNS) standard can be used as a widely-deployed and scalable solution.

  • REST and SOAP: When Should I Use Each (or Both)?

    Web developers today have a myriad of technologies they can choose from; for example, the two approaches for interfacing to the web with web services, namely SOAP and REST. Both approaches work, both have advantages and disadvantages to interfacing to web services, but it is up to the web developer to make the decision of which approach may be best for each particular case.

  • Resource-Oriented Architecture: Resource Metadata

    In this second article in the Resource-Oriented Architecture series, Brian Sletten discusses the benefits of REST, what constitutes a resource, associating metadata with a resource, the pitfalls of common models of resource metadata, SPARQL, RDF, expressing RDF facts, RDF triples, querying RDF, and sample RDF queries.

  • Book Excerpt and Interview: Dynamic SOA and BPM: Best Practices for Business Process Management and SOA Agility

    Boris Lublinsky interviews Marc Fiammante as part of a review of Marc' new book, Dynamic SOA and BPM: Best Practices for Business Process Management and SOA Agility. The book is based on many years of practical experience obtained during dozens of enterprise SOA implementations and covers major steps of such implementations

  • Decoupling REST URLs from Code using NetKernel Grammars

    In this article, Randolph Kahle explores the challenge of combining the potentially fluid world of URLs with the more static world of deployed code. Examples of how incoming URLS are parsed and outgoing URLs are generated using NetKernel grammars are given, and the NetKernel grammar system is explored in detail.

  • Resource-Oriented Architecture: The Rest of REST

    In this first article in the Resource-Oriented Architecture series, Brian Sletten discusses the REST architecture style, the history of SOA, SOAP and WS-*, the Semantic Web, URLs as identifiers, URIs and URNs, freedom of form, logically-connected late-binding systems, HATEOAS, and the impact of the Semantic Web upon software systems.

  • Building FlightCaster's Frontends for the Web and Smartphones

    In part two of InfoQ's interview with the FlightCaster team, we discuss scaling Rails on Heroku, the problems of integrating data from multiple providers and mobile smartphone applications.

  • Orchestrating RESTful Services With Mule ESB And Groovy

    In this article, David Dossot, co-author of Mule in Action, examines the power of Mule RESTpack and Groovy in orchestrating RESTful services in the Mule messaging platform. The article detail the interactions for each of these steps and will consider what particular Mule moving parts and Groovy features we have used to achieve such an interaction.

  • 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.

  • 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.

BT