Middleware definitions and overview

Transcription

1 Middleware definitions and overview Chantal Taconet CCN/CSC7321 octobre 2017 Revision : 545

2 Outline 1 Which middleware? Families of middleware Middleware for separation of concerns purpose Which technology for which situation Layer view of some middleware frameworks Conclusion Télécom SudParis INF octobre 2017 CCN/CSC7321 2/23

3 1 Which middleware???? JavaEE RPC JMS SOAP ESB AMQP DEBS SOA CORBA DDS B2C P2P SCA WebService Hibernate Struts IIOP CORBA REST RMI B2B EJB Spring WSDL MOM M2M EAI A wide number of middleware technologies are hidden under those acronyms! Télécom SudParis INF octobre 2017 CCN/CSC7321 3/23

4 1 Which middleware? 1.1 Middleware definitions Several definitions a Middleware is software glue. Middleware is the slash in Client/Server Software that mediates between an application program and a network. Middleware is computer software that connects software components or applications. It is used most often to support complex, distributed applications. It includes web servers, application servers, content management systems, and similar tools that support application development and delivery. Middleware is especially integral to modern information technology based on XML, SOAP, Web services, and service-oriented architecture. It goes on to say that it describes a piece of software that connects two or more software applications so that they can exchange data. Middleware is any software that allows other software to interact. a. Found on and Middleware Télécom SudParis INF octobre 2017 CCN/CSC7321 4/23

5 1 Which middleware? Middleware is sometimes called plumbing because it connects application and passes data between them. Middleware is software used for coupling high level system components (application) with basic system components (data and network) Télécom SudParis INF octobre 2017 CCN/CSC7321 5/23

6 1 Which middleware? 1.2 Middleware : a picture Presentation Layer MVC (Struts) System 1 Application Logic Middleware Application Logic System 2 Data Storage Layer persistency (JavaEE,Hibernate) Network Layer RPC, RMI, CORBA, SOAP MOM (JMS) Télécom SudParis INF octobre 2017 CCN/CSC7321 6/23

7 1 Which middleware? 1.3 Middleware as a universal adapter to build high level applications? Télécom SudParis INF octobre 2017 CCN/CSC7321 7/23

8 2 Families of middleware RPC middleware Object Middleware Message Oriented Middleware Component Middleware Service Middleware Database middleware Persistency middleware Transactional middleware Télécom SudParis INF octobre 2017 CCN/CSC7321 8/23

9 2.1 Middleware history 2 Families of middleware BEA WLS IBM WebSphere JBoss AS Apache Axis Eclipse WTP Microsoft.NET SOAP & WSDL BEA Tuxedo IBM Encina EJB & JTA JMS RMI RMI R 1998 XML Arjuna R 1989 Recoverability R 1988 OMG OTS 1994 BEA MQ TIBCO TIB Network Objects R 1993 DEC MQ InformationBus R 1992 RPC Systems DEC FUSE Orca R 1989 Emerald R 1987 ONC Field R 1987 Cedar RPC R 1984 ANSA CORBA SGML R 1986 GML R 1981 Nested transaction R 1980 RPC R 1981 Mesa R 1979 Module Interconnection Language R 1976 Scribe R 1981 Télécom SudParis INF octobre 2017 CCN/CSC7321 9/23

10 3 Middleware for separation of concerns purpose Middleware is a solution for the separation of concern paradigm Through middleware, separation of concern is reached for : Heterogeneity Distribution of pieces of software Persistency of components Transactions (including a set of requests in a transaction) Security issues New middleware for new preoccupations (e.g., context-awareness) Separation of concern enables application designers to focus on their business (more time to implement business components, use standard middleware components for handling other preoccupations). Télécom SudParis INF octobre 2017 CCN/CSC /23

