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

  • Introducing: Restful Objects

    Restful Objects is a public specification of a hypermedia API for domain object models. Version 1.0.0 of the specification has just been released and there are already two open source frameworks that implement the specification - one for the Java platform and one for .NET.

  • Interview and Book Excerpt: Service Design Patterns

    "Service Design Patterns" catalogs design patterns that cover the entire lifecycle of web services. This book is the latest addition to the Martin Fowler signature series which also contains a section on consumer driven contracts contributed by Ian Robinson. InfoQ talked to Rob Daigneau, the author of the book, regarding various topics related to the core idea behind "Service Design Patterns".

  • How REST replaced SOAP on the Web: What it means to you

    The number of REST APIs has grown dramatically over the last 5 years. However, most developers are still struggling to find an agreed upon definition of a RESTful Architecture leading to a lot of inconsistencies in the way these APIs are implemented. This article details how Mule iON, an Integration Platform as a Service, provides a consistent way to expose APIs and API mashups.

  • Is REST the future for SOA?

    In this article Boris Lublinsky discusses architectural difference between SOA and REST and discusses different approaches for leveraging REST in SOA implementations

  • Interview With Ross Mason On The Release Of Mule 3

    Mulesoft recently released Mule 3, their next generation ESB platform. The product comes with a lot of architectural changes under the hood to support the features aimed at making the product easier to use, such as Mule Cloud Connect and Flow, a message flow based service design. InfoQ caught up with Ross Mason to learn more about the product release and the new features in the product offering.

  • SOA Master Data Management in .NET 4.0

    Sharing data among applications in a complex corporate IT environment is unfortunately often reduced to sharing a common database or in some cases a cube. .NET 4.0 introduces a lot of industrialization tools that make the idea of an application independent SOA data repository reachable. This article explores some of those tools, and how they help make SOA data services flexible and non-intrusive.

  • Flexible and User-configurable Charts with Flash Builder Backed by a Java-based RESTful API

    Daniel Morgan shows how to build a portal-style web application comprising a Java back-end to serve a RESTful API for creating, updating, deleting and retrieving dashboard-style, user-configurable charts assembled using Adobe Flash Builder.

  • Nobody Needs Reliable Messaging

    Marc de Graauw challenges the notion that transport-level reliability mechanisms like WS-ReliableMessaging are needed, showing how business-specific logic for in-order and exactly-once processing do the job much better with examples from Dutch Healthcare's SOA.

  • Resource-Oriented Architecture: Information, Not Containers

    The Web is known primarily as a Web of Documents because that has been our main experience with it, but we should not ignore the idea of documents as a data source. New technologies are emerging to make it easier to encode extractable content on the Web. This article focuses on how producers can increase the machine-processability of the documents they produce.

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

BT