Re: [service-orientated-architecture] Re: What is a "well defined interface"?

Fri, 03 Mar 2006 11:38:14 -0800

Normally a business application also has rules to calculate GST and other applicable taxes. It will be good to have these functionalities as a service. So that the same application can work in different geographies by plugging in a different set of rules and business logic which is applicable to the country/continent we are targetting at. A simple example can be to have a Tax calculation service which can work in simple tax calculation mode (10% as GST for Australia) to a complex tax calculation (Variable State and Central Tax based on items for country like India). So a company with different offices world-wide can make use of same application with maximum re-use and the only few functionalities (like Tax Calculation) are localized.

My 2.2 cents (including GST).

Cheers :)
Samir Kumar Mishra
Tel: +61-403-747-809
Email: [EMAIL PROTECTED]
Home: http://samirmishra.tripod.com/
My Attitude in life is best described by my Blood Group…  B +ve


On 3/2/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
The advice I give to my clients is to start their reuse efforts with infrastructure functionality -- things like authentication, authorization, auditing, cryptography, logging, monitoring, caching, etc. One of the things I like best about SOAP is that it enables clean separation of infrastructure from business logic via the SOAP mediation model.

This approach brings two advantages: it is something that can be done reasonably well by an IT group without a huge amount of collaboration with all business groups that will use the services, and it gives the IT group more control over policy enforcement.

One of my clients (a Fortune 50 financial conglomerate) estimates that 30% of its current IT budget is spent on infrastructure functionality -- which currently is reimplemented in every application. By externalizing this functionality into reusable services, they could potentially save hundreds of millions of dollars a year. They would also have much better control of security and management, and they would ensure much more consistent enforcement of policy.

Another sweet opportunity for reuse is in response to government regulations. For example, anytime someone requests to open an account, a financial institution is required to check a government database to ensure that the person is not a known financeer of terrorists. Rather than implement this code in every line of business for every type of account, this code should be implemented as a shared service.

Anne



--



SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture

YAHOO! GROUPS LINKS



Reply via email to