Academic literature on the topic 'Message-Oriented Middleware'

Recent advances in embedded technologies have enabled cell phones tobecome powerful multihomed computing devices and hosts to a wide rangeof applications. However, communication between the device and the outsideworld is still a complicated task because the device is mobile, the connectionis intermittent, the signal strength varies greatly and the communicationoptions are heterogeneous. Previous work has suggested that communicationwith these devices is simplied and enhanced with the use of message orientedmiddleware (MOM).MOMs generally allow the exchange of small messages on an IP networkusing communication patterns such as notication, request/reply and pub-lish/subscribe. However, mobile devices also support non-IP networks suchas the short message service (SMS). SMS can be seen as a MOM that isadministered by a Mobile Network Provider (MNO). The advantage is itsubiquity and privileged access to the status of the device. Additionally, mo-bile devices can be reached simultaneously on multiple networks, but MOMsdo not support this functionality.In this work, we introduce a mobility middleware that will improve currentMOM. Our mobility middleware uses a utility-based scheme for automati-cally choosing one of three network types: MNO, WiFi and the SMS. Theselection scheme makes a decision using context information from the net-work, the user preferences, the application preferences and the infrastructure.Additionally, delay-tolerant application can use our mobility middleware todelay messages in order to improve the utility. We also guarantee FIFOordering and at-most-once delivery, at-least-once delivery or at-least-onceprocessing as required. Finally, we implement our solution with a Java MEclient and a Java middleware and evaluate the performance impact of addingour mobility middleware to a MOM.<br>Des avancements technologiques récents sur les systèmes embarqués ont permis aux cellulaires de devenir des puissants appareils et hôtes d'une panoplie d'applications. Cependant, la communication entre l'appareil et l'extérieur est encore une tâche compliquée parce que l'appareil est mobile, la connexion est intermittente, le signal varie et les options de communications sont hétérogènes. Des travaux passés ont suggéré que la communication avec ces appareils est simplifié et augmenté par l'utilisation d'un intergiciel par envoie de messages (MOM).Les MOMs permettent l'échange de petits messages sur un réseau IP tout en utilisant plusieurs modèles de communication tels que la notification, la transmission sur demande et la publication-souscription. Toutefois, les cellulaires supportent aussi les réseaux non IP tel que le service de minimessages (SMS). Le SMS peut être considéré comme un MOM qui est administré par un fournisseur de service sans-fil. L'avantage du SMS est sont ubiquité et sont accès privilégié au statu du cellulaire. De plus, les téléphones mobiles peuvent communiquer sur plusieurs réseaux simultanément, mais les MOMs ne supportent pas cette fonctionnalité.Dans ce travail, nous introduisons un intergiciel pour la mobilité permettant l'amélioration des MOMs suivant le protocole AMQP pour utilisant avec les téléphones intelligents. Notre intergiciel pour la mobilité utilise un modèle d'utilité pour choisir un canal de communication approprié entre les fournisseurs de service sans-fil, Wifi et le SMS. Le modèle d'utilité fait une décision à partir de l'information du contexte courant du réseau, des préférences de l'usager, des préférences de l'application ainsi que de l'infrastructure. De plus, les applications qui supportent un délai peuvent utiliser notre intergiciel pour la mobilité pour introduire un délai pour introduire un délai et améliorer l'utilité. Nous garantissons l'ordre premier entré et premier sortis des messages ainsi que la livraison au plus une fois, au moins une fois ou le traitement au moins une fois tel que requis. Finalement, nous implémentons un client Java ME ainsi qu'un intergiciel Java et nous évaluons l'impact sur la performance de l'introduction de notre intergiciel pour la mobilité à un MOM.

Message-oriented middleware (MOM) is a middleware used for communication between applications. There are many different MOM technologies available today, each offering different performance (throughput and latency). The performance of MOMs depends on both message size and message guarantee settings used. The problem is that it can be difficult for users to know which MOM they should choose given their requirements. The goal was to create a performance (latency and throughput) comparison of three popular MOMs; Apache Kafka, RabbitMQ and Nats Streaming. The result shows that Kafka is the best performing MOM for smaller message sizes (under 512 bytes). RabbitMQ has the best performance for larger message sizes (over 32768 bytes). Nats Streaming only outperformed the other message system for a few combinations of message guarantee settings with the message size 4096 bytes.<br>Meddelandeorienterad mellanprogramvara (MOM) är mellanprogramvara som används för kommunikation mellan applikationer. Det finns många MOM system som erbjuder olika prestanda (genomströmning och latens). Prestandan är beroende av vilka meddelandegarantier som används samt meddelande storlek. Detta gör det svårt för användare att välja MOM utifrån sina krav. Målet är därför att jämföra tre populära MOMs; Apache Kafka, RabbitMQ och Nats Streaming. Resultaten visar att Kafka presterar bäst med små meddelandestorlekar (Under 512 bytes). RabbitMQ presterar bäst för större meddelanden (Över 32768 bytes) medans Nats Streaming enbart presterar bäst med ett begränsat antal meddelandegarantier och med en meddelandestorlek på 4096 bytes.

