技术控

    今日:151| 主题:49194
收藏本版 (1)
最新软件应用技术尽在掌握

[其他] Messaging as a Service on OpenShift

[复制链接]
抱歉我无梦赠你 发表于 2016-10-3 22:11:01
87 1

立即注册CoLaBug.com会员,免费获得投稿人的专业资料,享用更多功能,玩转个人品牌!

您需要 登录 才可以下载或查看,没有帐号?立即注册

x
Inspired by a great blog post by Jakub Scholz on “Scalable AMQP infrastructure using Kubernetes and Apache Qpid”, I wanted to write a post about the ongoing effort to build Messaging-as-a-Service at Red Hat. Messaging components such as the Apache Qpid Dispatch Router , ActiveMQ Artemis and Qpidd scales well individually, but scaling a large deployment can become unwieldy. As Scholtz demonstrates, there are a lot of manual setup when creating such a cluster using kubernetes directly.
   The EnMasse project was created to provide the required tools and services for deploying and running a messaging service on OpenShift . Running on OpenShift means you can either run EnMasse on your own instance or in the cloud. You can also run EnMasse on OpenShift Origin , which is the upstream community project.
  The long term goals with the EnMasse project is to build a messaging service with the following properties:
  
       
  • Different communication patterns like request-response, pub-sub and events   
  • Store-and-forward semantics   
  • Support for a variety of different protocols like AMQP, MQTT, HTTP(1.1 & 2), CoAP and STOMP   
  • Multi-tenancy   
  • Scalability   
  • Elasticity without disruption  
  The rest of this post provides an initial overview of EnMasse. EnMasse is still under
  development, so a lot of the features mentioned may not be implemented or they are work in progress.
  EnMasse can be configured with a list of addresses. Each address can have 4 different semantics in EnMasse:
  
       
  • Anycast: Messages go from a client, through the router network, to another client connected to the router network on the same address.   
  • Broadcast: Messages go from a client, through  the router network to all clients connected to the router network on the same address.   
  • Queue: Messages go from a client to a queue. Another client can read the message from the queue at a later point.   
  • Topic: Aka. pub/sub. Messages go from a publisher client to multiple clients subscribed to the same address.  
  EnMasse is composed of the router network, the broker clusters, and the cluster admin components. The router network and the broker clusters handle messages, while the cluster admin components handles the router and broker configuration.
   
Messaging as a Service on OpenShift-1 (following,services,required,directly,creating)

  Router

  EnMasse uses the Apache Qpid Dispatch Router to scale the service in terms of the number of connections it can handle as well as the throughput.  The router also hides the brokers from the client so that the brokers themselves may be scaled, moved, upgraded and changed without the client noticing.
  Broker

  EnMasse creates broker clusters for queue and topic addresses. At present, EnMasse only supports ActiveMQ Artemis (or Red Hat JBoss A-MQ) as the message broker, though other brokers might be supported in the future. The brokers can also be scaled in the same way as routers, and EnMasse will ensure the cluster is configured correctly.
  Cluster administration

  EnMasse contains several cluster administration components that manages the router and broker configuration:
  
       
  • The configuration service provides a way for the router agent and the subscription service to subscribe for a list of all addresses configured in EnMasse.   
  • The router agent is responsible for configuring the network of routers based on the address configuration.   
  • The subscription service is responsible for managing durable subscriptions so that a reconnecting client will transparently connect to the same broker.   
  • The storage controller is responsible for creating, reconfiguring and deleting broker clusters based on two configuration files stored as openshift config maps. This component can be omitted, but will ease the maintenance when you want to configure multiple addresses.  
   I will try to write more articles about EnMasse as we are progressing with new features and improvements. For now, you can easily get started by following the github example . Do not hesitate to report bugs, and all contributions are always welcome.
      JoinRed Hat Developers, a developer program for you to learn, share, and code faster – and get access to Red Hat software for your development.  The developer program and software are both free!
友荐云推荐




上一篇:Arduino on Arduino battle ends in reconciliation, merger
下一篇:Query DynamoDB Items with DynamoDBMapper
酷辣虫提示酷辣虫禁止发表任何与中华人民共和国法律有抵触的内容!所有内容由用户发布,并不代表酷辣虫的观点,酷辣虫无法对用户发布内容真实性提供任何的保证,请自行验证并承担风险与后果。如您有版权、违规等问题,请通过"联系我们"或"违规举报"告知我们处理。

jpujze 发表于 2016-10-3 23:40:13
站位支持
回复 支持 反对

使用道具 举报

*滑动验证:
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

我要投稿

推荐阅读

扫码访问 @iTTTTT瑞翔 的微博
回页顶回复上一篇下一篇回列表手机版
手机版/CoLaBug.com ( 粤ICP备05003221号 | 文网文[2010]257号 )|网站地图 酷辣虫

© 2001-2016 Comsenz Inc. Design: Dean. DiscuzFans.

返回顶部 返回列表