A question that I am often asked by colleagues and friends alike is “What is an Enterprise Architect, anyway?” This article is the first in a series of articles that will explain the term “Enterprise Architecture,” why it is important, and how each of the disciplines that constitute Enterprise Architecture relate to each other. Most importantly, this article is going to talk about how Enterprise Architecture needs to govern the processes around software development.
This morning my RSS feeds had an update from Ms Manes’ blog again. She points to an article by Dan Woods of Forbes.com and says of his article that she is “pleased to see that Dan read beyond the first paragraph, and he understands the core message of my post (i.e., ‘SOA has been disappointing and that services should be a key focus’)” …
I wonder if Ms Manes realizes that she advocated exactly the same thing that Mr Woods advocated and then went on to slam the idea? In her original post she argued that the focus should shift from SOA to building services, and yet here she is arguing that just building services will result in fragile, expensive systems. Ms Manes is just flat-out contradicting herself.
“SOA is Dead; Long Live Services,” proclaimed Amy Thomas Manes on January 5th, 2009.
When I read Ms Manes’ post, I felt like the person standing on the sidewalk in a movie. The camera is focused on me and someone (SOA) steps out into the street. From the side of the screen, off-camera, a bus comes careening past and the person that stepped into the street is hit and taken completely out of camera and I’m left standing with my jaw on my knees.