Includes bibliographical references.<br>This thesis presents an investigation and evaluation of a Real-Time Message-Oriented Middleware (MOM) implementation using commercial off-the-shelf (COTS) software components. The Application Interface Services (APIS) is an implementation of a real-time MOM that provides network services to sub-systems of a large-scale distributed system. It is shown that the characteristics of a MOM are well suited to a real-time message distribution application and that APIS, as an implementation of a real-time MOM, can provide a heterogeneous network interlace to subsystems of a distributed real-time nature. This simplifies the task of implementing information exchange and provides a definitive boundary for assigning responsibility during system design and development.

Many different message-oriented middlewares (MOM) exist today on the market. With different underlying designs, purposes and features, it is not easy to make the right choice of MOM for your system. The IT company Nordicstation is in such a situation where they need to make a choice of MOM. They currently own a system called Sharelock which generates reports about violations of financial assets trad- ing. They wish to make the process of generating a report more asynchronous by using a MOM and they have a couple of requirements. This thesis was carried out with the purpose of finding the most suitable products for the system in mind, compare their features, performance, licenses and ease-of- use. This was accomplished by analysing their installation process, monitoring in- terfaces, documentation on their websites and performance in a simple throughput test. The results showed that RabbitMQ was the strongest candidate. It had good per- formance, an attractive web interface for monitoring, an easy installation and it also offered commercial support. Apache Artemis was also found to be an attractive choice but it did not have a web interface which made it hard to manage the system.<br>Idag finns det många meddelandebaserade mellanprogramvaror (MOM) på marknaden. Dessa har olika grundläggande designer, syften och kännetecken vilket kan göra det svårt att göra ett bra val av MOM för ett visst system. IT-företaget Nordicstation befinner sig i en sådan situation där de behöver göra ett val av MOM. De har ett system som kallas Sharelock som genererar rapporter om regelbrott in- om värdepappershandeln. De vill göra processen mer asynkron genom att använda en MOM och de har ett antal krav på produkten. Det här examensarbetet utfördes med syftet att hitta de mest passande produkter- na för det tänka systemet, jämföra deras särdrag, prestanda, licenser och anvä- ndarvänlighet. Detta gjordes genom att analysera deras installationsprocess, övervakningsgränssnitt, dokumentation på deras hemsida och prestanda i ett en- kelt prestandatest. Resultaten visade att RabbitMQ var den starkaste kandidaten. Den hade bra prestanda, ett attraktivt webbgränssnitt, en enkel installation och den erbjöd också kommersiell support åt kunder. Apache Artemis var också ett attraktivt val men den hade inget webbgränssnitt vilket gjorde det svårt att övervaka och hantera sys- temet.

