Sunday, October 19, 2003

Where did "service fabric' come from?

I recently had someone tell me that when 'graham glass invented service fabric...blah, blah, blah...", to which I commented... you know, I don't know who invented the term 'service fabric', but Microsoft has been using it for a while now...

---- from DevX --- *a few years ago*
In the following paragraph from the same HailStorm announcement, Mark Lucovsky, HailStorm's primary architect of HailStorm, explains the architectural structure for developers:

We have a thing that we're calling the "service fabric," which is the glue that holds [HailStorm], that makes this system possible. It's a common infrastructure that we've built that all these services to run under. It's a common way to name the services. It's a common way to think about the services. It's a common set of interfaces that if you're writing a HailStorm service, that service must expose in order to have uniform query across all the different services, to have uniform data manipulation. So if I want to add a chunk of XML to a service, I don't have to learn a new way [to do it] for Calendar versus an Address Book. It's the same add method. The data might be different. The schema for that particular service might be different, but the programming model and the service fabric and the glue that holds it all together is uniform.

anyone? surely one of you dinosaurs will tell me that Iona invented it, or it was an MPI term or some shit like that...

No comments: