News Stay informed about the latest enterprise technology news and product updates.

Five top SOA tips of 2009

Over the year we've published dozens of tips on topics across the spectrum of SOA technologies to help you build better service-oriented architecture. Here are five of the best.

Throughout the year, we've published dozens of tips to help you build a better service-oriented architecture. Below are five of the best.

1. Protocols for cloud services
As cloud computing grows, architectures and protocols will have to adapt. In this tip, discover how some technologies will develop with the cloud, and find out how others could remain unchanged. Protocols covered include bandwidth and storage with REST, remote procedure calls with SOAP, and RPC between objects with CORBA.

2. MapReduce in the browser helps collaborative supercomputing
Find out how MapReduce creates a framework for mapping a computation to run across thousands of low-cost PCs, and then reducing, or reassembling the individual computations into a final answer.

3. Service Decomposition splits service, not function
A service inventory is a living body of services that individually will need the freedom to evolve independently over time. What Thomas Erl and others learned when documenting the SOA design pattern catalog is that there are patterns that emerged not only at design-time but also during this post-implementation evolutionary stage in a service's lifecycle. Read about them here.

4. Using atomicity to gain SOA granularity
Here's a rigorous definition of atomicity: Services atomicity occurs when each input to a process is used to create one or more outputs from the process. One way to use this definition is to construct a matrix with inputs as rows, outputs as columns, and then mark the inputs used by each output. An atomic process will have all cells of the matrix marked. Find out how to achieve more benefits from atomicity in this tip.

5. How to create a REST strategy
Decided that REST is worth pursuing but looking for a reasonable strategy for identifying REST design and development opportunities? If you are designing and developing a new, highly scalable Web application, the REST approach is without question the best way to go. If you are working on an extension to an existing enterprise application, however, or on an integration project relying in whole or in part on existing infrastructure, the decision is a bit tougher. Learn why in this expert response from Eric Newcomer.

Dig Deeper on Topics Archive

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.