The democratization of Internet allowed many more people to use online services and enjoy their benefits. The traffic towards websites became tremendous those recent years, especially with the apparition of social networks. Mobile application, televisions and other non--‐computer devices also get connected to the Internet and use it to provide services to the end--‐users: Video on--‐demand, music streaming and so on. These applications rely on powerful backend servers that handle the requests made by devices and provide statistics and metrics about application usage. These metrics can be generated by aggregating the access logs (e.g. HTTP requests log), logs that are potentially extremely large. Big data tools and analytics, providing a way to handle this huge number of records, come then in hand, as typical client--‐server architectures, with a single database storing all the data, reach their limits in terms of performance and capacity. Data duplication, combined to dedicated and specialized databases storing it, is the key to efficient data handling.   How to fill up these databases in an elegant, efficient and scalable manner is the remaining question, and message--‐oriented middleware may be a viable answer. This project aims at exploring the capabilities of such middleware, identifying what are the benefits and the drawbacks in using them and presenting how they can be integrated in a real--‐world application that needs to aggregate events and logs on a large scale. Apache Kafka and RabbitMQ, two message--‐oriented middleware, are benchmarked and compared, on both performance metrics and qualitative criteria. A fully working proof--‐ of--‐concept (of an already--‐existing industry product modified to use a message--‐oriented middleware and a specialized data warehouse system) is developed and presented, to conclude on the usefulness of message--‐oriented middleware when designing scalable data analytics architectures.<br>Demokratiseringen av Internet har tillåtit många fler att använda online--‐tjänster och deras fördelar. Trafiken till webbsidor har blivit enorm de senaste åren. Speciellt i och med de sociala nätverken. Mobil--‐applikationer, TV--‐apparater och andra enheter ansluter sig i allt större omfattning till Internet och tillhandahåller tjänster till slutanvändare: Video On--‐Demand, strömmande musik o.s.v. Applikationerna förlitar sig på kraftfull infrastruktur som kan hantera de förfrågningar enheterna gör och tillhandahålla statistik och mätetal om applikationernas användning. Dessa mätetal kan skapas genom att aggregera access--‐loggar (ex. HTTP--‐loggar). Dessa loggar är potentiellt väldigt stora. Så kallade Big Data--‐verktyg kan lösa problemet med att hantera denna stora mängd data. Typiskt är dessa verktyg klient--‐server--‐arkitekturer med en enskild, central databas som lagrar all data. Dessa databaser har i regel begränsningar när det gäller prestanda och kapacitet.    Duplicering av data kombinerat med en dedikerad och specialiserad databas är nyckeln till en effektiv lösning på detta problem. Frågan är hur man på ett effektivt, elegant och skalbart sätt fyller dessa databaser med information. Här kan meddelande--‐baserad mellanprogramvara vara en lösning. Det här examensarbetet syftar till att granska hur sådan mellanprogramvara kan integreras i en applikation som används i branschen idag och som behöver aggregera stora mängder loggar. Apache Kafka och RabbitMQ, som är två meddelande--‐baserade mellanprogramvaror, granskas och jämförs. Prestanda och effektivitet av lösningarna testas. En fullständig prototyp skapas. Den baseras på ett befintligt system och ändras för att använda meddelande--‐baserad mellanprogramvara och ett specialiserat Data Warehouse--‐system. Slutligen dras slutsatser om meddelande--‐ baserad mellanprogramvara är effektivt när man vill skapa ett skalbart system för aggregering av loggar.

The publish/subscribe paradigm is used to support a many-to-many model that allows an efficient dissemination of messages across a distributed system. Message Oriented Middleware (MOM) is a middleware that provides an asynchronous method of passing information between networked applications. MOMs can be based on a publish/subscribe model, which offers a robust paradigm for message delivery. This research is concerned with this specific type of MOM. Recently, systems using MOMs have been used to integrate enterprise systems over geographically distributed areas, like the ones used in financial services, telecommunication applications, transportation and health-care systems. However, the reliability of a MOM system must be verified and consideration given to reachability to all intended destinations typically with to guarantees of delivery. The research in this thesis provides an automated means of checking the (re)configuration of a publish/subscribe MOM system by building a model and using Linear-time Temporal Logic and Computation Tree Logic rules to verify certain constraints. The verification includes the checking of the reachability of different topics, the rules for regulating the working of the system, and checking the configuration and reconfiguration after a failure. The novelty of this work is the creation and the optimization of a symbolic model checker that abstracts the end-to-end network configuration and reconfiguration behaviour and using it to verify reachability and loop detection. In addition a GUI interface, a code generator and a sub-paths detector are implemented to make the system checking more user-friendly and efficient. The research then explores another aspect of reliability. The requirements of mission critical service delivery over a MOM infrastructure is considered and we propose a new way of supporting rapid recovery from failures using pre-calculated routing Abstract tables and coloured flows that can operate across multiple Autonomous System domains. The approach is critically appraised in relation to other published schemes.

