Big Booger
September 23rd, 2006, 01:18 AM
What is Indigo?
Indigo, part of Microsoft's Windows operating system code-named Longhorn, unifies a variety of Microsoft technologies (COM+, MSMQ, ASP.NET Web services [ASMX], Remoting) and transports (HTTP, TCP, UDP, IPC) to create a single framework and runtime environment for building distributed systems.
Indigo is suited for building Service Oriented (SO) systems. Service Orientation helps architects and developers design and build connected systems. Service Orientation complements Object Orientation and helps express services in a platform and implementation independent manner.
Services are programs that are communicated with via message exchange. Services are autonomous, which means they exist and run on their own. Functionality exposed by these services are described using standards-based schema and contracts. Many applications can call a service, and the service won't crash if one of the consuming applications breaks. A system is a collection of deployed services cooperating in a given task. Systems are built to adapt to change.
How is it implemented?
Indigo is implemented in .NET; therefore, services are created with any CLR-compliant language. Indigo services are exposed on the wire via standards based technologies (such as XML, XSD, SOAP, WSDL, and other Web services specifications).
What are channels?
Indigo services are bound to the network through one or more channels attached to a port. Each channel is built dynamically at connection time to support the communications requirements negotiated between caller and service. This way, an Indigo service can talk to both a local Indigo service via IPC and a remote client app via HTTP at the same time.
Indigo, part of Microsoft's Windows operating system code-named Longhorn, unifies a variety of Microsoft technologies (COM+, MSMQ, ASP.NET Web services [ASMX], Remoting) and transports (HTTP, TCP, UDP, IPC) to create a single framework and runtime environment for building distributed systems.
Indigo is suited for building Service Oriented (SO) systems. Service Orientation helps architects and developers design and build connected systems. Service Orientation complements Object Orientation and helps express services in a platform and implementation independent manner.
Services are programs that are communicated with via message exchange. Services are autonomous, which means they exist and run on their own. Functionality exposed by these services are described using standards-based schema and contracts. Many applications can call a service, and the service won't crash if one of the consuming applications breaks. A system is a collection of deployed services cooperating in a given task. Systems are built to adapt to change.
How is it implemented?
Indigo is implemented in .NET; therefore, services are created with any CLR-compliant language. Indigo services are exposed on the wire via standards based technologies (such as XML, XSD, SOAP, WSDL, and other Web services specifications).
What are channels?
Indigo services are bound to the network through one or more channels attached to a port. Each channel is built dynamically at connection time to support the communications requirements negotiated between caller and service. This way, an Indigo service can talk to both a local Indigo service via IPC and a remote client app via HTTP at the same time.