1,486 research outputs found

    Upon a Message-Oriented Trading API

    Get PDF
    In this paper, we introduce the premises for a trading system application-programming interface (API) based on a message-oriented middleware (MOM), and present the results of our research regarding the design and the implementation of a simulation-trading system employing a service-oriented architecture (SOA) and messaging. Our research has been conducted with the aim of creating a simulation-trading platform, within the academic environment, that will provide both the foundation for future experiments with trading systems architectures, components, APIs, and the framework for research on trading strategies, trading algorithm design, and equity markets analysis tools. Mathematics Subject Classification: 68M14 (distributed systems).Trading System API, Straight-Through Processing, Distributed Computing, Service-Oriented Architecture (SOA), Message-Oriented Middleware (MOM), Java Message Service (JMS), OpenMQ

    ASETS – An Academic Trading Simulation Platform

    Get PDF
    This paper is intended to present the results of our academic research upon a distributed computing environment dedicated to trading simulation. Our research has been conducted with the aim of creating a trading simulation platform, that would provide both the foundation for future experiments with trading systems architectures, components, APIs, and the framework for research on trading strategies, trading algorithms design, and equity markets analysis tools.Trading Systems, Simulation, Distributed Computing, Service-Oriented Architecture (SOA), Message-Oriented Middleware (MOM), Java Message Service (JMS)

    Extending message-oriented middleware

    Get PDF
    Different types of middleware exist to facilitate the integration of software running on heterogeneous computing platforms. Message Oriented Middleware (MOM), for instance, enables the interaction between heterogeneous applications by exchanging packets of structured data (messages) through communication channels. The core responsibility of a MOM is asynchronous delivery of messages from senders to receivers, as well as management of the corresponding message queues. However, realistic software applications need many more messaging functions, for instance functions to enable auditing, encryption, tracking and transformation of messages. Such functions should be clearly provided by the underlying MOM and not implemented and re-implemented by applications themselves. In this paper, we present an approach for extending the core functionality of a MOM. In particular, we investigate how such extensions can be configured and combined, to ensure correct delivery of messages.II Workshop de Ingeniería de Software y Bases de Datos (WISBD)Red de Universidades con Carreras en Informática (RedUNCI

    Extending message-oriented middleware

    Get PDF
    Different types of middleware exist to facilitate the integration of software running on heterogeneous computing platforms. Message Oriented Middleware (MOM), for instance, enables the interaction between heterogeneous applications by exchanging packets of structured data (messages) through communication channels. The core responsibility of a MOM is asynchronous delivery of messages from senders to receivers, as well as management of the corresponding message queues. However, realistic software applications need many more messaging functions, for instance functions to enable auditing, encryption, tracking and transformation of messages. Such functions should be clearly provided by the underlying MOM and not implemented and re-implemented by applications themselves. In this paper, we present an approach for extending the core functionality of a MOM. In particular, we investigate how such extensions can be configured and combined, to ensure correct delivery of messages.II Workshop de Ingeniería de Software y Bases de Datos (WISBD)Red de Universidades con Carreras en Informática (RedUNCI

    Message Bus Architectures - Simplicity in the Right Places

    Get PDF
    There will always be a new latest and greatest architecture for satellite ground systems. This paper discusses the use of a proven message-oriented middleware (MOM) architecture using publish/subscribe functions and the strengths it brings to these mission critical systems. An even newer approach gaining popularity is Service Oriented Architectures (SOAs). SOAs are generally considered more powerful than the MOM approach and address many mission-critical system challenges. A MOM vs SOA discussion can highlight capabilities supported or enabled by the underlying architecture and can identify benefits of MOMs and SOAs when applied to differing sets of mission requirements or evaluation criteria

    R-MOM: A Component-Based Framework for Interoperable and Adaptive Asynchronous Middleware Systems

    Get PDF
    International audienceSystems of systems (SoS) are composed of subsystems such as Distributed, Information Technology, Real-Time and Embedded systems. Among distributed systems, Message- Oriented Middleware (MOM) is used by SoS in order to share status information from system elements (component, service, etc.). Often several different MOM technologies are used in one SoS, then interoperability between these MOM is a requirement. In this paper, we present R-MOM, a component-based framework for interoperable and adaptive asynchronous middleware systems. R-MOM provides a reflective component architecture where one MOM functionality is embedded into one component which is modifiable at run-time. Loosely-coupling between reflective components permits to get a fined-personalization of MOM functionalities, such as protocol, encoding rule, Quality of Services (QoS) processing, data production/consumption, description, routing and filtering. Interoperability between integrated protocol functionalities is a consequence of architecture design. R-MOM interoperates with different kinds of MOM, from distributed message queues (Java Message Service, Advanced Message Queueing Protocol, 0MQ) to content-based publish/ subscribe systems (OMG's Data Distribution Service). This paper describes the architectural concepts of the R-MOM framework, discusses its implementation, and evaluates its interoperability capability.Les Systèmes de Systèmes (SoS) sont composés de sous-systèmes tels que les systèmes de type distribué, IT, temps-réel et embarqué. Parmi les systèmes distribués, les intergiciels orientés message (MOM) sont utilisés par les SoS dans le but de partager des informations de statut des éléments du systèmes (composant, service, etc...). Souvent, plusieurs technologies MOM sont utilisées dans un même SoS, et interopérabilité entre MOM devient nécessaire. Dans ce papier, nous présentons R-MOM, un canevas basé sur l'approche composant pour les intergiciels interopérables, adaptatifs et asynchrones. R-MOM offre une architecture à composants réflexif, où une fonctionalité d'un MOM est embarquée dans un composant qui est modifiable durant son exécution. Le couplage lâche entre les composants réflexif permet de jouir d'une personnalisation fine sur les fonctionalités MOM visées, comme le protocole, la règle d'encodage, le support des qualités de service, la production et consommation, la description, le routage et le filtrage des données. L'interopérabilité entre les fonctionnalités protocolaire intégrées est une conséquence du choix de conception de l'architecture. R-MOM est interopérable avec différent types de MOM, depuis les queues de message distribué (Java Message Service, Advanced Message Queueing Protocol, 0MQ) jusqu'aux systèmes de publication/souscription basées sur le contenu (Service de Distribution de Données de l'OMG). Ce papier papier décrit les concepts d'architecture du canevas R-MOM, discute son implémentation et évalue sa capacité d'interopérabilité

    Performance Modelling of Message-Oriented Middleware with Priority Queues

    Get PDF
    Message-Oriented Middleware (MOM) with priority queues reduces the latency of critical events. In general, MOM uses a FIFO queuing methodology. But, different application scenarios require certain critical events with higher priority to be served earlier over low-priority events, so that the subscriber of the event consumes the high-priority event with less delay. In the context of the Palladio Component Model (PCM), MOM-based systems have been modelled considering message queue length and latency as metrics for performance prediction and simulation. However, the approaches did not consider modelling MOM with priority queues and their impact on performance. We will first, discuss the existing approaches in PCM which support performance prediction for MOM-based systems and then propose how they can be extended to support performance predictions for MOM with priority queuing. We will then conclude which approach is best suited to extend by assessing their capabilities to predict performance metrics relevant for priority queuing, especially the delay of individual events at the subscriber end

    Message Oriented Middleware For Library’s Metadata Exchange

    Get PDF
    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

    Performance Evaluation and Comparison of Distributed Messaging Using Message Oriented Middleware

    Get PDF
    Message Oriented Middleware (MOM) is an enabling technology for modern event- driven applications that are typically based on publish/subscribe communication [Eugster03]. 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 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 [Brosey01]. 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, functional comparison and qualitative study from developers perspective
    corecore