Middleware in Context: 2016 David E. Bakken. Cpt. S 464/564 Lecture Auxiliary Material (not from text) January 30, 2019

Transcription

1 Middleware in Context Prof. Dave Bakken Cpt. S 464/564 Lecture Auxiliary Material (not from text) January 30, 2019

2 Sources of Info D. Bakken, Middleware, unpublished article (from an Encyclopedia of Distributed Systems that was cancelled) from ca. 2000, Some of the example systems are a bit dated, but the first page describes the benefits of middleware very concisely. David E. Bakken, Washington State University, Pullman WA, Richard E. Schantz, BBN Technologies, Cambridge MA, Richard D. Tucker, Tucker Engineering Associates, Locust NC Smart Grid Communications:QoS Stovepipes or QoS Interoperability?.. Technical Report TR-GS-013, School of Electrical Engineering and Computer Science, Washington State University, November, TR-GS-013.pdf Won a best paper award REQUIRED READING FOR BOTH 464,564 Explains what middleware is, ways in which it is standardized, etc.

3 Context: (Most) Technology Marches On Hardware technology s progress phenomenal in last few decades Moore s Law Metcalf s Law Graphics processing power Software technology s progress is much more spotty Software crisis Yet SW is a large and increasing part of complex apps/systems! Apps and systems are rapidly becoming (more) networked Oops, distributed software is much harder yet to get right Middleware a promising technology for programability of distributed systems Also fertile grounds for adaptivity and dependability.

4 Why Middleware? Middleware == A layer of software above the operating system but below the application program that provides a common programming abstraction across a distributed system Middleware exists to help manage the complexity and heterogeneity inherent in distributed systems Middleware provides higher-level building blocks ( abstractions ) for programmers than the OS provides Can make code much more portable Can make them much more productive Can make the resulting code have fewer errors Analogy MW:sockets HOL:assembler Middleware sometimes is informally called plumbing Connects parts of a distributed application with data pipes and passes data between them

5 Middleware in Context Host 1 Host 2 Distributed Application Client Distributed Application Server Middleware API Middleware Middleware API Middleware Operating System API OS Comm. Processing Storage Operating System API OS Comm. Processing Storage Network

6 Middleware Benefit: Masking Heterogeneity Middleware s programming building blocks mask heterogeneity Makes programmer s life much easier!! Kinds of heterogeneity masked by middleware (MW) frameworks All MW masks heterogeneity in network technology All MW masks heterogeneity in host CPU Almost all MW masks heterogeneity in operating system (or family thereof) Notable exception: Microsoft middleware (de facto; not de jure or de fiat) Almost all MW masks heterogeneity in programming language Noteable exception: Java RMI Some MW masks heterogeneity in vendor implementations CORBA best here

7 Middleware Benefit: Transparency Middleware can provide useful transparencies: Access Transparency Location transparency Concurrency transparency Replication transparency Failure transparency Mobility transparency Masking heterogeneity and providing transparency makes programming distributed systems much easier to do!

8 Programming with Middleware Programming with Middleware Do not have to learn a new programming language! (Usually) Use an existing one already familiar with: C++, Java, C#, Ada, (yuk) Visual Basic, (yuk) COBOL Ways to Program with Middleware 1. Middleware system provides library of functions (Linda, others) 2. Support directly in language from beginning (Java and JVM s RMI) 3. External Interface Definition Language (IDL) that maps to the language and generates local proxy IDL looks a lot like C++ class definitions with a few other keywords, and no object state Run an IDL compiler that generates proxy files (source and header) for any languages supported

9 9 Middleware vs. Sockets Middleware is much easier to program! Example interface from CORBA (OMG) IDL: module HelloApp { interface Hello { bool MyFunction(in float a, in string b, in int c, in string d, in float e, out double ret); }; };

10 10 Middleware vs. Sockets(2) Calling that interface in C++ with CORBA boolean success = helloimpl.myfunction(3.3, hello, 2345, bakken!, 67.34, doublebox);

11 11 Middleware vs. Sockets (3) float a; char b[5]; int c;char d[7]; float e; double rval; int success //Ignore read errors. Hardcode field size, assume //all systems are same CPU arch. and bit size read(socket, &a, sizeof(float)); read(socket, b, sizeof(char) * 5); read(socket, &c, sizeof(int)); read(socket, d, sizeof(char)*7); read(socket, &e, sizeof(float)); // continued on next slide

