You might have seen the recent news reports about the collision between U.S. and Russian communication satellites. The U.S. satellite was one of the Iridium satellites. What wasn’t reported and you probably don’t know is that an object database management system (ODBMS) is an important part of the Iridium system. Even though ODBMSs are a [...]
February 13, 2009
I am now also posting on the Cutter Blog. My initial posting is (The Acronym) SOA is (Perhaps) Dead (at Some Companies); Long Live Services. It is a response to Anne Thomas Manes’ SOA is Dead; Long Live Services on her blog at the Burton Group.
January 9, 2009
The typical definition of an atomic task or process is one that cannot be decomposed further. This is vague and subject to interpretation. The Decomposition Matrix on this site uses a specific definition: A task (for business process diagrams) or a process (for data flow diagrams) is atomic if every input relates to every output [...]
December 3, 2008
My last posting referenced the criteria for a well-formed business process diagram mentioned in Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. I am going to expand on their criteria to create a more comprehensive definition of a well-formed business process diagram.
To start, here are three criteria from [...]
November 18, 2008
I recently received two new books on business process modeling. Both books looked interesting because they had great titles. As it turns out, one book is great and the other not so good.
The not so good book is Business Process Driven SOA using BPMN and BPEL by Matjaz B. Juric and Kapil Pant. There are [...]
October 9, 2008
The Design Decomposition Blog is written by Doug Barry.
Representational State Transfer (REST) is a style of
architecture based on a set of principles that describe how networked resources are defined
and addressed. These principles were first described in 2000 by Roy Fielding as part
of his doctoral dissertation (new window).
REST is an alternative to the W3C's set of standards that include SOAP (new window) and other WS-*
specifications (some are shown in the navigation menu below).
It is important to note
that REST is a style of software architecture as opposed to a set of standards.
As a result, such applications or architectures are sometimes referred to as RESTful or REST-style applications or architectures. REST has proved to be a popular
choice for implementing Web Services. For example, the books suggested at the
bottom of many of these article pages are dynamically generated, in part, using
a REST architecture. It is one of the options for Amazon Web Services (new window).
An application or
architecture considered RESTful or REST-style is characterized by:
State and
functionality are divided into distributed resources
Every resource is
uniquely addressable using a uniform and minimal set of commands (typically
using HTTP commands of GET, POST, PUT, or DELETE over the Internet)
The protocol is
client/server, stateless, layered, and supports caching
This is essentially the
architecture of the Internet and helps to explain the popularity and ease-of-use
for REST.
There are nearly 400 pages of articles on this site with over 130 pages on Web services and service-oriented architecture.
Search this site for more articles
Custom Search
Browse this site for more articles
Click on the topics below to browse the articles on this site. You can see more detail by clicking on the arrows. This highlights the location of the current
article: Representational State Transfer (REST).
Amazon, Electronic Arts highlight tech action MarketWatch For its part, EA is looking to put that forecast behind and focus on the rest of 2010. The company already has the first big video-game hit of the year with ...
Restful Web Services by Leonard Richardson, Sam Ruby, David Heinemeier Hansson Average Customer Review: based on 44 reviews. Customer Review: RESTful Web Services is one of the best books I have recently read. Before starting reading I have attended a few presentations on REST and I naively thought I became quite familiar with it. Now I can see how ignorant I was about it... This book really helped me to deeply understand what REST is all about and why it is becoming so p...
RESTful .NET: Build and Consume RESTful Web Services with .NET 3.5 by Jon Flanders Average Customer Review: based on 9 reviews. Customer Review: There are two things I really liked about Flanders' book: (1) It has a gradual progression from concept to implementation that is both easy to read and very structured. It made the whole book very valuable. The initial section on REST is concise and either enlightening or revision, depending on what you already know. The transition t...
RESTful Java Web Services by Jose Sandoval Average Customer Review: based on 3 reviews. Customer Review: I bet this book will be outdated in a year, but I like that it's a straightforward approach current status of RESTful frameworks in java.
RESTful PHP Web Services by Samisa Abeysinghe Average Customer Review: based on 5 reviews. Customer Review: This weekend I had the opportunity to read RESTful PHP, by Samisa Abeysinghe, published by Packt Publishing. The book is short, about 200 pages, but full of great information about what REST is, how it is used, how it is supposed to be used and how to use it with PHP. The book assumes you have a working knowledge of PHP, and how to i...