Offer channel agnostic reusable services

Although you probably build services for an initiative or a project ensure that there are no hidden or explicit couplings with a distribution channel. You should remove identifiers, user tokens, authentication tokens, and other data attributes specific to a distribution channel so your service can be truly reusable. Often in a rush to make dates you might implement an interface that is tightly coupled to a specific channel like a call center. Now, your service isn’t reusable for the branch channel or an online self-service channel or an interactive voice response channel. If you are unsure of how to decouple channel specific attributes you can always encapsulate a separate interface with those attributes (in case of a web service interface you can encapsulate these as a separate XML Schema). As you expose your service with other channels you can either expand or replace the channel data structure at run-time.

Like this post? Subscribe to RSS feed or get blog updates via email.

add to Digg it : post to facebook: Stumble It! : :

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: