Several years ago a few smart people (yes, Bill and myself included) developed a contrived SOA reference implementation as part of our roles as Enterprise Architects in a group charged with Strategy, Architecture and Innovation within the Information Technology Group. We needed something more flexible (and entertaining) than the traditional stock trader or banking scenario, so Baloney on Barter (BOB) was born. Though BOB is several years old (ancient in technology terms), we continue to use many of the concepts and lessons learned today in our consulting roles not from a technology perspective rather as an approach to establishing an architecture goal, executing the forward engineering to prove the concept and supporting the concepts with a complete set of artifacts for all levels of staff. In other words, the process of Enterprise Architecture with focus on applications and technology.
Posts Tagged: Service Oriented Architecture
9
Sep 09
SOA Not So DOA
Bill and I came across this article recently, SOA Not So DOA, which was an excellent, short article. The author had some very good points such as,
“SOA is not a redefinition of modularization, object orientation, componentization. Yes, SOA builds on all three notions but it extends these constructs and thereby creates additional business and IT value. SOA is about integrating the business world with the information technology world in a way that makes both more effective and flexible using services.”
However, the article seemed to abruptly end, just as it was getting to the real meat.
1
Sep 09
SOA: What’s in it for me? Part 4 of 4: Infrastructure
This is the fourth and final post in our “SOA: What’s in it for me?” series. This series was in response to a question from a former cohort, Chris, from the old days at a giant semiconductor company:
“Any thoughts on communicating just exactly what SOA is to mixed audience of technical and non-technical folks, and how it will help them?”
I will assume that you have read part 1, part 2, and part 3 of this series on selling SOA to the business, developer, and data folks respectively. Without further ado, the value proposition of SOA with respect to infrastructure.
26
Aug 09
Federated ESBs
We found and article today by By Sajeev Nair, program director & head, Internet & emerging technologies practice, Mindtree, that in essence stated that it is time for federation of ESBs.
“In a federated ESB, there is one “master” ESB to which several “dependent” ESBs are connected, which forms a single federated logical domain. The master ESB acts as a single point of contact for the service consumers (external to the organization). The service consumer can make requests to any business unit in an enterprise via the master ESB. It also hosts the services for governance, security and management. The master ESB can have its own repository, helping in co-ordination of dependent ESBs via routing rules stored in central management.”
24
Aug 09
SOA: What’s in it for me? Part 3 of 4: The “Data Folks”
This is Part 3 of 4 posts in response to a question from a former cohort, Chris, from the old days at a giant semiconductor company:
“Any thoughts on communicating just exactly what SOA is to mixed audience of technical and non-technical folks, and how it will help them?”
Before I get to the problem at hand, I will assume that you have read part 1 and part 2 of this series on selling SOA to the business and developers respectively. That is to say, I am not going to focus on anything other than the value proposition of SOA with respect to data.