Architecture — 2 comments
26
Aug 09
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.”
Continue reading →
Architecture — 1 comment
24
Aug 09
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.
Continue reading →
Architecture — 1 comment
20
Aug 09
This is Part 2 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?”
In the first post, SOA: What’s in it for me? Part 1 of 4: The Business, Bill discusses how to deal with business folks when it comes to SOA, which boils down to:
“Never sell SOA to the business outside the context of a business problem that needs solving.”
Of course Bill provides many other tasty nuggets so if you missed his post, I recommend heading over there first. In this post, I will be talking about SOA from the developer’s perspective.
Continue reading →
Architecture — 1 comment
18
Aug 09
In response to our post “What to expect” our former cohort Chris from the old days at a giant semiconductor company posed the question:
“Any thoughts on communicating just exactly what SOA is to mixed audience of technical and non-technical folks, and how it will help them?”
Yes Chris, yes we do have quite a bit to say on the subject. In a previous post we talked about SOA being a means to a end which implies that SOA is an architectural response to a bigger need or problem. The worst thing you can do as an architect is to attempt to sell SOA as SOA. The equivalent mistake would be to try to sell Model/View/Controller (MVC) or Event-Driven architecture (EDA) to a business analyst or end-user. Either they will not get it or they will not care or both.
A better approach is to present the problem at hand, describe how the problem can be solved in conceptual terms, and then and only then illustrate how SOA (assuming it does) provides the design to solve the problem.
Having said that, this is part 1 of 4 posts on how to explain SOA to an organization.
Continue reading →
Gadgets — 3 comments
10
Aug 09
GEO Tagging of photos and GEO Tracking of people are my latest fling. Well, really it is the mashup of the two. But before you run off (or return) from the links lets talk a bit about what I am up to and how it all works…
Continue reading →
