Relevant bibliographies by topics / Message Oriented Middleware (MOM)

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Book chapters
  4. Conference papers

Academic literature on the topic 'Message Oriented Middleware (MOM)'

Author: Grafiati
Published: 4 June 2025
Last updated: 6 July 2025

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Message Oriented Middleware (MOM).'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Message Oriented Middleware (MOM)"

1

Ni, Wayan Wisswani, and Wayan Kandi Wijaya I. "Message Oriented Middleware for Library's Metadata Exchange." TELKOMNIKA Telecommunication, Computing, Electronics and Control 16, no. 6 (2018): 2756–62. https://doi.org/10.12928/TELKOMNIKA.v16i6.9475.

Full text
Abstract:
Library is one of the important tools in the development of science to store various intellectual properties. Currently most libraries are managed by standalone systems and are not equipped with data exchange facilities with other libraries for sharing information. Sharing of information between libraries can be done with integration metadata owned library. In this research, the integration architecture of metadata exchange is done with Message Oriented Middleware (MOM) technology. This MOM redeems the collection metadata that matches the standard Dublin Core format. In this research, database structure, MOM structure and set of rules to perform data sharing process. With the proposed MOM architectural design is expected to search process information between libraries will become easier and cheaper.
APA, Harvard, Vancouver, ISO, and other styles
2

Wang, Chong Nan, Zong Tao Wang, and Gang Yuan. "Application Demand Analysis of Message-Oriented Middleware with Pub/Sub Model on TT&C Computer." Applied Mechanics and Materials 599-601 (August 2014): 1403–6. http://dx.doi.org/10.4028/www.scientific.net/amm.599-601.1403.

Full text
Abstract:
Message-Oriented Middleware(MOM) with Pub/Sub model is suitable for the information transmission of TT&C computer system for the advantage of fully information sharing, loosing coupling interconnects, many-to-many communication and flexible resources reorganization. This thesis introduces the basic concept of Pub/Sub model, analysis the characteristics of TT&C application.Priority it put forward the key technologies: Message model, Matching algorithm, Routing protocol and Redundancy virtualization strategy for establishing MOM with Pub/Sub model on TT&C compter system.
APA, Harvard, Vancouver, ISO, and other styles
3

Zhong, Zhen Kui. "Design and Implementation of Software Architecture of Manufacturing Execution System Based on Middleware Technology." Applied Mechanics and Materials 443 (October 2013): 526–30. http://dx.doi.org/10.4028/www.scientific.net/amm.443.526.

Full text
Abstract:
Manufacturing execution system is the software system that is used most widely for manufacturing enterprises to realize informatization. In order to solve the problem of distributed heterogeneous environment, MES introduces the concept of middleware. It is in the middle of the operation system software and MES and above the operation system, network and database and below the MES. It helps the software developers to flexibly and high effectively develop and integrate complicated all modules in MES as well as complicated application and communications in enterprises. This design adopts two kinds of middleware. The first kind is Message Oriented Middleware (MOM). Message Oriented Middleware hides the details of interaction between all kinds of machine equipment and MES data under the unified data specifications. It makes in-time, high-efficient and stable data transmission as well as easily copes with the complicated production environment. The second kind is common transaction processing middleware. It enclosures the details of transaction processing and offers a stable transaction platform, enabling the developers to pay attention to the development of business logic. It ensures the development qualities and the development costs.
APA, Harvard, Vancouver, ISO, and other styles
4

P. Ahuja, Sanjay, and Naveen Mupparaju. "Performance Evaluation and Comparison of Distributed Messaging Using Message Oriented Middleware." Computer and Information Science 7, no. 4 (2014): 9. http://dx.doi.org/10.5539/cis.v7n4p9.

