Web services can most certainly be used as a middle tier for many kinds of problems. As for transactions, there are many different levels that you can consider. The easiest approach to implement, given today's standards, is to make sure that each request is a complete transaction -- this will give you reliability similar to existing client/server systems (from the client to the server tier). If you need the ability to have multiple independent requests encapsulated within a single 2PC (two-phase commit) transaction, unfortunately, the standards just aren't there yet (though there are a number of proposals on the table, such as WS-AtomicTransaction). The challenge with 2PC, however, is that it only works in a synchronous environment, which limits overall availability (a chain is only as good as its weakest link). You might want to consider how you would recast portions of your architecture to be asynchronous where appropriate, to decouple the different tiers as much as possible. As part of this, think about using compensating transactions to revert changes, as opposed to using 2PC. While asynchrony is not appropriate for every portion of an overall architecture, if you use it wisely the end result will be a more robust and flexible architecture in general.
Dig Deeper on Topics Archive
Related Q&A from Daniel Foody
Daniel Foody defines end-to-end security and discusses the different parts of security to consider. Continue Reading
Dan Foody discusses the capability of using Web services for ASP applications. Continue Reading
Daniel Foody discusses the "find-bind-execute" paradigm and secure service directories. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.