DOCSLIB.ORG

Cloud Message Queue

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Cloud Message Queue Cloud Message Queue © 2020 General Electric Company Contents Chapter 1: Overview 1 Overview of Cloud Message Queue 2 Chapter 2: Architecture 3 Cloud Message Queue Architecture 4 Chapter 3: Getting Started with Cloud Message Queue 5 Create Cloud Message Queue Service Instance 6 Update Cloud Message Queue Service Instance 7 Bind the Cloud Foundry Application to the Cloud Message Queue Service Instance 8 Unbind the Cloud Foundry Application from the Cloud Message Queue Service Instance 10 Delete Cloud Message Queue Service Instance 10 Chapter 4: Accessing Cloud Message Queue Web Console 11 About Accessing Cloud Message Queue Web Console 12 Access the Web Console for a Single-Instance Broker 12 Access the Web Console for an Active or Standby Broker 13 Chapter 5: Using Cloud Message Queue Service 14 About Using Cloud Message Queue Service 15 Connect to ActiveMQ Broker using Java Message Service (JMS) 15 Connect to ActiveMQ Broker with Golang 19 About Connecting the ActiveMQ Broker with Ruby 21 Chapter 6: Migrating to Cloud Message Queue 27 About Migrating to Cloud Message Queue 28 Migrate from Predix Message Queue to Cloud Message Queue 28 Create Cloud Message Queue Service Instance 28 Migrate from RabbitMQ to ActiveMQ 29 ii Cloud Message Queue Chapter 7: Security 30 About Cloud Message Queue Security 31 Chapter 8: Backup 32 About Backing up Messages 33 Chapter 9: Retrieving Broker and Destination Metrics 34 About Retrieving Metrics for the Message Queue Broker and Destination Applications 35 Retrieve Metrics for Broker and Destination Applications 35 Chapter 10: Reference 38 Performance Benchmarking 39 Chapter 11: Release Notes 41 Third Quarter of 2020 42 iii Copyright GE Digital © 2020 General Electric Company. GE, the GE Monogram, and Predix are either registered trademarks or trademarks of General Electric Company. All other trademarks are the property of their respective owners. This document may contain Confidential/Proprietary information of General Electric Company and/or its suppliers or vendors. Distribution or reproduction is prohibited without permission. THIS DOCUMENT AND ITS CONTENTS ARE PROVIDED "AS IS," WITH NO REPRESENTATION OR WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF DESIGN, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. ALL OTHER LIABILITY ARISING FROM RELIANCE UPON ANY INFORMATION CONTAINED HEREIN IS EXPRESSLY DISCLAIMED. Access to and use of the software described in this document is conditioned on acceptance of the End User License Agreement and compliance with its terms. iv © 2020 General Electric Company Chapter 1 Overview Topics: • Overview of Cloud Message Queue © 2020 General Electric Company 1 Overview of Cloud Message Queue Cloud Message Queue is a service that provides the ability to exchange messages between different applications, components, and devices in a highly durable and reliable manner. It is built upon Apache ActiveMQ and is backed by Amazon MQ, which is a managed message broker service for Apache ActiveMQ. Cloud Message Queue utilizes the features of Amazon MQ to ensure its high availability and message durability. Cloud Message Queue is designed to replace Predix Message Queue which is built upon RabbitMQ. The Predix Message Queue service will no longer be available in future and therefore, GE Digital recommends you migrate to the Cloud Message Queue service before the Predix Message Queue service is deprecated. Some of the salient features of Cloud Message Queue are as follows: • It supports a wide range of clients, including Java Message Service (JMS) 1.1 and .NET Message Service (NMS). • It is compatible with a range of programming languages, including Node.js, Go, Python, Ruby, and C++. • It supports various wire-level protocols, such as Advanced Message Queuing Protocol (AMQP), Simple (or Streaming) Text Oriented Messaging Protocol (STOMP), OpenWire, WebSocket, and MQ Telemetry Transport (MQTT). • It provides all the standard JMS features, including point-to-point messaging, publish/subscribe messaging, request/reply, persistent and non-persistent modes, JMS transactions, and distributed (XA) transactions. • It provides the flexibility of sending messages through both queues and topics, using a single-broker. In point-to-point messaging, the ActiveMQ broker balances the load by routing each message from the queue to one of the available consumers in a sequential manner. In pub/sub messaging, the broker delivers each message to every consumer that has subscribed to the topic. • In addition to basic queues and topics, it supports other complex patterns, such as composite and virtual destinations. Composite destinations are used for producers to send the same message to multiple destinations. Whereas, virtual destinations are used for publishers to broadcast messages through a topic to a pool of receivers subscribing through queues. Note: Currently, Cloud Message Queue supports the following versions of ActiveMQ: • 5.15.0 • 5.15.6 • 5.15.8 • 5.15.9 • 5.15.10 2 © 2020 General Electric Company Chapter 2 Architecture Topics: • Cloud Message Queue Architecture © 2020 General Electric Company 3 Cloud Message Queue Architecture The following architecture diagram provides a high-level information on how a user application interacts with an Amazon MQ (ActiveMQ) instance using the Cloud Message Queue service. The ActiveMQ message broker sends the messages from one application to another. The application that creates a message is called the producer and the application that receives and processes that message is called the consumer of the message. The message broker routes each message through one of the following destinations: • Queue: Used in a point-to-point messaging domain where the message awaits its delivery to a single consumer. • Topic: Used in a publish/subscribe or pub/sub messaging domain where the message is delivered to multiple consumers that have subscribed to the topic. 4 © 2020 General Electric Company Chapter 3 Getting Started with Cloud Message Queue Topics: • Create Cloud Message Queue Service Instance • Update Cloud Message Queue Service Instance • Bind the Cloud Foundry Application to the Cloud Message Queue Service Instance • Unbind the Cloud Foundry Application from the Cloud Message Queue Service Instance • Delete Cloud Message Queue Service Instance © 2020 General Electric Company 5 Create Cloud Message Queue Service Instance About This Task You can create the Cloud Message Queue service instance with default or customized Amazon MQ configurations. For more information on Amazon MQ configurations, and their elements and attributes, refer to Amazon MQ documentation. Procedure 1. In the Cloud Foundry (CF) Command Line Interface, run the following command to access the list of Cloud Message Queue plans that are available in the CF marketplace for subscription: cf m -s cloud-message-queue 2. Depending on whether you want to use the default or customized Amazon MQ configurations, perform one of the following tasks: • Create the instance with the default configurations. • Create the instance with customized configurations. Create Service Instance with Default Configurations Procedure 1. Access KBA 000036364, and then download the configuration file corresponding to the version of your ActiveMQ broker specified in the following table: ActiveMQ Version Configuration File 5.15.0 defaultConfigForEngineVersion5-15-0.zip 5.15.6 defaultConfigForEngineVersion5-15-6.zip 5.15.8 defaultConfigForEngineVersion5-15-8.zip 5.15.9 defaultConfigForEngineVersion5-15-9.zip 5.15.10 defaultConfigForEngineVersion5-15-10.zip Note: By default, the KahaDB persistence adapter is enabled in all the configurations. If you want to access the broker or destination metrics within your application, you must enable <statisticsBrokerPlugin/>. 2. Extract the content of the downloaded ZIP file. 3. In the Cloud Foundry (CF) Command Line Interface, run the following command to create the service instance: cf create-service cloud-message-queue <subscription_plan_name> <service_instance_name> Note: • The angle brackets (< >) in the command indicate placeholder text. You must replace the placeholder text with an appropriate value before running the command. • By default, Cloud Message Queue supports ActiveMQ V5.15.9 and the default configuration of ActiveMQ V5.15.9 will be used to create the instance. 6 © 2020 General Electric Company Create Service Instance with Customized Configurations About This Task You can create the Cloud Message Queue service instance with customized values of the following parameters: • ActiveMQ configuration XML • ActiveMQ engine version • Description string Important: The angle brackets (< >) in this topic indicate placeholder text. If such placeholder text is part of a command, replace the placeholder text with an appropriate value before running the command. Procedure 1. Create an XML file with the customized settings of your ActiveMQ broker. Note: For more information on customizing the settings of your ActiveMQ broker, refer to Amazon MQ documentation. 2. In the Base64 utility, run the following command to generate a Base64 encoded output of the content of the XML file: cat <config_file_name>.xml | base64 -w 0 3. Perform one of the following steps to create the service instance: • In the Cloud Foundry (CF) Command Line Interface, run the following command: cf create-service cloud-message-queue <subscription_plan_name> <service_instance_name> -c '{"EngineVersion": "<ActiveMQ_broker_engine_version>", "Description":"<description_string>",
Load more