Full text
Abstract:
Message Oriented Middleware (MOM) is an enabling technology for modern event-driven applications that are typically based on publish/subscribe communication (Eugster, 2003). Enterprises typically contain hundreds of applications operating in environments with diverse databases and operating systems. Integration of these applications is required to coordinate the business process. Unfortunately, this is no easy task. Enterprise Integration, according to the authors in (Brosey et al, 2001), "aims to connect and combines people, processes, systems, and technologies to ensure that the right people and the right processes have the right information and the right resources at the right time”. Communication between different applications can be achieved by using synchronous and asynchronous communication tools. In synchronous communication, both parties involved must be online (for example, a telephone call), whereas in asynchronous communication, only one member needs to be online (email). Middleware is software that helps two applications communicate with one another. Remote Procedure Calls (RPC) and Object Request Brokers (ORB) are two types of synchronous middleware—when they send a request they must wait for an immediate reply. This can decrease an application’s performance when there is no need for synchronous communication. Even though asynchronous distributed messaging using message oriented middleware is widely used in industry, there is not enough work done in evaluating the performance of various open source Message oriented middleware. The objective of this work was to benchmark and evaluate three different open source MOM’s performance in publish/subscribe and point-to-point domains, and provide a functional comparison and qualitative study from developers perspective.
APA, Harvard, Vancouver, ISO, and other styles
5

Najhan, Muhamad Ibrahim, and Fadzil Hassan Mohd. "A Comprehensive Comparative Study of MOM for Adaptive Interoperability Communications in Service Oriented Architecture." International Journal of Trend in Scientific Research and Development 3, no. 3 (2019): 23–30. https://doi.org/10.31142/ijtsrd21595.

Full text
Abstract:
Numerous software platforms have developed to support several application systems with a variety of techniques and solution. The communications between those platforms are required to ensure tasks distributed across different application systems. The collaboration between distinct application systems to grow, in tandem with the growth of SOA in which the resources of each SOA application might be developed and implemented using different standard and specification. Within this context, interoperability communications is significant to consolidate the optimization of these resources. Additionally, identifying the requirements attribute related to interoperability communications are the first step required in the development of interoperability communications. MOM can be considered as a tool for enabling the communications between distributed applications where the transaction or event notifications are delivered between distributed applications through the message. MOM provides a program to program connection by message passing. Most of the MOM environments are implemented using queued message store and forward capability, which is Message Queuing Middleware MQM . In addition, an adaptive interoperability communications can be defined as the computer system that enables self coordination to distribute computing resources and an adaptive to the new environment while hiding fundamental complexity from the operators and users. The intelligent system has the capability of self management to overcome the rapidly growing complexity in computing systems. The system makes decisions on its own by using the rules that have been identified. Intelligent system also provides an adaptive and dynamic environment for the process of communication. The framework of an intelligent system, fundamentally consists of intelligent elements. Each element performs a fixed function and interacting with other elements in a very dynamic environment. Najhan Muhamad Ibrahim | Mohd Fadzil Hassan "A Comprehensive Comparative Study of MOM for Adaptive Interoperability Communications in Service Oriented Architecture" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Volume-3 | Issue-3 , April 2019, URL: https://www.ijtsrd.com/papers/ijtsrd21595.pdf
APA, Harvard, Vancouver, ISO, and other styles
6

Flores-González, Martín, Ignacio Trejos-Zelaya, and César Garita. "Modelado exploratorio del rendimiento y la confiabilidad de software sobre middleware orientado a mensajes." Revista Facultad de Ingeniería 29, no. 54 (2020): e11764. http://dx.doi.org/10.19053/01211129.v29.n54.2020.11764.

Full text
Abstract:
El rendimiento es un importante atributo de calidad de un sistema de software. La Ingeniería de rendimiento del software comprende las actividades de análisis, diseño, construcción, medición y validación, que atienden los requerimientos de rendimiento a lo largo del proceso de desarrollo de software. En los sistemas de software que utilizan comunicación basada en mensajes, el rendimiento depende en gran medida del middleware orientado a mensajes (Message-Oriented Middleware – MOM). Los arquitectos de software necesitan considerar su organización, configuración y uso para predecir el comportamiento de un sistema que use tal plataforma. La inclusión de un MOM en una arquitectura de software requiere conocer el impacto de la mensajería y de la infraestructura utilizada. Omitir la influencia del MOM llevaría a la generación de predicciones erróneas. En este artículo se explora tal influencia, mediante el modelado y la simulación basados en componentes, utilizando el enfoque Palladio Component Model – PCM. En particular, una aplicación modelada en PCM fue adaptada para incluir comunicación basada en mensajes. Las simulaciones sobre el modelo, mediciones sistemáticas y pruebas de carga sobre la aplicación permitieron determinar cómo cambios introducidos en el modelo influyen en las predicciones del comportamiento de la aplicación en cuanto a rendimiento y confiabilidad. Fue posible identificar un cuello de botella que impacta negativamente el rendimiento y la confiabilidad del sistema original. La introducción de MOM mejoró la confiabilidad del sistema, a expensas del rendimiento. La simulación del rendimiento basado en componentes reveló diferencias significativas respecto de los experimentos basados en pruebas de carga y mediciones.
APA, Harvard, Vancouver, ISO, and other styles
7

