Thursday, 10 September, 2009

Think about the services desgined without SOA Governance Layer!

Dear friends,

I really feel apologize for not being active for a very long time, as I was strucked up as usual not doing any great work! :-) Jokes apart... :)

In this post, "Think about the services desgined without SOA Governance Layer!", we shall discuss the drawbacks of services which are not designed under the Governance model.
Before going to the topic in depth, we can know the definition of keywords: SOA/Governance model.

SOA: (Service Oriented Architecture):-

i) SOA is an architectural style based on the concept of a service, that enables business agility. -architectural style means SOA is a way of planning, designing, implementing &managing IT systems. -business agility means that the strength of SOA is to provide benefit to business in the form of agility(implies wrap&re-use)
ii) Producer & Consumer interact in a loosely coupled manner via an independent interface contract.
-Service Implementation is independent of platform and language. -Service Providers and their interfaces must be discoverable in some manner. -Service Virtualization

SOA Governance:- definition from TIBCO

SOA Governance is about Accountability (clear roles and responsibilities), Visibility (of assets and their access control, and Auditability (who did what) through the entire lifecycle.
1. Decide what services to expose 2. Register the services 3. Monitor environment 4. Secure services 5. Manage Service Level Agreements for operational assurance 6. Virtualize the services for location transparency and high availability 7. Integrate/Mediate Services

So, what happens if I do design my services without SOA Governance?

When the developers implements security, they must understand :-
- The Security standards and how to implement them in all technologies, packages ex: .NET,J2EE - Policies definitions are not globally defined, applied and managed - Policies are applied atomically to the services by the developer,since it is implemented to the particular service and any change that needs to be done might affect the behaviour of the code. - Policy changes typically require developers to modify all the affected code.
- Needs redeployment of all the modified services.

By the above points, we must have come to know the importance of designing an architecture with the Governance model

How it resolves? What are the types of SOA Governance? How it can be implemented?

Stay tuned!! :)


No comments: