Some thoughts on logic duplication in SOA design

My blog has moved. You can view this post at the following address: http://www.osherove.com/blog/2005/1/9/some-thoughts-on-logic-duplication-in-soa-design.html
Published Sunday, January 09, 2005 3:55 AM by RoyOsherove
Filed under:

Comments

Saturday, January 08, 2005 11:24 PM by Javier Luna

# re: Some thoughts on logic duplication in SOA design

Nice post...!!!
Sunday, January 09, 2005 5:45 AM by Udi Dahan - The Software Simplist

# re: Some thoughts on logic duplication in SOA design

It's not that Layers can't trust each other, but that services can't trust each other (by default), it goes to the fact that they're autonomous - they may receive a message with data that hasn't been validated yet. Since services can't assume that all data arriving will be valid, they need to be able to validate it themselves, which, in turn, leads to duplication of validation logic. I think that what you are suggesting may remove the need for a given service to perform validation under certain, but not all, circumstances. This helps performance, but doesn't necessarily remove duplication.
Sunday, January 09, 2005 9:24 AM by Roy Osherove

# re: Some thoughts on logic duplication in SOA design

Udi: I've taken the time to assume that the different layers are actually services themselves. It does remove duplication because I've added the assumption that there is one trusted validation service. I added a little coupling to the mix.