COM DCOM MTS COM COM Component Object Model

COM DCOM MTS COM+

COM – Component Object Model Since 1992 A framework for creating and using components v v Makes software easier to write and reuse Provides widest choice in services, tools, languages, and applications Features v v Any Programming Language Integrated with Development Tools Flexible Security Mature specification and reference implementation

COM – Component Object Model In the same process Fast, direct function calls On the same machine Fast, secure IPC Client Component Client Process Client COM Server Process Component

DCOM – Distributed COM Added features v v Services used in a standard way, regardless of location Multiple Network Transports Across machines Secure, reliable and flexible DCE-RPC based DCOM protocol Client Machine Client Server Machine DCE COM RPC Component

DCOM – Distributed COM Clients C O M TCP, UDP IPX, SPX HTTP C O M Queued Client Machine Server Machine COM Object

MTS – Microsoft Transaction Server Since 1996 v NT 4. 0 Option Pack Combines the features of v v TP monitor Object Request Broker Features v v Transactions Scalability services Connection Management Administration

COM+ 1. 0 Since 1997 v 1. 0 with Windows 2000 As easy to develop Server Components as it is to develop Client Components As easy to deliver enterprise apps as it is to deliver workgroup apps! Consists of v v v Runtime Services Invocation

Technology Scenario COM+ MTS COM+ Services: Events Security Load Balancing Queued Components In Memory Database Compensating COM+Resource Manager caring, sharing Administration The environment for your components MTS Services: Transactions Resource Pooling Security Administration The Model Tools Support Multi-Language Discovery (QI)

Enterprise Services COM+ continues to involve v v Successor to MTS and COM+ 1. 5 in Windows 2003 & Windows. XP In. NET, those types are know under the name v . NET Enterprise Services The. NET Enterprise Services are today a wrapper around the COM+ Service v v Enterprise Services will move in the CLR over time Are a strategic part of. NET

Enterprise Services Provides support for v v v v Distributed Transactions Security Object Pooling Just in time activation Queued Components Loosely Coupled Events Server Application Process Model ES is the programming model that will most resemble the Indigo programming model.

What is Indigo? a unified programming model and communications infrastructure for developing connected systems the best features of. NET Remoting, ASMX, System. Messaging and. NET Enterprise Services into a unified programming and administration model deep support for standards - including XML, SOAP, WSDL, and WS-* - makes it easier to integrate applications and services without sacrificing security or reliability

Indigo and Unification Application ASMX . NET Remoting Enterprise Services System. Messaging Services Queuing Eventing Simple Config Broad Vision Routing Attributes Interoperable Extensibility Transactions Service Model. Object-Oriented Service-Oriented Components Instance Manager Context Manager Discovery Queuing Reliable Msg Durable Msg Type Declarative Transacted Integration Behaviors Methods Service Methods Port Channels (Datagram, Reliable, Peer, …) Policy Engine Transport Channels (IPC, HTTP, TCP…) Channel Security Indigo Message Encoder Hosting Environments ASP. NET . container . exe NT Service Dll. Host Indigo will superset of the features of our existing stacks

Conclusion COM+ 1. 5 takes Microsoft’s enterprise component architecture to the next level Better scalability v v Application Pooling Adjustable transaction isolation level Better administration v v Ability to disable/pause for updates Process dump feature Better reliability v v Recycle applications upon predefined triggers Limit activations with memory gates Better flexibility v v v Web Services Service Without Component aliasing Better productivity v Enterprise Services namespace