SOA Case Study Contest

Readers,

Folks at CIO & SOA Consortium are coming together again to sponsor the SOA Case Study Contest.

In case you have executed a project, build a success story around it & would like to present it as the business case, please visit the link & submit your case study.

The contest if open to all including government agencies. You have only 12 days to go!!!

Submission ends on 26th June. Good Luck!!!

Author Award

Readers!! It has been some time that I had co-authored for "Service Oriented Architecture with Java" & also shared some bouquets/brickbats with you all.
Now it has come as a big moment of joy that the book has been nominated of the author award by its publishers Packt.
In case you have read it, please do vote for it. Also, it can still be purchased from:

• Packt
• Amazon

You can also view the sample chapter here.
Still, if you would just like to read the reviews & then possibly check out the book, please have the reviews here:

• SOA-EDA
• The Server Side
• IT Toolbox

The least you can do is, vote for "Service Oriented Architecture with Java" at the Award Site.

Cheers!! And look forward to your votes.

REST Architecture

What is REST & what I understand by it??

Here is how Dr. Roy Fielding defines it:

“Representational State Transfer is intended to evoke an image of how a well-designed Web application behaves: a network of web pages (a virtual state-machine), where the user progresses through an application by selecting links (state transitions), resulting in the next page (representing the next state of the application) being transferred to the user and rendered for their use.”

The term was first given to describe a form of web architecture. So in short, REST is a model for building a distributed system.

Webservices & REST

Early webservices were the same as well. It was signified by the lack of integration among the services & difficulties in embedding services from various other sources.

This is where the role of REST comes into picture. REST, in fact is only a architecture. It doesn't bog you down with what underlying technologies to use, but helps you build distributed web applications & services. This way, RESTful webservice came to be known as second generation webservices.

Designing a RESTful webservice involves:

1. Become free of underlying programming semantics. Expose the business implementation as a service. So the consumer will identify the service with a URI, which becomes a representation.
2. This enables the representation to be callable over the HTTP interface.
3. Each representation should have URL links to other representations.
4. The URIs should not show any actions, should be shown like a verb/noun.

Eg. http://www.abc.com/AddItem

And not like,

http://www.abc.com/showPage?Process=Add

5. XML is the format to work on, so design proper schema for representations.