In this excerpted chapter from his upcoming book, Programming Indigo, David Pallmann describes the Indigo programming model for building service-oriented applications.
In this excerpted chapter from his upcoming book, Programming Indigo, David Pallmann describes the Indigo programming model for building service-oriented applications.
Indigo – Another Microsoft jargon trying takes its undeserved place in enterprise computing.
Hey, I don’t find a “What is Indigo” section anywhere. You guys *assume* that we should know what it is already, right?
Frankly I don’t give two hoots to Indigo or any other Microsoft conjencutred crap.
what is a service oriented application (SOA)?
See http://msdn.microsoft.com/Longhorn/understanding/pillars/Indigo/def…
It will be interesting to see if Mono can develop something comparable to Indigo, or at least compatible.
Do any MS developers feel Indigo is an improvement over WS in .Net?
“Do any MS developers feel Indigo is an improvement over WS in .Net?”
From the exposure I’ve had to Indigo so far (the CTP/Beta releases) it’s a godsend over the current namespace mess we have in .Net 1.x (Web Services, remoting, COM+, MSMQ…all seperate namespaces, trying to get them to play nice w/ each other is tedious at best). Indigo provides a unified API, and is transport agnostic (for the most part) in the eyes of the developer, meaning we don’t have to meddle with specifying transport protocols, etc…indigo does a lot to alleviate the plumbing.
Here’s a description I found helpful:
“The basic building block of SOA is the service. A service is a self-contained software module that performs a predetermined task: “verify a customer’s credit history,” for example. Services are software components that don’t require developers to use a specific underlying technology. As Java developers, we tend to focus on reusing code; thus, we tend to tightly integrate the logic of objects or components within an application. However, SOA promotes application assembly because services can be reused by numerous consumers. For example, in order to create a service that charges a consumer’s credit card, we build and deploy only one instance of such a service; then we can consume this service from any number of applications.”
http://www.onjava.com/pub/a/onjava/2005/01/26/soa-intro.html