|
ActiveMQ
Apache ActiveMQ is an Open-source software, open source message broker written in Java together with a full Java Message Service (JMS) client. It provides "Enterprise Features" which in this case means fostering the communication from more than one client or server. Supported clients include Java via JMS 1.1 as well as several other "cross language" clients. The communication is managed with features such as computer clustering and ability to use any database as a JMS persistence (computer science), persistence provider besides virtual memory, cache (computing), cache, and journal (computing), journal persistency. There's another broker under the ActiveMQ umbrella code-named ''Artemis''. It is based on the HornetQ code-base which was donated from the JBoss community to the Apache ActiveMQ community in 2015. Artemis is the "next generation" broker from ActiveMQ and will ultimately become the next major version of ActiveMQ. History The ActiveMQ project was originally created by its ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
HornetQ
HornetQ is an open-source asynchronous messaging Message-oriented middleware (MOM) is software or hardware infrastructure supporting sending and receiving messages between distributed systems. MOM allows application modules to be distributed over heterogeneous platforms and reduces the complex ... project from JBoss (company), JBoss. It is an example of Message-oriented middleware. HornetQ is an open source project to build a multi-protocol, embeddable, very high performance, clustered, asynchronous messaging system. During much of its development, the HornetQ code base was developed under the name JBoss Messaging 2.0. The HornetQ project is licensed using the Apache Software License v 2.0. As of 4-2-2010 HornetQ is the SPECjms2007 record breaker. History Tim Fox started work on HornetQ in 2007 as JBoss Messaging 2.0. After 2 years of effort, Fox realised the original JBoss Messaging codebase had been almost completely rewritten and it was decided to release it under a diffe ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Apache ServiceMix
Apache ServiceMix is an open-source software project to implement a distributed enterprise service bus (ESB). Architecture ServiceMix is based on the service-oriented architecture (SOA) model. It is a project of the Apache Software Foundation and was built on the semantics and application programming interfaces of the Java Business Integration (JBI) specification JSR 208. The software is distributed under the Apache License. ServiceMix supports the OSGi framework. ServiceMix integrated Spring Framework support and can be run at the edge of the network (inside a client or server), as a standalone ESB provider or as a service within another ESB. ServiceMix is compatible with Java Platform, Standard Edition or a Java Platform, Enterprise Edition application server. ServiceMix uses ActiveMQ to provide remoting, clustering, reliability and distributed failover. The basic frameworks used by ServiceMix are Spring and XBean. ServiceMix is composed versions of Apache ActiveMQ, ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Advanced Message Queuing Protocol
The Advanced Message Queuing Protocol (AMQP) is an open standard application layer protocol for message-oriented middleware. The defining features of AMQP are message orientation, queuing, routing (including point-to-point and publish-and-subscribe), reliability and security. AMQP mandates the behavior of the messaging provider and client to the extent that implementations from different vendors are interoperable, in the same way as SMTP, HTTP, FTP, etc. have created interoperable systems. Previous standardizations of middleware have happened at the API level (e.g. JMS) and were focused on standardizing programmer interaction with different middleware implementations, rather than on providing interoperability between multiple implementations. Unlike JMS, which defines an API and a set of behaviors that a messaging implementation must provide, AMQP is a wire-level protocol. A wire-level protocol is a description of the format of the data that is sent across the network as ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Message Broker
A message broker (also known as an integration broker or interface engine) is an intermediary computer program module that translates a message from the formal messaging protocol of the sender to the formal messaging protocol of the receiver. Message brokers are elements in telecommunication or computer networks where software applications communicate by exchanging formally-defined messages. Message brokers are a building block of message-oriented middleware (MOM) but are typically not a replacement for traditional middleware like MOM and remote procedure call (RPC). Overview A message broker is an architectural pattern for message validation, transformation, and routing. It mediates communication among applications, minimizing the mutual awareness that applications should have of each other in order to be able to exchange messages, effectively implementing decoupling. Purpose The primary purpose of a broker is to take incoming messages from applications and perform some actio ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
OpenWire (binary Protocol)
OpenWire is a binary protocol designed for working with message-oriented middleware Message-oriented middleware (MOM) is software or hardware infrastructure supporting sending and receiving messages between distributed systems. MOM allows application modules to be distributed over heterogeneous platforms and reduces the comple .... It is the native wire format of ActiveMQ. External linksActiveMQ - OpenWire Message-oriented middleware Network protocols {{compu-network-stub ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Apache Camel
Apache Camel is an open source framework for message-oriented middleware with a rule-based routing and mediation engine that provides a Java object-based implementation of the Enterprise Integration Patterns using an application programming interface (or declarative Java domain-specific language) to configure routing and mediation rules. The domain-specific language means that Apache Camel can support type-safe smart completion of routing rules in an integrated development environment using regular Java code without large amounts of XML configuration files, though XML configuration inside Spring Framework is also supported. Camel is often used with Apache ServiceMix, Apache ActiveMQ and Apache CXF in service-oriented architecture projects. Tooling * Several Apache Maven-plugins are provided for validation and deployment. * Graphical, Eclipse-based tooling is freely available from Red Hat. It provides graphical editing and debugging and advanced validation. * Eclipse based tooli ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Service-oriented Architecture
In software engineering, service-oriented architecture (SOA) is an architectural style that focuses on discrete services instead of a monolithic design. By consequence, it is also applied in the field of software design where services are provided to the other components by application components, through a communication protocol over a network. A service is a discrete unit of functionality that can be accessed remotely and acted upon and updated independently, such as retrieving a credit card statement online. SOA is also intended to be independent of vendors, products and technologies. Service orientation is a way of thinking in terms of services and service-based development and the outcomes of services. A service has four properties according to one of many definitions of SOA: # It logically represents a repeatable business activity with a specified outcome. # It is self-contained. # It is a black box for its consumers, meaning the consumer does not have to be aware of the s ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Java Message Service
The Jakarta Messaging API (formerly Java Message Service or JMS API) is a Java application programming interface (API) for message-oriented middleware. It provides generic messaging models, able to handle the producer–consumer problem, that can be used to facilitate the sending and receiving of messages between software systems. Jakarta Messaging is a part of Jakarta EE and was originally defined by a specification developed at Sun Microsystems before being guided by the Java Community Process. General idea of messaging Messaging is a form of '' loosely coupled'' distributed communication, where in this context the term 'communication' can be understood as an exchange of messages between software components. Message-oriented technologies attempt to relax ''tightly coupled'' communication (such as TCP network sockets, CORBA or RMI) by the introduction of an intermediary component. This approach allows software components to communicate with each other indirectly. Benefits o ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Apache CXF
Apache CXF is an open source software project developing a Web services framework. It originated as the combination of Celtix developed by IONA Technologies and XFire developed by a team hosted at Codehaus in 2006. These two projects were combined at the Apache Software Foundation. The name "CXF" was derived by combining "''Celtix''" and "''XFire''". Description CXF is often used with Apache ServiceMix, Apache Camel and Apache ActiveMQ in service-oriented architecture (SOA) infrastructure projects. Apache CXF supports the Java programming interfaces JAX-WS, JAX-RS, JBI, JCA, JMX, JMS over SOAP, Spring, and the XML data binding frameworks JAXB, Aegis, Apache XMLBeans, SDO. CXF includes the following: *Web Services Standards Support: **SOAP **WS-Addressing ** WS-Policy **WS-ReliableMessaging **WS-SecureConversation **WS-Security **WS-SecurityPolicy *JAX-WS API for Web service development **Java-first support **WSDL-first tooling *JAX-RS (JSR 339 2.0) API for RESTful Web service ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Service-Oriented Architecture
In software engineering, service-oriented architecture (SOA) is an architectural style that focuses on discrete services instead of a monolithic design. By consequence, it is also applied in the field of software design where services are provided to the other components by application components, through a communication protocol over a network. A service is a discrete unit of functionality that can be accessed remotely and acted upon and updated independently, such as retrieving a credit card statement online. SOA is also intended to be independent of vendors, products and technologies. Service orientation is a way of thinking in terms of services and service-based development and the outcomes of services. A service has four properties according to one of many definitions of SOA: # It logically represents a repeatable business activity with a specified outcome. # It is self-contained. # It is a black box for its consumers, meaning the consumer does not have to be aware of the s ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
MQTT
MQTT (originally an initialism of MQ Telemetry Transport) is a lightweight, publish-subscribe, machine to machine network protocol for Message queue/Message queuing service. It is designed for connections with remote locations that have devices with resource constraints or limited network bandwidth. It must run over a transport protocol that provides ordered, lossless, bi-directional connections—typically, TCP/IP. It is an open OASIS standard and an ISO recommendation (ISO/IEC 20922). History Andy Stanford-Clark ( IBM) and Arlen Nipper (then working for Eurotech, Inc.) authored the first version of the protocol in 1999. It was used to monitor oil pipelines within the SCADA industrial control system. The goal was to have a protocol that is bandwidth-efficient, lightweight and uses little battery power, because the devices were connected via satellite link which, at that time, was extremely expensive. Historically, the "MQ" in "MQTT" came from the IBM MQ (then 'MQSeries') pro ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Streaming Text Oriented Messaging Protocol
Simple (or Streaming) Text Oriented Message Protocol (STOMP), formerly known as TTMP, is a simple text-based protocol, designed for working with message-oriented middleware (MOM). It provides an interoperable wire format that allows STOMP clients to talk with any message broker supporting the protocol. Overview The protocol is broadly similar to HTTP, and works over TCP using the following commands: *CONNECT *SEND *SUBSCRIBE *UNSUBSCRIBE *BEGIN *COMMIT *ABORT *ACK *NACK *DISCONNECT Communication between client and server is through a "frame" consisting of a number of lines. The first line contains the command, followed by headers in the form : (one per line), followed by a blank line and then the body content, ending in a null character. Communication between server and client is through a MESSAGE, RECEIPT or ERROR frame with a similar format of headers and body content. Example SEND destination:/queue/a content-type:text/plain hello queue a ^@ Implementations Thes ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