12 12 Middleware vs. Sockets (4) // continued from previous slide calculating return values etc goes here //send back return value write(socket, &rval, sizeof(double)); //cant tell if it actually was recieved, or if socket is broken write(socket, &success, sizeof(int)); //again, no error checking

13 13 Middleware vs. Sockets (5) This socket code ignored all of the following: Errors with the socket Differences in system architecture Differences in CPU endianness Differences in representation of data types between languages I/O errors All of the above (and much more) are handled by middleware Middleware s programming building blocks (abstractions) mask heterogeneity Makes programmer s life much easier!!

14 Kinds of Middleware Distributed Tuples: (a, b, c, d, e) Relational databases, SQL, relational algebra Linda and tuple spaces JavaSpaces (used by Java Jini) Remote procedure call (RPC) make a function call look local even if non-local Message-Oriented Middleware (MOM) messages and message queues Data/topic-based publish-subscribe (quite popular) Distributed Object Middleware Make an object method look local even if non-local CORBA DCOM/SOAP/.NET Java RMI

15 Middleware Category Kinds of Middlware (cont.) Different middleware systems encapsulate and integrate the different kinds of resources with varying degrees: Distributed Tuples Remote Procedure Call Message- Oriented MW Data/Topic Based Distributed Objects Communication Processing Storage Yes Limited Yes Yes Yes No Yes No Limited Yes No Limited Yes Yes Yes For many (non-database) applications, and supporting adaptation, distributed object middleware is better because it is more general But pub sub and tuples are more decoupled which can help

16 Middleware and Legacy Systems Legacy systems are a huge problem (and asset) in industry and military domains! Middleware often called a glue technology: integrated legacy components Much distributed programming involves integrating components, not building them from scratch! Middleware s abstractions are general enough to allow legacy systems to be wrapped Distributed objects are best here because more general End result: a very high-level lowest common denominator of interoperability

17 Multi-Layered Middleware

18 One Middleware Layering Taxonomy (BBN/Schantz) Domain-Specific Services Services and APIs tailored to (and reusable only within) certain domains (health care, telecommunications, etc) Examples: CORBA Domain Interfaces, Boeing Bold Stroke architecture Common MW Services Adds high-level, domain-independent reusable services for events, fault tolerance, security, Examples: CORBAServices, Eternal Distribution MW Provides rich distributed object model that supports much heterogeneity and transparency Examples: CORBA,.NET., Java RMI Infrastructure MW Encapsulates core OS Comm. and concurrency services (sometimes enhances them too) Examples: JVM (and other VMs), ACE, group comm. (Figure courtesy of D. Schmidt)

19 CORBA and System Builders Hooks Interface Implementation IDL Compiler Repository Repository Client Servant Smart Stub Stub/proxy (SII) DII ORB Interface ORB Interface Skeleton DSI Object Adaptor Interceptor Interceptor ORB core ORB core Interceptor Interceptor Standard Interfaces IDL-generated ORB-Specific

20 CORBA DOC MODEL QUO/CORBA DOC MODEL Quality Objects (QuO) Dave Bakken QuO Adds Specification, Measurement, and Adaptation into the Distributed Object Model CLIENT IDL STUBS OBJ REF in args operation() out args + return value Network OBJECT (SERVANT) IDL SKELETON ORB IIOP IIOP ORB OBJECT ADAPTER Application Developer Mechanism Developer CLIENT OBJ REF in args operation() out args + return value OBJECT (SERVANT) Application Developer Delegate IDL STUBS SysCond Contract SysCond MECHANISM/PROPERTY MANAGER Network SysCond Contract SysCond IDL SKELETON Delegate ORB IIOP IIOP ORB OBJECT ADAPTER QuO Developer Mechanism Developer

21 CORBA DOC MODEL QUO/CORBA DOC MODEL Quality Objects (QuO) Dave Bakken QuO Adds Specification, Measurement, and Adaptation into the Distributed Object Model CLIENT IDL STUBS OBJ REF in args operation() out args + return value Network OBJECT (SERVANT) IDL SKELETON ORB IIOP IIOP ORB OBJECT ADAPTER Application Developer Mechanism Developer CLIENT OBJ REF in args operation() out args + return value OBJECT (SERVANT) Application Developer Delegate IDL STUBS SysCond Contract SysCond MECHANISM/PROPERTY MANAGER Network SysCond Contract SysCond IDL SKELETON Delegate ORB IIOP IIOP ORB OBJECT ADAPTER QuO Developer Mechanism Developer