Jiang, Peng, John Bigham, Eliane Bodanese, and Emmanuel Claudel. "Publish/subscribe delay-tolerant message-oriented middleware for resilient communication." IEEE Communications Magazine 49, no. 9 (2011): 124–30. http://dx.doi.org/10.1109/mcom.2011.6011743.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Galinec, Darko, and Ljerka Luić. "Asynchronous Message-Passing and Inter-Application Communication Software for Process Improvement in Complex Systems." International Journal of Knowledge-Based Organizations 4, no. 4 (2014): 36–50. http://dx.doi.org/10.4018/ijkbo.2014100103.

Full text
Abstract:
Complex systems nowadays are usually supported by previously developed or inherited application systems, which have been developed on the basis of business functions standard model. Such application systems cover particular business fields, however, since they have been developed in an independent and uncoordinated way, there are modest possibilities of interacted automated data exchange because of heterogeneous data. Because of increasing data exchange needs, enforcement of development and upgrade of programmatic procedures is required. In this connection it is necessary to find ways and means to integrate all existing application systems in given circumstances and render possible exchange and usage of all needed data in a reliable and consistent way. The problem can be solved in different ways. Asynchronous message-passing and inter-application communication software appliance imply commencement of automated data exchange among existing organizations application systems, providing for full scale control and management of mutually exchangeable data, internally as well as externally. In this connection contributing model of the running application systems integrated by means of Message-Oriented Middleware (MOM) of the complex system has been created.
APA, Harvard, Vancouver, ISO, and other styles
9

Risimic, Dejan. "An integration strategy for large enterprises." Yugoslav Journal of Operations Research 17, no. 2 (2007): 209–22. http://dx.doi.org/10.2298/yjor0702209r.

Full text
Abstract:
Integration is the process of enabling a communication between disparate software components. Integration has been the burning issue for large enterprises in the last twenty years, due to the fact that 70% of the development and deployment budget is spent on integrating complex and heterogeneous back-end and front-end IT systems. The need to integrate existing applications is to support newer, faster, more accurate business processes and to provide meaningful, consistent management information. Historically, integration started with the introduction of point-to-point approaches evolving into simpler hub-and spoke topologies. These topologies were combined with custom remote procedure calls, distributed object technologies and message-oriented middleware (MOM), continued with enterprise application integration (EAI) and used an application server as a primary vehicle for integration. The current phase of the evolution is service-oriented architecture (SOA) combined with an enterprise service bus (ESB). Technical aspects of the comparison between the aforementioned technologies are analyzed and presented. The result of the study is the recommended integration strategy for large enterprises.
APA, Harvard, Vancouver, ISO, and other styles
10

Chen, Guangxuan, Liping Ding, Guangxiao Chen, and Panke Qin. "Reliable Security Strategy for Message-Oriented Middleware." International Journal of Digital Crime and Forensics 10, no. 1 (2018): 12–23. http://dx.doi.org/10.4018/ijdcf.2018010102.

Full text
Abstract:
This article explores a method to solve the security problems such as limited single-server processing power and single point of failure, and so on, a newly designed and developed Message-Oriented Middleware that supports clustering features. By improving the traditional reverse proxy cluster system, Message-Oriented Middleware has been made more applicable to message transmission services. A method of dynamic load balancing and load transfer was based on a variety of factors that was also designed according to the characteristics of a message service system. The method can solve problems like system instability and performance bottle-neck in Message-Oriented Middleware effectively and can increase the throughput of the system obviously.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Message Oriented Middleware (MOM)"

