Message-oriented middleware

Message-oriented middleware
Name	Message-oriented middleware
Developer	IBM, Oracle Corporation, Red Hat, Apache Software Foundation, Microsoft
Released	1990s
Programming language	Java (programming language), C++, C#
Operating system	Linux, Microsoft Windows, macOS
Genre	Middleware
License	Proprietary, Apache License

Message-oriented middleware

Message-oriented middleware provides asynchronous communication between distributed applications by exchanging messages via intermediaries to decouple software components and enable reliable, scalable integration across heterogeneous systems. Implementations span commercial vendors and open-source projects from IBM to the Apache Software Foundation and are used across enterprise, cloud, and embedded environments where systems such as SAP SE, Salesforce, Twitter, Netflix (service) and Amazon (company) require resilient integration. Designers draw on influences from early messaging systems at Sun Microsystems, Microsoft, and research from institutions like Massachusetts Institute of Technology and Stanford University.

Overview

Message-oriented middleware sits between client (computing)s and server (computing)s to enable asynchronous, loosely coupled communication, often via message brokers, queues, or topics developed by vendors such as IBM's WebSphere MQ, Oracle Corporation's Oracle AQ, Red Hat's AMQ, and projects like Apache ActiveMQ and RabbitMQ. It intersects with architectures promoted by Amazon Web Services, Google Cloud Platform, Microsoft Azure and standards driven by organizations like the Object Management Group and Internet Engineering Task Force. Key adoption drivers include integration of legacy systems at Bank of America, event-driven designs at Netflix (service), and microservices at companies such as Uber Technologies and Airbnb.

Architecture and Components

Typical deployments include brokers, queues, topics, producers, consumers, adapters, and connectors from vendors like TIBCO Software and Solace Systems. Brokers implement features pioneered by research groups at Carnegie Mellon University and products from Oracle Corporation; connectors integrate with databases such as Oracle Database, Microsoft SQL Server, and platforms like Salesforce. Client libraries for Java (programming language), C#, C++, and scripting languages enable producers and consumers to interact with brokers; management consoles and monitoring tools from Splunk, Datadog, and Prometheus (software) provide operational visibility. High-availability patterns leverage clustering and replication as used by Red Hat's offerings and cloud-native designs promoted by Kubernetes and Docker ecosystems.

Messaging Models and Patterns

Common models include point-to-point queuing exemplified by IBM deployments and publish–subscribe used by Apache Kafka and Eclipse Mosquitto in IoT scenarios pioneered by Cisco Systems collaborations. Patterns such as request–reply, work queues, competing consumers, and dead-letter queues derive from enterprise designs at Goldman Sachs and JPMorgan Chase. Architectural patterns—event sourcing used by EventStore (software) and CQRS promoted in systems at Microsoft—are frequently combined with middleware to enable eventual consistency and replayability in systems at PayPal and Stripe (company).

Protocols and Standards

Interoperability relies on protocols and standards such as Advanced Message Queuing Protocol, Message Queuing Telemetry Transport, AMQP, MQTT, Streaming Text Oriented Messaging Protocol, and implementations influenced by specifications from the Internet Engineering Task Force and OASIS. JMS (Java Message Service) from Sun Microsystems standardized Java APIs used across Oracle Corporation and IBM products. Security and management extensions reference work by IETF and specifications used by Amazon Web Services and Google Cloud Platform to integrate with cloud messaging and serverless platforms.

Use Cases and Applications

Enterprises deploy messaging middleware for order processing at Walmart, payment processing at Visa (company), telemetry ingestion at SpaceX, sensor networks in deployments by Siemens, and real-time analytics at Facebook. Cloud-native applications at Netflix (service) and Uber Technologies use middleware for resilience and scaling; telecom operators like AT&T and Verizon Communications use message brokers for signaling and billing. Healthcare providers integrate medical devices and electronic health records using standards-driven adapters from vendors such as GE Healthcare and Philips.

Performance, Scalability, and Reliability

Scalability approaches include sharding, partitioning (as popularized by Apache Kafka), broker federations from Red Hat, and elastic scaling on Amazon Web Services and Google Cloud Platform. Reliability mechanisms—persistent storage, replication, acknowledgements, and transactions—trace to enterprise requirements in systems built by IBM and financial institutions like Goldman Sachs. Benchmarks and tuning practices from vendors and research at MIT and Stanford University focus on throughput, latency, and end-to-end durability under workloads encountered by Twitter and LinkedIn.

Security and Management Practices

Security practices incorporate authentication (OAuth standards from IETF work), authorization integrated with LDAP directories and Active Directory (Microsoft), encryption in transit (TLS specified by IETF) and at rest, and auditing for compliance with laws like Sarbanes–Oxley Act and regulations applied in sectors such as finance and healthcare enforced by entities like the U.S. Department of Health and Human Services. Management combines logging, tracing with tools like Jaeger (software) and Zipkin (software), monitoring via Prometheus (software), and governance frameworks used by organizations such as The Open Group and OASIS.

Category:Middleware