- December 1, 2008
- Posted by: admin
- Categories: Agile Applications, Blog, Business Dynamics, Enterprise Agility, Enterprise Software, SOA & Agile Applications
Service-oriented architecture represents an alternative to the slash-and-burn approach to system modernization. Transitioning to SOA takes a lot of planning, and it’s best to start small. Vendors are also lining up with products meant to ease implementation.
SOA transition” is buzz term growing in popularity among IT managers, especially when they meet with corporate boardroom residents. Businesses are transitioning into service-oriented architecture by tapping into the increasing number of SOA products software makers are creating to meet this new interest.
However, for the uninitiated, SOA is just another entry in the mushrooming jumble of acronyms and alphabet soups business technology users must digest. The world of e-commerce is undergoing a transition toward greater use of SOA. Its proponents claim that SOA holds real promise to drive further adoption and greater efficiency for e-commerce.
SOA can be a powerful asset for IT organizations, enabling them to unite disparate systems using well-defined, common standard interfaces. One should not view SOA as a new technology, however. It is a flexible business process that can help adopters cost-effectively deliver increased value to their customers.Rather than throwing investment money into “rip and replace” strategies that involve complete software rewrites, application modernization with SOA enables organizations to reuse valuable business logic within applications that can seamlessly integrate with newer, Web-based systems.
What is the impact on the average developer’s day-to-day activities? What new skills are required? How do you enforce good governance? How do you think SOA will impact the Business Logic of Work flows in your organization?