Il Serverless Computing rappresenta un passo avanti nel campo dei servizi cloud in quanto permette di velocizzare lo sviluppo e il rilascio di applicazioni. Infatti, in questo modello di servizio, conosciuto anche con il nome di Function-as-a-Service (FaaS), gli sviluppatori non devono preoccuparsi del provisioning, dei server o delle configurazioni dell'infrastruttura, ma solo di creare funzioni che saranno eseguite in risposta a determinati eventi. Il modello ``pay-for-execution'', in cui i costi vengono addebitati solo per l'effettivo tempo di esecuzione delle funzioni, permette di ottenere alle aziende un Time-to-Market molto più rapido con un conseguente aumento della produttività. Di particolare interesse per questo studio risultano essere Trigger ed Invoker, ovvero i due componenti che in ambito Serverless si occupano di innescare e eseguire le funzioni. Infatti, l'obiettivo di questa tesi è stato progettare ed implementare un Message-Oriented-Middleware (MoM) che permetta di ottenere qualità della comunicazione tra Trigger e Invoker attraverso lo sviluppo di un meccanismo di classificazione e prioritizzazione del traffico. Nei risultati sperimentali, dove si è ipotizzato di avere due differenti classi di traffico con una più prioritaria dell'altra, si è verificata l'efficacia della soluzione proposta dove i dati collezionati hanno mostrato particolari benefici per la classe prioritaria in termini di latenze end-to-end e numero di pacchetti persi.

Il Serverless Computing, detto anche Function-as-a-Service (FaaS), rappresenta un’evoluzione dei servizi cloud in quanto consente agli sviluppatori di non preoccuparsi del provisioning, dei server o delle configurazioni dell’infrastruttura, ma solo di definire funzioni che saranno eseguite in risposta a determinati eventi detti Trigger. Il FaaS si basa principalmente sul modello “pay-for-execution” : i costi vengono addebitati solo per l’effettivo tempo di esecuzione delle funzioni. Questo garantisce costi effettivi minori e commisurati all’effettivo utilizzo delle funzioni, solitamente direttamente proporzionale al guadagno legato all’applicativo. L’obiettivo di questa tesi è stato riprogettare ed implementare un Message-Oriented- Middleware (MoM). Nella sua versione iniziale permetteva di ottenere qualità della comunicazione tra Trigger e Invoker attraverso lo sviluppo di un meccanismo di classificazione e prioritizzazione del traffico. La riprogettazione è stata mirata ad ottenere più dinamismo nel funzionamento del MoM e una redistribuzione del carico sui nodi esecutori. Questo in modo tale da non sovraccaricare nessuno nodo ridirezionando il traffico che precedentemente veniva scartato (per non generare sovraccarico) verso un broker sul cloud. Quest’ultimo esegue le Azure Functions collegate agli eventi ricevuti. Il ridirezionamento del carico è basato sulla priorità degli eventi dando cosi maggiore priorità di instradamento locale agli eventi più “importanti” per garantirne l’esecuzione più rapida.

Message brokers are the backbone of modern publish subscribe messaging systems. These brokers can degrade or fail for a variety of reasons. This research specifically looks at the detection, prediction and mitigation of bottlenecks in brokers. The message-oriented-middleware framework here uses either a cluster of brokers on a Local Area Network (LAN) or a federation of brokers on a Wide Area Network (WAN) to route messages, facilitate multicasting and ameliorate demand surges and geographically related faults. Sensors have been constructed to monitor brokers and controllers to run the bottleneck detection algorithms. An overlay manager controls broker and topic pairing. Each topic is assigned a primary and secondary broker. When a failure is predicted, the overlay manager routes messages from the failing broker by switching topics to its secondary broker(s). The application for bottleneck forecasting is to allow us to pre-empt a broker failure and hence reroute messages to other brokers to increase resilience and reliability. The key contributions of this research are an abstract model of message-oriented-middleware broker based on the Apache Qpid message broker coupled with the use of analytical autoregressive exogenous (ARX) models that describes the broker behaviour during bottleneck conditions. The Apache Qpid message broker is a message broker that implements the Advanced Message Queuing Protocol (AMQP) for publish-subscribe messaging. ARX models are autoregressive models where the output depends on the previous output as well as external stimuli. These components are integrated to produce a generalised technique for calibrating broker performance and detection of bottlenecks in the broker. This research show how models were initially constructed using a complete range of input data. As bottlenecks occur only when the broker is heavily loaded, input data during idle periods can cause corruption to the model fit. Models were constructed with segmented input data, with each segment covering the range of one peak period. The segmented input allows the modelling of the broker behaviour only when it is experiencing a bottleneck. The result of this is a much-improved fit of the predictive models. The work here is compared against previous work using Markov-chains for creating predictive models. The results of both approaches are compared and reported.