The emergence of SOA is worth mentioning about. If the two options are considered, if not SOA what would be the other option. It's manually developing each and every component needed for particular application. Rather than doing it, SOA enhances reusability, configurability, and it saves financial objective in a greater extend as well.
In the word SOA, there are two main topics. Service and architecture. Where architecture elaborate on the detailed plan of a particular system while service means the serving intended target.
Architecture is not something that we can implement and deploy. It is just a concept, idea and paradigm but can be put in to a presentable format using many methods. It describes each and every element in the relevant system and provide scope. In other words it's a "Blue Print". There are many views on why architecture is needed. Followings lists down some of them.
- Team Structure
- Documentation Organisation
- Work Breakdown Structure (WBS)
- Scheduling, Planning, Budgeting
- Unit Testing, Integration,
Service is proving or serving particular set of intended people with something which will eventually help them to make their life easy. The exact difference between service and system should be identified in order to cater them separately.
The main purpose of moving from the traditional development environment to the new SOA is because of the difficulty in adopting to the changes which would be needed everyday for a growing business.
The main useful feature, component of the SOA is the loosely coupling, which is the less knowledge of direct links with another entity. Simply less dependency of something else.
The benefits of SOA can be listed down
- Easy assembling
- Easy configurations
- Modularity
- Time and money saving
No comments:
Post a Comment