Eric Hartwell's InfoWeb
| March 2005 | ||||||
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | 31 | ||
| Feb Apr | ||||||
Services are, and are not... [adamga's WebLog 3/27/2005; 4:52:57 AM] A common technique for systems integration these days is to use some form of message queueing technology... When discussing SOA, people often make the mistake of confusing this type of service-based design with a service oriented architecture. As Don Box puts it, there are four basic tenets of SOA:
- Services are autonomous
- Services share schema and contract, not class
- Boundaries are explicit
- Service compatibility is determined based on policy
Clearly, a message queueing solution does not meet this criteria...
12:41:06 PM
- Services are autonomous
- Services share schema and contract, not class
- Boundaries are explicit
- Service compatibility is determined based on policy
Clearly, a message queueing solution does not meet this criteria...
12:41:06 PM