Analytics Vasiliki (Vasia) Kalavri
 vkalavri@bu.edu Spring 2020 1/28: Stream ingestion and pub/sub systems Streaming sources Files, e.g. transaction logs Sockets IoT devices and sensors Databases notify unsubscribe advertise(): information reg. future events Publish/Subscribe Systems 17 Pub/Sub levels of de-coupling • Space: interacting parties do not need to know each other • Publishers Decoupling Message-passing RPC/RMI Asynchronous RPC Futures Message Queues Pub/Sub Yes Yes Yes Can you fill this in? 19 Pub/Sub vs. other paradigms Paradigm Space Decoupling Time Decoupling Synchronization

Password for client connection permissions: - action: Operation type of permission. `pub` means publish permission, `sub` ˓→means subscription permission. permit: List of topics allowed by the operation Username for client ssl connection permissions: - action: Operation type of permission. `pub` means publish permission, `sub` ˓→means subscription permission. permit: List of topics allowed by the operation permissions: - action: 'pub' permit: ['tls/#'] - action: 'sub' permit: ['tls/#'] - username: test password: hahaha permissions: - action: 'pub' permit: ['#'] - action: 'sub' permit: ['#'] subscriptions:

for client connection permissions: - action: Operation type of permission. `pub` means publish permission, `sub` means subscription permission. permit: List of topics allowed by the operation client ssl connection permissions: - action: Operation type of permission. `pub` means publish permission, `sub` means subscription permission. permit: List of topics allowed by the operation action: 'pub' permit: ['tls/#'] - action: 'sub' permit: ['tls/#'] - username: test password: hahaha permissions: - action: 'pub' permit: ['#'] - action: 'sub'

Password for client connection permissions: - action: Operation type of permission. `pub` means publish permission, `sub` ˓→means subscription permission. permit: List of topics allowed by the operation Username for client ssl connection permissions: - action: Operation type of permission. `pub` means publish permission, `sub` ˓→means subscription permission. permit: List of topics allowed by the operation permissions: - action: 'pub' permit: ['tls/#'] (continues on next page) 48 Chapter 7. Device connect to Hub Service BAETYL Documentation (continued from previous page) - action: 'sub' permit: ['tls/#']

for client connection permissions: - action: Operation type of permission. `pub` means publish permission, `sub` means subscription permission. permit: List of topics allowed by the operation client ssl connection permissions: - action: Operation type of permission. `pub` means publish permission, `sub` means subscription permission. permit: List of topics allowed by the operation action: 'pub' permit: ['tls/#'] - action: 'sub' permit: ['tls/#'] - username: test password: hahaha permissions: - action: 'pub' permit: ['#'] - action: 'sub'

用硬件和驱动 驱动程序 程序启 启用 用 10 b. 运行以下命令来创建 OperatorGroup CR: c. 创建以下 Subscription CR，并将 YAML 保存到 nfd-sub.yaml 文件中： 订阅 订阅示例 d. 运行以下命令来创建订阅对象： e. 进入 openshift-nfd 项目： 验证 验证 要验证 Operator 部署是否成功，请运行： 输 name: nfd source: redhat-operators sourceNamespace: openshift-marketplace $ oc create -f nfd-sub.yaml $ oc project openshift-nfd $ oc get pods NAME READY 创建以下 OperatorGroup CR 并保存 YAML 文件，如 kmm-op-group.yaml ： c. 创建以下 Subscription CR 并保存 YAML 文件，如 kmm-sub.yaml ： apiVersion: v1 kind: Namespace metadata: name: openshift-kmm apiVersion: operators.coreos

Galley Injector MQ Broker Envoy MQ Broker Envoy MQ Broker Envoy 注册 Service Service Service Pub sub Pub sub Pub sub xDS Config • MQ Broker把Envoy作为 它与服务之间的代理 • Envoy拓展兼容了PubSub 通信的协议，比如 RocketMQ的通信协议 • Service的代码依然使用

Encapsulation, MitM attacks on Service Invocation, DoS attack mitigations, API Authentication and Pub/Sub scoping. Since Dapr is available as open source software, the adopted methodology was clearly a python-app (for testing), crypto implementations, secrets storage features, network filtering features, pub/sub mechanism implementations, authentication features and throttling. ◦ Sources ▪ Repository: • https://github PING +PONG CLIENT LIST $155 id=194029 addr=10.244.2.7:41477 fd=9 name= age=60 idle=0 flags=N db=0 sub=0 psub=0 multi=-1 qbuf=12 qbuf-free=32756 obl=0 oll=0 omem=0 events=r cmd=client In order to ensure

RocketMQ, Azure queue, service bus, Redis, MySQL, NATS streaming, Kafka, GCP pub/sub - Test RocketMQ examples : Pub/sub, Broadcast, Schedule, Batch, Filter, Logappender, OpenMessaging, Transaction

默认消费组权限，该值默认为 DENY(拒绝)，建议值为 SUB。  topicPerms 设置 topic 的权限。其类型为数组，其可选择值在下节介绍。  groupPerms 设置消费组的权限。其类型为数组，其可选择值在下节介绍。可以为每一消费组配置不 一样的权限。 2. RocketMQ ACL 权限可选值  DENY 拒绝。  PUB 拥有发送权限。 本文来自『中间件兴趣圈 本文来自『中间件兴趣圈』公众号，仅作技术交流，未授权任何商业行为。 145 > 1.15 RocketMQ ACL 使用指南  SUB 拥有订阅权限。 3. 权限验证流程 上面定义了全局白名单、用户级别的白名单，用户级别的权限，为了更好的配置 ACL 权限规则，下面给出权限匹配逻辑。 本文来自『中间件兴趣圈』公众号，仅作技术交流，未授权任何商业行为。 1.15 RocketMQ ACL 使用指南 < 146 12345678 whiteRemoteAddress: admin: false defaultTopicPerm: DENY defaultGroupPerm: SUB topicPerms: - TopicTest=PUB groupPerms: 本文来自『中间件兴趣圈』公众号，仅作技术交流，未授权任何商业行为。 1.15 RocketMQ ACL 使用指南 < 148 # the