Service oriented architecture is widely used in the business processes today because it uses object oriented programming techniques to make each part of the program independent of the other. With this, it can run the processes or data and store it without the help of any other process or application. While others may have SOA protest on the means and ways of storing these data, to some others, it does not really matter as long as the data retrieved is correct when it is requested.
There are also concerns and SOA protests on upgrades and updates on the object. Although this could potentially be a challenge to many other programs, this is not the case with SOA. The developer can still use the same processes regardless of the changes and updates in the implementation of the process. If any of the underlying algorithms are changed as an update or upgrade of the SOA object, interfacing will not change. This will certainly reduce SOA protest on compatibility and system lifespan.
There was always a protest of a major system re-design and re-write whenever there are new processes introduced. But with an SOA system, new processes are easily implemented because using it with another system or using it with a newer system at a later time will only take little building and re-designing. This saves valuable time needed so the system can be used without major overhaul.
The heart of SOA is the service it provides to the end-user. With a good SOA system, customer protests on complicated service interfaces because just enough detail is given to the customer for the service to be implemented.