11 3 Middleware for separation of concerns purpose 3.1 Levels of heterogeneity addressed by middleware Middleware may address several level of heterogeneity Hardware heterogeneity (e.g., Little Endian and Big Endian representation) Operating System heterogeneity (e.g., library availability) Language heterogeneity (e.g., one piece of software in C, another piece of software in java Application logic heterogeneity (e.g., data transformation from one application to the other) Télécom SudParis INF octobre 2017 CCN/CSC /23

12 3 Middleware for separation of concerns purpose 3.2 Middleware for several levels of distribution pieces of software connected by middleware may be distributed on : Several processes (in the same computer) Several computers (in the same local area network) Several networks (in the same company) Several companies Télécom SudParis INF octobre 2017 CCN/CSC /23

13 3 Middleware for separation of concerns purpose 3.3 Examples of software distribution Middleware Télécom SudParis INF octobre 2017 CCN/CSC /23

14 4 Which technology for which situation 4.1 Interaction styles Object/Service/Component lifecycle : servers and containers Data management Presentation middleware Service Oriented Architecture Component based Architecture Architectural styles Télécom SudParis INF octobre 2017 CCN/CSC /23

15 4.1 Interaction styles 4 Which technology for which situation Middleware for distributed synchronous requests (network layer) RPC : request broker, CORBA : object request broker, multi-languages, Local Area Network (LAN) RMI : object request broker, java, LAN Web services (synchronous messages) : request broker, multi-languages, Wide Area Network, service orchestration, clouds Message Oriented Middleware (MOM) (network and data layers) JMS, LAN DEBS AMQP ESB Enterprise Service Bus, WAN EAI Enterprise Application Integration, data exchange, WAN Télécom SudParis INF octobre 2017 CCN/CSC /23

16 4 Which technology for which situation 4.2 Object/Service/Component lifecycle : servers and containers Application server manager : instantiation, containers Application Servers JavaEE (JBoss, glassfish, Websphere) : Light servers : Spring Web container : Web Server (tomcat, jetty, LiteWebServer : Télécom SudParis INF octobre 2017 CCN/CSC /23

17 4.3 Data management 4 Which technology for which situation Data Oriented Middleware (network and data layers) EAI Enterprise Application Integration, data exchange, WAN REST (Representational State Transfer), DDS Data Distribution Service Transaction middleware : several requests in a same transaction (commited or rollbacked) (network layer) JavaEE (EJB), includes transaction management Persistency middleware handles persistency of data or objects (data layer) JavaEE (EJB) includes persistency preoccupation (various technologies) Hibernate is a persistency framework (from object to relational database paradigm) Télécom SudParis INF octobre 2017 CCN/CSC /23

18 4.4 Presentation middleware 4 Which technology for which situation Presentation middleware : handles presentation of information (presentation layer) Struts Web presentation of components through the MVC approach (Model View Controler) Télécom SudParis INF octobre 2017 CCN/CSC /23

19 4.5 Service Oriented Architecture Service Oriented Architecture (for sequence of services) Service abstraction Service Orchestration Workflow of services 4 Which technology for which situation a. Source de la figure https :// Télécom SudParis INF octobre 2017 CCN/CSC /23

20 4.6 Component based Architecture 4 Which technology for which situation Component abstraction Component Assembly (e.g. SCA Service Component Architecture, Fractal components, CORBA Component Model) Télécom SudParis INF octobre 2017 CCN/CSC /23

21 4.7 Architectural styles 4 Which technology for which situation P2P (peer 2 peer) M2M (machine 2 machine) B2B Business 2 business B2C Business 2 consumers 3 tiers Presentation Application logic Persistency Télécom SudParis INF octobre 2017 CCN/CSC /23

22 5 Layer view of some middleware frameworks Structural Compositions Activity Orchestrations SCA BPEL Application servers Life cycle (instantiate) Persistency JavaEE Distributed Event Based System RabbitMQ WebServices/JavaRMI/CORBA Synchronous Distributed Requests sockets TCP/UDP Télécom SudParis INF octobre 2017 CCN/CSC /23

23 6 Conclusion Choice of a middleware may be decided lately when designing an application (Model Driven Architecture). Middleware may connect pieces of software implemented separately and available on the network. Standardisation is essential to connect pieces of software Universal adapter is of course not possible : Many technologies are available with different characteristics (e.g., target platform, semantics, efficiency) The basic of middleware is about distribution (RPC, RMI, MOM, SOAP) sometimes called plumber solutions. Above distribution, higher abstractions may be built : publish/subscribe, data distribution, persistency, transactions, presentation, naming, workflow, orchestration and composition. Télécom SudParis INF octobre 2017 CCN/CSC /23