1

Eriksson, John. "Comparing message-oriented middleware for financial assets trading." Thesis, KTH, Data- och elektroteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-188194.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
2

Simonetti, Giacomo. "Message-oriented Middleware per qualità del servizio in funzioni Serveless." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2022.

Find full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
3

Campagna, Leonardo. "Message-Oriented-Middleware per Funzioni QoS-enabled in Contesto Serverless." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2021. http://amslaurea.unibo.it/24188/.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
4

Machado, Caciano dos Santos. "MPI sobre MOM para suportar log de mensagens pessimista remoto." reponame:Biblioteca Digital de Teses e Dissertações da UFRGS, 2010. http://hdl.handle.net/10183/27656.

Full text
Abstract:
O aumento crescente no número de processadores das arquiteturas paralelas que estão no topo dos rankings de desempenho, apesar de permitir uma maior capacidade de processamento, também traz consigo um aumento na taxa de falhas diretamente proporcional ao número de processadores. Atualmente, as técnicas de tolerância a falhas com recuperação retroativa são as mais empregadas em aplicações MPI, principalmente a técnica de checkpoint coordenado. No entanto, previsões afirmam que essa última técnica será inadequada para as arquiteturas emergentes. Em contrapartida, as técnicas de log de mensagens possuem características que as tornam mais apropriadas no novo cenário que se estabelece. O presente trabalho consiste em uma proposta de log de mensagens pessimista remoto com checkpoint não-coordenado e a avaliação de desempenho da comunicação MPI sobre Publish/Subscriber no qual se baseia o log de mensagens. O trabalho compreende: um estudo das técnicas de tolerância a falhas mais empregadas em ambientes de alto desempenho e a motivação para a escolha dessa variante de log de mensagens; a proposta de log de mensagens; uma implementação de comunicação Open MPI sobre OpenAMQ e sua respectiva avaliação de desempenho com comunicação tradicional TCP/IP e com o log de mensagens pessimista local da distribuição do Open MPI. Os benchmarks utilizados foram o NetPIPE, o NAS Parallel Benchmarks e a aplicação Virginia Hydrodynamics (VH-1).<br>The growing number of processors in parallel architectures at the top of performance rankings allows a higher processing capacity. However, it also brings an increase in the fault rate which is directly proportional to the number of processors. Nowadays, coordinated checkpoint is the most widely used rollback technique for system recovery in the occurrence of faults in MPI applications. Nevertheless, projections point that this technique will be inappropriate for the emerging architectures. On the other hand, message logging seems to be more appropriate to this new scenario. This work consists in a proposal of pessimistic message logging (remote based) with non-coordinated checkpoint and the performance evaluation of an MPI communication mechanism that works over Publish/Subscriber channels in which the proposed message logging is based. The work is organized as following: an study of fault tolerant techniques used in HPC and the motivation for choosing this variant of message logging; a message logging proposal; an implementation of Open MPI communication over OpenAMQ; performance evaluation and comparision with the tradicional TCP/IP communication and a pessimistic message logging (sender based) from Open MPI distribution. The benchmark set is composed of NetPIPE, NAS Parallel Benchmarks and Virginia Hydrodynamics (VH-1).
APA, Harvard, Vancouver, ISO, and other styles
5

Bezerra, Yuri Morais. "Multi-MOM : um middleware multi-paradigma, extensível e orientado a mensagens para computação móvel." Universidade Federal da Paraí­ba, 2010. http://tede.biblioteca.ufpb.br:8080/handle/tede/6144.

