Today someone challenged me to explain Indigo in five minutes.
Here goes.
Indigo connects software together using structural contracts (a.k.a. schemas) and behavioral contracts (a.k.a. message exchange patterns).
We integrate with the CLR and COM and eviscerate your local types into either data contracts or service contracts, but never both. An especially cool feature of Indigo is that the sender and receiver don't need to share the same CLR types (nor do both sides even need to be Indigo or CLR or COM).
The messages we use in Indigo are based on the SOAP processing/data model but don't use angle brackets unless we are forced to, and when forced to, we do it happily and pretty damn fast.
We support a variety of message transports and support both transport-level and SOAP-level security and reliability.
Oh yeah, and we integrate tightly with System.Transactions and a queueing system.
There. That took me less than five minutes and I type much slower than I speak.
Maybe I'm jaded, but I'm skeptical of technologies whose core concepts can't be explained crisply in five minutes or less.
Posted
Oct 02 2004, 04:19 AM
by
don-box