1 / 11

Overview of Microsoft Transaction Server and COM Technology Evolution

This overview delves into Microsoft Transaction Server (MTS) and Component Object Model (COM) technology, highlighting their evolution since circa 1990. MTS aims to facilitate easy creation of OLTP applications, enabling code cooperation across different organizations using various languages and compilers. With a massive $1 billion market in third-party objects, COM provides a binary, runtime standard that promotes interface-focused development. The text covers the significance of distributed computing via proxy/stub technology and emphasizes the importance of language choice and integration within large systems.

akina
Télécharger la présentation

Overview of Microsoft Transaction Server and COM Technology Evolution

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Microsoft Transaction ServerCOM + Jim LyonHPTS ’99

  2. COM Overview • Original goal: allow code from different organizations to cooperate inside a process. • Different compilers. • Different languages. • Different release schedules. • Wildly successful: • Introduced circa 1990. • Underlies OLE. • $1billion market in third-party objects. • On every windows system, and some others.

  3. COM Overview • Basic concept: interface pointer • Expresses function signature contract and some semantics. • Similar to Java interface. • Each object implements 1 or more interfaces. • Dynamically discoverable. • Single inheritance of interface definitions.

  4. COM Overview • COM is a binary, runtime standard: • Interface pointer: a pointer to a pointer to an array of pointers to functions. • Completely neutral to language or runtime environment. • Supported from C, C++, VB, Cobol, Java, and various interpreters, and a host of third-party environments.

  5. COM Evolution • Distributed COM (1995) • Put clients and servers on different machines, via proxy/stub technology. • MTS (1996, 1998), COM+ (2000) • Add declarative behavior to server objects.

  6. MTS, COM+ • Goal: Make it easy to create OLTP applications. • Design points: • Allow programmer to think serially • Leave the multithreading to us • Get system services declaratively.

  7. MTS Services • Security (access control, auditing) • Serialization • Transactions • Object lifetime • Others • Model largely copied by EJB.

  8. MTS is Winning Does your organization use MTS? Project Phases Yes (85%) No (15%)

  9. Success Factor:Your Choice of Languages Programmer Population Language Use with MTS

  10. Other Success Factors • Microsoft is focused on making it work. • Consortia are frequently focused on: • Getting a spec published. • Ensuring that no competitor gets an advantage. • Trying to fight a common enemy. • Religion (“write once, debug everywhere”)

  11. Other Success Factors • Integration • Push the ORB into the OS. • Push the Web Server into the OS. • Evolution “Every large system that works has evolved from a small system that worked.” (Fred Brooks)

More Related