Full text
Abstract:
Made available in DSpace on 2015-05-14T12:36:56Z (GMT). No. of bitstreams: 1 arquivototal.pdf: 2305795 bytes, checksum: 0e634264f2c488a816479aec2da0cc18 (MD5) Previous issue date: 2010-08-16<br>Coordenação de Aperfeiçoamento de Pessoal de Nível Superior<br>Advances in wireless communication technologies and miniatuziation of mobile devices are leading to great opportunities in the development of applications to explore this new computing frontier. However, the development of applications for such scenarios introduces new challenges, as mobile applications run on resouce-scarce devices and communicate with each other by means of wireless networks, which are characterized by intermittent connections. In order to avoid having to deal with such issues in an ad hoc fashion for every application, middleware platforms are adopted, concealing difficulties raised by mobility from application engineers as much as possible. Due to the asynchronous and loosely coupled communication style, Message-oriented Middleware (MOM) platforms have been commonly adopted for supporting the development of networked mobile applications. However, one of the most significant limitations of current MOM for mobile platforms is that they typically support a single, predefined communication paradigm (e.g., publish/subscribe). Such a restriction limits the scope of applications supported by the middleware. In order to mitigate such a limitation, this paper presents a middleware for mobile devices capable of supporting an extensible set of message-oriented communication paradigms (e.g. tuple spaces, message queue, publish/subscribe). Supported by an integrated architecture, which has been conceived based on a Software Product Line (SPL) approach, the middleware encapsulates common features that deal with mobility issues and provides them as shared, reusable components. Evaluation results show that the overhead introduced by such a multi-paradigm approach is minimal, both in memory footprint and runtime performance. Additionally, an application scenario illustrates how mobile applications may benefit from such an approach.<br>Os avanços nas tecnologias de comunicação sem fio e a miniaturização dos dispositivos móveis de alta capacidade estão trazendo grandes oportunidades para o desenvolvimento de aplicações que explorem essas novas fronteiras da computação. Entretanto, o desenvolvimento de aplicações nestes cenários traz novos desafios, pois estas operam em dispositivos de recursos limitados e comunicam-se através de redes sem fio, caracterizadas por conexões intermitentes. Para evitar que esses desafios tenham que ser resolvidos de forma improvisada para cada aplicação, plataformas de middleware são utilizadas, liberando os desenvolvedores de aplicações das dificuldades trazidas pela mobilidade. Devido ao seu estilo de comunicação assíncrono e fracamente acoplado, plataformas de Middleware orientado a Mensagens (MOM) têm sido comumente adotadas nestes casos. Entretanto, uma das limitações mais significantes das atuais plataformas de MOM é que elas geralmente dão suporte a um paradigma de comunicação único e predefinido (ex.: publish/subscribe). Essa restrição limita o escopo de aplicações que o middleware pode dar suporte. Para lidar com essa limitação, esta dissertação propõe um middleware para dispositivos móveis capaz de dar suporte a um conjunto extensível de paradigmas de comunicação baseados em mensagens (ex.: espaço de tuplas, filas de mensagens, publish/subscribe). Através de uma arquitetura integrada, a qual foi concebida baseada numa abordagem de Linha de Produto de Software (LPS), o middleware encapsula funcionalidades comuns para lidar com os desafios trazidos pela mobilidade, provendo componentes reusáveis e compartilhados entre os diversos paradigmas. Os resultados da avaliação mostram que o overhead introduzido pela abordagem multi-paradigma é mínimo, tanto em termos de espaço ocupado em memória, quanto em desempenho em tempo de execução. Por fim, com o intuito de ilustrar como aplicações móveis podem se beneficiar dessa abordagem, um cenário de aplicação é descrito.
APA, Harvard, Vancouver, ISO, and other styles
6

Laumay, Philippe. "Configuration et déploiement d'intergiciel asynchrone sur système hétérogène à grande échelle." Phd thesis, Grenoble INPG, 2004. http://tel.archives-ouvertes.fr/tel-00005409.