Recommended publications
  • D-Bus, the Message Bus System Training Material
    Maemo Diablo D-Bus, The Message Bus System Training Material February 9, 2009 Contents 1 D-Bus, The Message Bus System 2 1.1 Introduction to D-Bus ......................... 2 1.2 D-Bus architecture and terminology ................ 3 1.3 Addressing and names in D-Bus .................. 4 1.4 Role of D-Bus in maemo ....................... 6 1.5 Programming directly with libdbus ................. 9 1 Chapter 1 D-Bus, The Message Bus System 1.1 Introduction to D-Bus D-Bus (the D originally stood for "Desktop") is a relatively new inter process communication (IPC) mechanism designed to be used as a unified middleware layer in free desktop environments. Some example projects where D-Bus is used are GNOME and Hildon. Compared to other middleware layers for IPC, D-Bus lacks many of the more refined (and complicated) features and for that reason, is faster and simpler. D-Bus does not directly compete with low level IPC mechanisms like sock- ets, shared memory or message queues. Each of these mechanisms have their uses, which normally do not overlap the ones in D-Bus. Instead, D-Bus aims to provide higher level functionality, like: Structured name spaces • Architecture independent data formatting • Support for the most common data elements in messages • A generic remote call interface with support for exceptions (errors) • A generic signalling interface to support "broadcast" type communication • Clear separation of per-user and system-wide scopes, which is important • when dealing with multi-user systems Not bound to any specific programming language (while providing a • design that readily maps to most higher level languages, via language specific bindings) The design of D-Bus benefits from the long experience of using other mid- dleware IPC solutions in the desktop arena and this has allowed the design to be optimised.
    [Show full text]
  • Robust Messaging with Rabbitmq
    Spring RabbitMQ for High Load Martin Toshev Who am I Software consultant (CoffeeCupConsulting) BG JUG board member (http://jug.bg) OpenJDK and Oracle RDBMS enthusiast Twitter: @martin_fmi 2 3 Agenda • Messaging Basics • RabbitMQ Overview • Spring RabbitMQ 4 Messaging Basics 5 Messaging • Messaging provides a mechanism for loosely-coupled integration of systems • The central unit of processing in a message is a message which typically contains a body and a header 6 Use cases • Offloading long-running tasks to worker nodes • Distributing and processing high loads of data • Aggregating logs and propagating events between systems • Many others … 7 Messaging protocols • Messaging solutions implement different protocols for transferring of messages such as AMQP, XMPP, MQTT, STOMP, Kafka binary protocol and others • The variety of protocols imply vendor lock-in 8 Messaging protocols comparison AMQP MQTT XMPP STOMP Kafka goal replacement of messaging for instant messaging, message-oriented processing of large proprietary protocols resource-constrained adopted for wider middleware real-time data feeds devices use format binary binary XML-based text-based binary API divided into classes simple (5 basic different XML items ~ 10 basic commands 42 request types in (> 40 methods in operations with 2-3 with multiple types latest version (Kafka RabbitMQ) packet types for each) 2.0.0) reliability publisher/subscriber acknowledgements Acknowledgments Subscriber Acknowledgements, acknowledgements, and resumptions acknowledgements transactional transactions
    [Show full text]
  • Beej's Guide to Unix IPC
    Beej's Guide to Unix IPC Brian “Beej Jorgensen” Hall [email protected] Version 1.1.3 December 1, 2015 Copyright © 2015 Brian “Beej Jorgensen” Hall This guide is written in XML using the vim editor on a Slackware Linux box loaded with GNU tools. The cover “art” and diagrams are produced with Inkscape. The XML is converted into HTML and XSL-FO by custom Python scripts. The XSL-FO output is then munged by Apache FOP to produce PDF documents, using Liberation fonts. The toolchain is composed of 100% Free and Open Source Software. Unless otherwise mutually agreed by the parties in writing, the author offers the work as-is and makes no representations or warranties of any kind concerning the work, express, implied, statutory or otherwise, including, without limitation, warranties of title, merchantibility, fitness for a particular purpose, noninfringement, or the absence of latent or other defects, accuracy, or the presence of absence of errors, whether or not discoverable. Except to the extent required by applicable law, in no event will the author be liable to you on any legal theory for any special, incidental, consequential, punitive or exemplary damages arising out of the use of the work, even if the author has been advised of the possibility of such damages. This document is freely distributable under the terms of the Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 License. See the Copyright and Distribution section for details. Copyright © 2015 Brian “Beej Jorgensen” Hall Contents 1. Intro................................................................................................................................................................1 1.1. Audience 1 1.2. Platform and Compiler 1 1.3.
    [Show full text]
  • An Introduction to Linux IPC
    An introduction to Linux IPC Michael Kerrisk © 2013 linux.conf.au 2013 http://man7.org/ Canberra, Australia [email protected] 2013-01-30 http://lwn.net/ [email protected] man7 .org 1 Goal ● Limited time! ● Get a flavor of main IPC methods man7 .org 2 Me ● Programming on UNIX & Linux since 1987 ● Linux man-pages maintainer ● http://www.kernel.org/doc/man-pages/ ● Kernel + glibc API ● Author of: Further info: http://man7.org/tlpi/ man7 .org 3 You ● Can read a bit of C ● Have a passing familiarity with common syscalls ● fork(), open(), read(), write() man7 .org 4 There’s a lot of IPC ● Pipes ● Shared memory mappings ● FIFOs ● File vs Anonymous ● Cross-memory attach ● Pseudoterminals ● proc_vm_readv() / proc_vm_writev() ● Sockets ● Signals ● Stream vs Datagram (vs Seq. packet) ● Standard, Realtime ● UNIX vs Internet domain ● Eventfd ● POSIX message queues ● Futexes ● POSIX shared memory ● Record locks ● ● POSIX semaphores File locks ● ● Named, Unnamed Mutexes ● System V message queues ● Condition variables ● System V shared memory ● Barriers ● ● System V semaphores Read-write locks man7 .org 5 It helps to classify ● Pipes ● Shared memory mappings ● FIFOs ● File vs Anonymous ● Cross-memory attach ● Pseudoterminals ● proc_vm_readv() / proc_vm_writev() ● Sockets ● Signals ● Stream vs Datagram (vs Seq. packet) ● Standard, Realtime ● UNIX vs Internet domain ● Eventfd ● POSIX message queues ● Futexes ● POSIX shared memory ● Record locks ● ● POSIX semaphores File locks ● ● Named, Unnamed Mutexes ● System V message queues ● Condition variables ● System V shared memory ● Barriers ● ● System V semaphores Read-write locks man7 .org 6 It helps to classify ● Pipes ● Shared memory mappings ● FIFOs ● File vs Anonymous ● Cross-memoryn attach ● Pseudoterminals tio a ● proc_vm_readv() / proc_vm_writev() ● Sockets ic n ● Signals ● Stream vs Datagram (vs uSeq.
    [Show full text]
  • Rocketbufs: a Framework for Building Efficient, In-Memory, Message-Oriented Middleware
    RocketBufs: A Framework for Building Efficient, In-Memory, Message-Oriented Middleware Huy Hoang, Benjamin Cassell, Tim Brecht, Samer Al-Kiswany Cheriton School of Computer Science, University of Waterloo ABSTRACT ACM Reference Format: As companies increasingly deploy message-oriented middleware Huy Hoang, Benjamin Cassell, Tim Brecht, Samer Al-Kiswany. 2020. Rock- (MOM) systems in mission-critical components of their infrastruc- etBufs: A Framework for Building Efficient, In-Memory, Message-Oriented Middleware. In The 14th ACM International Conference on Distributed and tures and services, the demand for improved performance and func- Event-based Systems (DEBS ’20), July 13–17, 2020, Virtual Event, QC, Canada. tionality has accelerated the rate at which new systems are being ACM, New York, NY, USA, 12 pages. https://doi.org/10.1145/3401025.3401744 developed. Unfortunately, existing MOM systems are not designed to take advantages of techniques for high-performance data center communication (e.g., RDMA). In this paper, we describe the design 1 INTRODUCTION and implementation of RocketBufs, a framework which provides Message-Oriented Middleware (MOM) systems, also often referred infrastructure for building high-performance, in-memory Message- to as publish/subscribe, message-queuing, or event-based systems, Oriented Middleware (MOM) applications. RocketBufs provides are a popular class of software designed to support loosely-coupled memory-based buffer abstractions and APIs, which are designed messaging in modern distributed applications. Examples of appli- to work efficiently with different transport protocols. Applications cations and services that utilize MOM systems include IBM’s cloud implemented using RocketBufs manage buffer data using input functions [29], the Apache OpenWhisk serverless framework [10], (rIn) and output (rOut) classes, while the framework is responsible the Hyperledger blockchain framework [7] and streaming media for transmitting, receiving and synchronizing buffer access.
    [Show full text]
  • Analysis of Notification Methods with Respect to Mobile System Characteristics
    Proceedings of the Federated Conference on DOI: 10.15439/2015F6 Computer Science and Information Systems pp. 1183–1189 ACSIS, Vol. 5 Analysis of notification methods with respect to mobile system characteristics Piotr Nawrocki ∗, Mikołaj Jakubowski † and Tomasz Godzik ‡ ∗AGH University of Science and Technology, al. A. Mickiewicza 30, 30-059 Krakow, Poland e-mail:[email protected] †e-mail:[email protected] ‡e-mail:[email protected] Abstract—Recently, there has been an increasing need for most promise and therefore the purpose is to discern their secure, efficient and simple notification methods for mobile usefulness in the best way possible. systems. Such systems are meant to provide users with precise In addition to the protocols and methods above, we inves- tools best suited for work or leisure environments and a lot of effort has been put into creating a multitude of mobile tigated other solutions, such as the Apple push notification applications. However, not much research has been put at the or Line application which, for various reasons, were not same time into determining which of the available protocols considered further. The Apple push notification technology is a are best suited for individual tasks. Here a number of basic good solution, but it is proprietary, i.e. limited to Apple devices notification methods are presented and tests are performed for and that is why we decided to test more universal solutions the most promising ones. An attempt is made to determine which methods have the best throughput, latency, security and other first. There are also solutions (applications) that use their own characteristics.
    [Show full text]
  • AMQP and Rabbitmq Message Queuing As an Integration Mechanism
    2/19/2018 MQTT A protocol for communicating with your things David Brinnen and Brett Cameron SESAM Seminar, March 2018 Abstract The Internet of Things refers to the ever-growing network of physical devices that have IP connectivity, allowing them to connect to the internet, and the communication that occurs between these devices and other internet-enabled devices and systems. In this talk, Brett and David will introduce the Internet of Things and will discuss some of the key technologies associated with the creation of Internet of Things solutions and services within the manufacturing domain. Particular attention will be given to MQTT, which is gaining acceptance as the preferred protocol for use by the Internet of Things applications. Currently available implementations of MQTT will be briefly reviewed and case studies illustrating the application of the protocol will be presented. Some examples of how MQTT might be used to implement secure, fault-tolerant, and scalable Internet of Things solutions will be discussed, and the application and use of MQTT in Next Generation SCADA systems that need to monitor and control devices at scale in a connected world will be will be discussed and demonstrated. 2 2/19/2018 About David Since completing his Masters studies in Embedded Software at the Swedish Royal Institute of Technology 2015 (KTH), David has been working as a software engineer across a range of projects, including the implementation of control logical and the commissioning of Energy Machines integrated energy systems and air handling units (https://www.energymachines.com/), and the development of a next-generation SADA platform (ControlMachines™) and simulation software to control, monitor, and model Energy Machines deployments.
    [Show full text]
  • Open Message Queue Technical Overview Release 5.0
    Open Message Queue Technical Overview Release 5.0 May 2013 This book provides an introduction to the technology, concepts, architecture, capabilities, and features of the Message Queue messaging service. Open Message Queue Technical Overview, Release 5.0 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Multiprocess Communication and Control Software for Humanoid Robots Neil T
    IEEE Robotics and Automation Magazine Multiprocess Communication and Control Software for Humanoid Robots Neil T. Dantam∗ Daniel M. Lofaroy Ayonga Hereidx Paul Y. Ohz Aaron D. Amesx Mike Stilman∗ I. Introduction orrect real-time software is vital for robots in safety-critical roles such as service and disaster response. These systems depend on software for Clocomotion, navigation, manipulation, and even seemingly innocuous tasks such as safely regulating battery voltage. A multi-process software design increases robustness by isolating errors to a single process, allowing the rest of the system to continue operating. This approach also assists with modularity and concurrency. For real-time tasks such as dynamic balance and force control of manipulators, it is critical to communicate the latest data sample with minimum latency. There are many communication approaches intended for both general purpose and real-time needs [19], [17], [13], [9], [15]. Typical methods focus on reliable communication or network-transparency and accept a trade-off of increased mes- sage latency or the potential to discard newer data. By focusing instead on the specific case of real-time communication on a single host, we reduce communication latency and guarantee access to the latest sample. We present a new Interprocess Communication (IPC) library, Ach,1 which addresses this need, and discuss its application for real-time, multiprocess control on three humanoid robots (Fig. 1). There are several design decisions that influenced this robot software and motivated development of the Ach library. First, to utilize decades of prior development and engineering, we implement our real-time system on top of a POSIX-like Operating System (OS)2.
    [Show full text]
  • Sarath Singapati Inter Process Communication in Android Master of Science Thesis
    SARATH SINGAPATI INTER PROCESS COMMUNICATION IN ANDROID MASTER OF SCIENCE THESIS Examiner: Professor Tommi Mikkonen Examiner and thesis subject approved by The Faculty of Computing and Electrical Engineering on 7th March 2012 II ABSTRACT TAMPERE UNIVERSITY OF TECHNOLOGY Master’s Degree Programme in Information Technology SARATH SINGAPATI INTER PROCESS COMMUNICATION IN ANDROID Master of Science Thesis, 45 pages, 4 Appendix pages June 2012 Major: Software Systems Examiner: Professor Tommi Mikkonen Keywords: Android, Google, mobile applications, Process, IPC Google's Android mobile phone software platform is currently the big opportunity for application software developers. Android has the potential for removing the barriers to success in the development and sale of a new generation of mobile phone application software. Just as the standardized PC and Macintosh platforms created markets for desktop and server software, Android, by providing a standard mobile phone application environment, creates a market for mobile applications and the opportunity for applica- tions developers to profit from those applications. One of the main intentions of Android platform is to eliminate the duplication of functionality in different applications to allow functionality to be discovered and in- voked on the fly, and to let users replace applications with others that offer similar func- tionality. The main problem here is how to develop applications that must have as few dependencies as possible, and must be able to provide services to other applications. This thesis studies the Android mobile operating system, its capabilities in develop- ing applications that communicate with each other and provide services to other applica- tions. As part of the study, a sample application called “Event Planner”, has been devel- oped to experiment how Inter Process Communication works in Android platform, ex- plains how to implement, and use Inter Process Communication (IPC).
    [Show full text]
  • [MS-MQOD]: Message Queuing Protocols Overview
    [MS-MQOD]: Message Queuing Protocols Overview Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected].
    [Show full text]
  • Writing a Message Broker in Golang
    Writing a Message Broker in GoLang George Vanburgh Supervised by Alvaro A.A. Fernandes May 3, 2016 A report submitted in part fulfilment of the degree of BSc (Hons) in Computer Science with Industrial Experience Abstract This report details an exercise in learning and evaluating the 'Go' programming language, by building a feature-rich application message broker using modern software engineering techniques and best practises. Some of the unique features of Go are presented, and the importance and relevance of these features in building simple, high-performance distributed software is explored. Discussion of the novel 'CSP-style' concurrency features in Go lead to an unorthodox design proposal for an enterprise-style messaging broker - George's Asynchronous Message Broker (gamq). The implementation of gamq is then is then described and critiqued. Finally, the process and results of the software testing are presented, and analysed. Acknowledgements Many thanks to my supervisor, Alvaro Fernandes, for his continuous support, guidance and patience - without which, this project would have been impossible. Thanks also go to my family and friends for their help and encouragement both during this project, and throughout my time at University. Contents 1 Introduction 3 1.1 Background . .3 1.2 Goals . .3 2 Background 4 2.1 Messages . .4 2.2 Message Brokers . .4 2.2.1 Pub/Sub . .6 2.2.2 Queues . .8 2.2.3 Topics . .8 2.3 Broker Requirements . .8 2.3.1 Failure Handling . 10 2.3.2 Network Bandwidth Utilisation . 10 2.3.3 Network latency . 10 2.3.4 Network packet loss . 11 2.3.5 Message power cost .
    [Show full text]