Middleware’s message : the financial technics of codata

In this paper, I will argue for the relevance of certain distinctive features of messaging systems, namely those in which data (a) can be sent and received asynchronously, (b) can be sent to multiple simultaneous recipients and (c) is received as a “potentially infinite” flow of unpredictable events. I will describe the social technology of the stock ticker, a telegraphic device introduced at the New York Stock Exchange in the 1860s, with reference to early twentieth century philosophers of synchronous experience (Bergson), simultaneous sign interpretations (Mead and Peirce), and flows of discrete events (Bachelard). Then, I will show how the ticker’s data flows developed into the 1990s-era technologies of message queues and message brokers, which distinguished themselves through their asynchronous implementation of ticker-like message feeds sent between otherwise incompatible computers and terminals. These latter systems’ characteristic “publish/subscribe” communication pattern was one in which conceptually centralized (if logically distributed) flows of messages would be “published,” and for which “subscribers” would be spontaneously notified when events of interest occurred. This paradigm—common to the so-called “message-oriented middleware” systems of the late 1990s—would re-emerge in different asynchronous distributed system contexts over the following decades, from “push media” to Twitter to the Internet of Things

On MAS Scalability

In open dynamic multi-agent environments the number of agents can vary significantly within very short periods of time. Very few (if any) current multi-agent systems have, however, been designed to cope with large-scale distributed applications. Scalability requires increasing numbers of new agents and resources to have no noticeable effect on performance nor to increase administrative complexity. In this paper a number of implications for techniques and management are discussed. Current research on agent middleware is briefly described.

Management of e-technology in China

"e" technology is bringing about many challenges for companies, in particular for their managers. This concerns a vast range of business processes in many sectors of the economy and in nearly every country of the world. In rapidly industrializing China, companies and other organizations are actively finding their way by adapting, developing and exploiting new e-technologies. The paper's focus is the identification of the management issues in implementing e-technology in China. The paper reports on research into difficulties of establishing and operating e-business in China. In particular, it discusses management related to e-technology sharing and application. A brief review of literature is followed by the analysis of three recent case studies: an international IT services alliance, a financial services provider and an international manufacturing joint venture. All case companies are applying e-technology in China, but the role of e-technology differs in the three cases: adding a service line to the existing business processes; developing a new business process; and increasing efficiency and effectiveness in business processes. The conclusions present the emerging management issues: cooperation is a key asset in networking; the choice of business models plays an important role; adequate management attention for details such as a training program is require

A Reference Architecture for Electronic Business-to-Business Collaboration Setup and Enactment Systems

The question what a business-to-business (B2B) collaboration setup and enactment application-system should look like remains open. An important element of such collaboration constitutes the inter-organizational disclosure of business-process details so that the opposing parties may protect their business secrets. For that purpose, eSourcing [37] has been developed as a general businessprocess collaboration concept in the framework of the EU research project Cross- Work. The eSourcing characteristics are guiding for the design and evaluation of an eSourcing Reference Architecture (eSRA) that serves as a starting point for software developers of B2B-collaboration systems. In this paper we present the results of a scenario-based evaluation method conducted with the earlier specified eSourcing Architecture (eSA) that generates as results risks, sensitivity, and tradeoff points that must be paid attention to if eSA is implemented. Additionally, the evaluation method detects shortcomings of eSA in terms of integrated components that are required for electronic B2B-collaboration. The evaluation results are used for the specification of eSRA, which comprises all extensions for incorporating the results of the scenario-based evaluation, on three refinement levels.Peer reviewe

Définition des bases d'un guide sur l'architecture orientée service "En corrélation avec le guide SWEBOK"

Ce mémoire aborde un sujet du domaine de l'intégration d'applications d'entreprise qui est basé sur la notion de services. Le nom exact de ce domaine est architecture orientée service. L'architecture orientée-service est abordée par ce mémoire comme étant une nouvelle approche de l'intégration d'applications, qui est en soit un problème qui date de plusieurs années déjà. Des survols historiques et théoriques sont donnés afin de fournir l'état de l'art, en plus d'approfondir la matière avant d'entrer dans le coeur du sujet qui est, comme le titre l'indique, les bases d'un guide sur l'architecture orientée service basé sur le SWEBOK. Pour ce faire, le chapitre 4 est divisé en sections faisant directement référence au SWEBOK mais où l'on retrouve plutôt des contributions de l'auteur sur chacun des domaines abordés. Une suite d'objectifs est donnée en début de chapitre 4. Les contributions doivent répondre à un ou plusieurs de ces objectifs. Aux contributions, sont donc directement attribués des objectifs, ainsi qu'une courte explication qui décrit comment chacune des contributions répond aux divers objectifs. Une analyse sommaire des relations entre contributions et objectifs suit afin de déterminer si des hypothèses et généralisations découlent de cet exercice. La conclusion porte, d'une façon générale, sur l'ensemble du mémoire, mais aussi principalement sur le contenu du chapitre 4. ______________________________________________________________________________ MOTS-CLÉS DE L’AUTEUR : Architecture, Orientée-service, Architecture orientée-service, Intégration d'applications d'entreprise, Conception d'application, Services web, Conception de logiciel, Swebok, Génie logiciel, Soa