Full text
Abstract:
L émergence des environnements omniprésents pose un nouveau défi aux systèmes informatiques. Les intergiciels asynchrones (Message-Oriented Middleware, MOM) sont reconnus comme étant la solution la plus apte à répondre aux besoins de passage à grande échelle, de flexibilité, et d' hétérogénéité des nouvelles applications distribuées. Mais l'implémentation des intergiciels asynchrones actuels reste souvent figée quels que soient les sites d'exécution et l'application (les applications) l'utilisant et sont peu voire pas configurables. Cette thèse s'intéresse à la configuration et au déploiement des intergiciels asynchrones sur système hétérogène à grande échelle. Elle vise la définition d'un modèle d'intergiciel asynchrone configurable permettant une configuration statique et à l'exécution. Elle a pour objectif d'associer les nombreux travaux dans le domaine de l'asynchrone qui ont mené à la définition des modèles de communication asynchrones et les réflexions menées dans les intergiciels synchrones autour des nouveaux besoins de configuration et d'adaptabilité. La synthèse de tous nos travaux nous a mené à la création de DREAM (Dynamic REflective Asynchronous Middleware), un intergiciel asynchrone adaptable. Les mécanismes de contrôles fournis par Dream ainsi que son architecture permettent de réaliser une configuration en se basant sur les besoins applicatifs et les contraintes imposées par le système. Nous validons notre prototype par l'implémentation d'un service à évènement à base d'agents dans lequel nous utilisons les capacités d'adaptation de DREAM pour ajouter de nouvelles fonctionnalités.
APA, Harvard, Vancouver, ISO, and other styles
7

Kuhlman, Christopher James. "A Message Oriented Middleware Library." Also available to VCU users online at:, 2007. http://hdl.handle.net/10156/1207.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Desjeans, Gauthier Jean-François. "A message oriented middleware for mobility." Thesis, McGill University, 2011. http://digitool.Library.McGill.CA:80/R/?func=dbin-jump-full&object_id=97182.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
9

Nilsson, Erik, and Victor Pregén. "Performance evaluation of message-oriented middleware." Thesis, KTH, Hälsoinformatik och logistik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-283539.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
10

Steyn, Manie C. "APIS : a real-time message-oriented middleware." Master's thesis, University of Cape Town, 2001. http://hdl.handle.net/11427/8752.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Message Oriented Middleware (MOM)"

1

Curry, Edward. "Message-Oriented Middleware." In Middleware for Communications. John Wiley & Sons, Ltd, 2005. http://dx.doi.org/10.1002/0470862084.ch1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Etzkorn, Letha Hughes. "Introduction to Message-Oriented Middleware." In Introduction to Middleware. Chapman and Hall/CRC, 2017. http://dx.doi.org/10.4324/9781315118673-21.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Liu, Yang, Liang-Jie Zhang, and Chunxiao Xing. "Review for Message-Oriented Middleware." In Lecture Notes in Computer Science. Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-59615-6_12.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Laumay, Philippe, Eric Bruneton, Noël De Palma, and Sacha Krakowiak. "Preserving Causality in a Scalable Message-Oriented Middleware." In Middleware 2001. Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/3-540-45518-3_17.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Yang, Hao, Minkyong Kim, Kyriakos Karenos, Fan Ye, and Hui Lei. "Message-Oriented Middleware with QoS Awareness." In Service-Oriented Computing – ICSOC 2007. Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-10383-4_22.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Goel, Sushant, Hema Sharda, and David Taniar. "Asynchronous Messaging Using Message-Oriented-Middleware." In Intelligent Data Engineering and Automated Learning. Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/978-3-540-45080-1_162.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Banavar, Guruduth, Tushar Chandra, Robert Strom, and Daniel Sturman. "A Case for Message Oriented Middleware." In Lecture Notes in Computer Science. Springer Berlin Heidelberg, 1999. http://dx.doi.org/10.1007/3-540-48169-9_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Goel, Sushant, Hema Sharda, and David Taniar. "Message-Oriented-Middleware in a Distributed Environment." In Innovative Internet Community Systems. Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/978-3-540-39884-4_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Yuan, Pingpeng, and Hai Jin. "A Composite-Event-Based Message-Oriented Middleware." In Grid and Cooperative Computing. Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-24679-4_122.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Taton, Christophe, Noël De Palma, Daniel Hagimont, Sara Bouchenak, and Jérémy Philippe. "Self-optimization of Clustered Message-Oriented Middleware." In On the Move to Meaningful Internet Systems 2007: CoopIS, DOA, ODBASE, GADA, and IS. Springer Berlin Heidelberg, 2007. http://dx.doi.org/10.1007/978-3-540-76848-7_38.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Message Oriented Middleware (MOM)"

1

