SOA: To Do or not to Do
Gopala Behera & K.T.R.B. Sarma, with their vast experience in witnessing SOA projects gone awry, offer a series of criteria for determining when to launch a SOA and, equally important, when not to. This Article should be required reading for both IT and business managers who are in the early stages of planning a SOA in their organizations.
Gopala Behara
Dr. Gopala Krishna Behara is a Senior Enterprise Architect in the Enterprise Consulting and Architecture Practice division of Wipro. He has a total of around 12 years of experience with Software Engineering, including Project Management, Enterprise Architecture, Business Process Management, SOA, Solution Architecture, Design and Development for Internet/Intranet, Client/Server applications, and Business Application Systems for clients, with commendable exposure in designing the Applications under UML methodology and Rational Unified Process. He has been a key contributor and part of the core team at SOA Center Of Excellence.
Latest posts by Gopala Behara (see all)
- Application Portfolio Analysis: Tool for Cloud Migration - December 4, 2017
- Next Generation Reference Architecture For Connected Government - March 6, 2017
- Telecom Reference Architecture, Part 2 - September 14, 2013
- Maturity Assessment for Enterprise Architecture - January 8, 2013
- Telecom Reference Architecture, Part 1 - July 6, 2010
