How can IT be changed?

FOR IMMEDIATE RELEASE
(Free-Press-Release.com) November 11, 2011 -- Amazon did very well -- that is, enforce SOA (service-oriented architecture). In 2002 or thereabouts, Bezos mandated that all Amazon teams had to expose their data and functionality through service interfaces, and that those teams needed to use those service interfaces to communicate. Period. Or else. It was a forced march to SOA that took several years. Amazon is now an extensible, programmable platform -- and that Amazon Web Services could not have been built without it.

Having covered SOA intensively for several years, I can tell you that the kind of transformation Bezos was able to pull off is quite rare. SOA is one of those initiatives that's for the greater good: Going forward you can build applications using shared services instead of one-off code -- and when you need to improve what a service delivers, every application that uses it is gets the benefit of that improvement. But in the short term? Typically, SOA doesn't do the service owner much good.
That's why so many organizations struggled with SOA. When each fiefdom in an organization has its own agenda, getting all of them to march to the same SOA tune is not easy, especially when the benefit takes a while to arrive.

If developers, instead of using service interfaces to access existing functionality, duplicated that functionality by building it from scratch, they would lose part of their compensation. For an easier reference, just consider the late Steve Jobs, he was and still is one of the biggest pioneers in this IT industry, even though not directly because he was more of a vision orientated person altogether, but all in all IT professionals can and will learn a lot, a heap load of information and future from the late one.

http://www.electrocomputerwarehouse.com

cheap computers     Refurbished C