Rosa, Nelson S., and David J. M. Cavalcanti. "Exploiting Controllers to Adapt Message-Oriented Middleware." In 2024 IEEE International Conference on Autonomic Computing and Self-Organizing Systems (ACSOS). IEEE, 2024. https://doi.org/10.1109/acsos61780.2024.00027.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Zhou, Pu, Zeren Yu, Xiaoli Chai, and Yan Zuo. "RapidIO-Based Message-Oriented Middleware Design for FPGA Interconnection." In 2024 4th International Conference on Electronic Information Engineering and Computer Communication (EIECC). IEEE, 2024. https://doi.org/10.1109/eiecc64539.2024.10929219.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Ratmumad, Seoulcha, and Wannarat Suntiamorntut. "Improvement of Message-Oriented Middleware (MOM) for the Surveillance Platform." In 2023 20th International Joint Conference on Computer Science and Software Engineering (JCSSE). IEEE, 2023. http://dx.doi.org/10.1109/jcsse58229.2023.10202030.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Ding, Hong, Chuang Zhang, Xiaojun Chen, Jinqiao Shi, and Wenan Wang. "Cloud-MOM: A Content-Based Real-Time Message-Oriented Middleware for Cloud." In 2018 IEEE 20th International Conference on High Performance Computing and Communications; IEEE 16th International Conference on Smart City; IEEE 4th International Conference on Data Science and Systems (HPCC/SmartCity/DSS). IEEE, 2018. http://dx.doi.org/10.1109/hpcc/smartcity/dss.2018.00128.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Luzuriaga, Jorge E., Miguel Perez, Pablo Boronat, Juan Carlos Cano, Carlos Calafate, and Pietro Manzoni. "Impact of mobility on Message Oriented Middleware (MOM) protocols for collaboration in transportation." In 2015 IEEE 19th International Conference on Computer Supported Cooperative Work in Design (CSCWD). IEEE, 2015. http://dx.doi.org/10.1109/cscwd.2015.7230943.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Ibrahim, Najhan M., and Mohd Fadzil Hassan. "Agent-based Message Oriented Middleware(MOM) for cross-platform communication in SOA systems." In 2012 International Conference on Computer & Information Science (ICCIS). IEEE, 2012. http://dx.doi.org/10.1109/iccisci.2012.6297529.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Chen, Qiyang, James Yao, and Rubin Xing. "Middleware Components for E-commerce Infrastructure: An Analytical Review." In InSITE 2006: Informing Science + IT Education Conference. Informing Science Institute, 2006. http://dx.doi.org/10.28945/2951.

Full text
Abstract:
Embracing inapt infrastructure technology is a major threat in developing extensive and efficient Web-based systems. The architectural strength of all business models demands an effective integration of various technological components. And middleware, the center of all applications, becomes the driver—everything works if middleware does. In the recent times, the client/server environment has experienced sweeping transformation and led to the notion of the “Object Web”. Web browser is viewed as a universal client that is capable of shifting flawlessly and effortlessly between various applications over the Net. This paper presents an overview of middleware and the facilitating technologies and point toward the latest developments, taking into account the functional potential of the on-market middleware solutions as well as their technical strengths and weaknesses. The paper classifies and describes various types of middleware technologies such as database middleware, Remote Procedure Call (RPC), application server middleware, message-oriented middleware (MOM), Object Request Broker (ORB), transaction-processing monitors, and Web middleware etc., with on-market technologies.
APA, Harvard, Vancouver, ISO, and other styles
8

Rausch, Thomas. "Message-oriented middleware for edge computing applications." In Middleware '17: 18th International Middleware Conference. ACM, 2017. http://dx.doi.org/10.1145/3152688.3152690.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Sachs, Kai, Samuel Kounev, Stefan Appel, and Alejandro Buchmann. "Benchmarking of message-oriented middleware." In the Third ACM International Conference. ACM Press, 2009. http://dx.doi.org/10.1145/1619258.1619313.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Yongguo, Jiang, Liu Qiang, Qin Changshuai, Su Jian, and Liu Qianqian. "Message-oriented Middleware: A Review." In 2019 5th International Conference on Big Data Computing and Communications (BIGCOM). IEEE, 2019. http://dx.doi.org/10.1109/bigcom.2019.00023.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Message Oriented Middleware (MOM)' for particular source types:
Journal articles Dissertations / Theses
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography