Modern Messaging with RabbitMQ, Spring Cloud, and Reactor

Modern Messaging with RabbitMQ,
Spring Cloud, and Reactor
Arnaud Cogoluègnes
@acogoluegnes

© 2013-2018 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license:
http://creativecommons.org/licenses/by-nc/3.0/
Disclaimer
2

Safe Harbor Statement
The following is intended to outline the general direction of Pivotal's offerings. It is intended for information
purposes only and may not be incorporated into any contract. Any information regarding pre-release of
Pivotal offerings, future updates or other planned modifications is subject to ongoing evaluation by Pivotal
and is subject to change. This information is provided without warranty or any kind, express or implied,
and is not a commitment to deliver any material, code, or functionality, and should not be relied upon in
making purchasing decisions regarding Pivotal's offerings. These purchasing decisions should only be
based on features currently available. The development, release, and timing of any features or
functionality described for Pivotal's offerings in this presentation remain at the sole discretion of Pivotal.
Pivotal has no obligation to update forward looking information in this presentation.
3

Arnaud Cogoluègnes
● Principal Software Engineer at Pivotal
● RabbitMQ Team
● Spring user since 2005
● Developer, trainer, consultant, author
4

Agenda
● RabbitMQ update
● RabbitMQ in Spring and Reactor worlds
● Tips for the best RabbitMQ development experience
5

Agenda
● RabbitMQ update
6

What is RabbitMQ
● Messaging broker
● Multi-protocol (AMQP 0-9-1, AMQP 1.0, MQTT, STOMP, …)
● Started in 2006
● Broad ecosystem including Spring support
● Clustering and high availability support
● Web management UI & REST API
7

RabbitMQ Ecosystem
● Officially supported clients: Java, Erlang, .NET, JMS
● Community-led clients: Ruby, Python, PHP, Objective-C, JavaScript, Go, C, C++
● And more…
● Higher-level clients: Spring AMQP, RawRabbit (.NET)
8

AMQP Model
9
Publishing
application
Consuming
application
Consuming
application
Exchange
Queues

When to use RabbitMQ?
● Enterprise Integration
● Asynchronicity, buffering for upstream when downstream is down
● High message rate, low latency use cases
● Many connections, low message rate, aka IoT use cases
10

What’s New RabbitMQ 3.7
● Released November 2017
● Focus on operations, usability, and reliability
● Operator policies and per-vhost message store (operations)
● New configuration format
● Peer discovery for cluster formation
● Proxy Protocol support for load balancing
11

Historical configuration format
● Erlang terms, difficult to work with, even for machines
12
[
{ssl, [{versions, ['tlsv1.2', 'tlsv1.1']}]},
{rabbit, [
{ssl_listeners, [5671]},
{ssl_options, [{cacertfile,"/path/to/ca_certificate.pem"},
{certfile, "/path/to/server_certificate.pem"},
{keyfile,
"/path/to/server_key.pem"},
{versions, ['tlsv1.2', 'tlsv1.1']}
]}
]}
].

New configuration format
● INI / sysctl inspired
● Easier to generate and parse for both humans and machines
● Validated against a schema
13
listeners.ssl.1 = 5671
ssl_options.cacertfile = /path/to/ca_certificate.pem
ssl_options.certfile = /path/to/server_certificate.pem
ssl_options.keyfile = /path/to/server_key.pem
ssl_options.versions.1 = tlsv1.2
ssl_options.versions.2 = tlsv1.1

Peer Discovery for Cluster Formation
14
Cluster
Where are
you guys?

Peer Discovery for Cluster Formation
● How do peers discover each other at first start
● Previously, only CLI tools and configuration file
● Not very automation friendly
● Peer discovery phase into the RabbitMQ boot sequence
● Support for AWS, Kubernetes, etcd, Consul, pre-configured DNS records
● Other can be supported by virtue of the plugin system
15

Proxy Protocol Support
● Common to use a proxy such as HAProxy or AWS ELB
● RabbitMQ could not display the real source IP
16
Client 2
<<ip-client-2>>
Client 3
<<ip-client-3>>
Client 1
<<ip-client-1>>
Proxy
<<ip-proxy>>
<<ip-proxy>>
<<ip-proxy>>
<<ip-proxy>>
Who’s this?

Proxy Protocol Support
● A solution to know about client IP: Proxy Protocol
● Opt-in and requires a compatible proxy
● No client library changes
17
Client 2
<<ip-client-2>>
Client 3
<<ip-client-3>>
Client 1
<<ip-client-1>>
Proxy
<<ip-proxy>>
<<ip-client-1>>
<<ip-client-2>>
<<ip-client-3>>
Much better!

Disclaimer
18
The following features may never happen.
This is R&D.
No promises.

http://creativecommons.org/licenses/by-nc/3.0/ 19
RabbitMQ Roadmap
● OAuth support
● New strongly consistent queue implementation, aka “Quorum Queue”
● Better network partition handling, aka. “Mnevis initiative”

Quorum Queue
● A new type of queue
● As long as more than half of nodes are available:
● Consistent (no message lost)
● Available
● Trades latency for throughput
● Builds on top of our own Raft library
● Raft: Consensus algorithm
● Jepsen tested
● Jepsen: toolkit to detect failures of a distributed system
● Should alleviate some of the shortcomings of mirrored queues
20

Better network partition handling
● Network partition handling heavily depends on Mnesia
● Mnesia is Erlang internal distributed key-value store
● RabbitMQ requirements don’t always align with Mnesia
● Network partition detection, partial partition handling, etc
● Expected outcomes:
● Better resilience to network partition
● Easier to choose between availability and consistency
● Experiments at their early stages...
21

RabbitMQ Java Client
● One of the officially supported clients
● The most used client
● Full support for AMQP 0.9.1 and RabbitMQ extensions
● Built-in support for automatic connection recovery
● 2 supported branches
● 4.x: Java 6+
● 5.x: Java 8+
● Independant release cycle since 4.0
● November 2016
22

New in RabbitMQ Java Client 4.0
● Automatic connection recovery enabled by default
● Logging support (!)
● Metrics support
● Dropwizard Metrics and Micrometer as of 4.3
● Java NIO connector (opt-in)
● With TLS support, no external dependency
● Topology recovery filtering and retry
23

New in RabbitMQ Java Client 5.0
● Java 8 is required
● Lambda-oriented API:
● For Consumers (message delivery, cancellation, etc)
● For Listeners (publish confirms, rejected messages, etc)
● Asynchronous RPC (with CompletableFuture)
24

Agenda
● RabbitMQ update
● RabbitMQ in the Spring and Reactor world
25

RabbitMQ in Spring and Reactor Worlds
26
Spring AMQP
Spring Boot
Reactor
Spring
Spring Integration
Spring Cloud
Spring Cloud Data Flow

Spring AMQP
27
Spring AMQP
Spring Boot
Reactor
Spring
Spring Integration
Spring Cloud

Spring AMQP
● Spring concepts for AMQP
● Template approach
● POJO programming (serialization/deserialization)
● Queue affinity for message consumption
● Built-in connection and topology recovery
● Sophisticated message container listeners
● Request/reply
28
Spring AMQP
Spring
Framework
RabbitMQ Java
Client

Spring Boot
29
Spring AMQP
Spring Boot
Reactor
Spring
Spring Integration
Spring Cloud

RabbitMQ Support in Spring Boot
● Declare and autowire:
● Connection factory
● Access template
● Asynchronous listeners
● Metrics for instrumentation of connections
30

Demo - Spring Boot & RabbitMQ
● Auto-configuration
● RabbitMQ Client metrics
● Prometheus endpoint
31

Reactor
32
Spring AMQP
Spring Boot
Reactor
Spring
Spring Integration
Spring Cloud

Reactor RabbitMQ
● Reactive and functional API for
RabbitMQ
● Reactor’s Flux and Mono API to
produce and consume messages
● Builds on top the Java client and
Reactor Core
33
Reactor RabbitMQ
Reactor
Core
RabbitMQ
Java Client

Reactor RabbitMQ
● Use cases:
● Manage exchanges, queues,
and bindings
● Publish a Flux of messages
● Consume messages as a Flux
34
Reactor RabbitMQ
Reactor
Core
RabbitMQ
Java Client

Reactor RabbitMQ
● Managing exchanges, queues, and bindings
35
Sender sender = ReactorRabbitMq.createSender(senderOptions);
sender.declare(exchange("my.exchange"))
.then(sender.declare(queue("my.queue")))
.then(sender.bind(binding("my.exchange", "a.b","my.queue")))
.subscribe(r -> System.out.println("Declared and bound"));

Reactor RabbitMQ
● Publishing messages
36
Flux<OutboundMessage> outboundFlux = ...
sender.send(outboundFlux)
.doOnError(e -> log.error("Send failed", e))
.subscribe();

Reactor RabbitMQ
● Publishing messages with publisher confirms
37
Flux<OutboundMessage> outboundFlux = ...
sender.sendWithPublishConfirms(outboundFlux)
.subscribe(outboundMessageResult -> {
log.info("Outbound message has reached the broker");
});

Reactor RabbitMQ
● Consuming messages
38
Receiver receiver = ReactorRabbitMq.createReceiver();
Flux<Delivery> inboundFlux = receiver
.consumeNoAck("reactive.queue");

Reactor RabbitMQ: other goodies
● Acknowledgment
● Retry on publishing
● Connection failure handling
● Request/reply with Mono
39

Reactor
40
Spring AMQP
Spring Boot
Reactor
Spring
Spring Integration
Spring Cloud

Reactive Monitoring over HTTP with HOP
● Java Client for RabbitMQ REST API
● Meant for administration and monitoring, not messaging
● 2 clients:
● Blocking client based on Spring’s RestTemplate
● Non-blocking, reactive client based on Reactor Netty
41

42
HOP
Spring Web
(RestTemplate)
Reactor Netty
RabbitMQ Management Plugin

● Compute message rate across virtual hosts:
43
ReactorNettyClient client = new ReactorNettyClient(
"http://localhost:15672/api", "guest", "guest"
);
Mono<Double> vhostsRate = client.getVhosts()
.map(vhostInfo -> vhostInfo.getMessagesDetails().getRate())
.reduce(0.0, (acc, current) -> acc + current);

Spring Framework
44
Spring AMQP
Spring Boot
Reactor
Spring
Spring Integration
Spring Cloud

Spring WebSocket
● In Spring MVC and Spring WebFlux
● Make web pages dynamic and reactive
● Good for low latency, high frequency, and high volume use cases
● Broker abstraction for message passing
● Local and STOMP relay implementations
45

Spring WebSocket, local broker
46
Browser 2
Browser 1
Web
Container
Notifications
Notifications

Spring WebSocket, local broker, cluster
47
Browser 1
Web
Container
Notifications
Web
Container
Browser 2
Notifications
ClusterClients DO NOT see each other

Spring WebSocket, STOMP broker, cluster
48
Browser 1
Web
Container
Notifications
Web
Container
Browser 2
Notifications
ClusterClients DO see each other

Demo - Spring WebSocket & RabbitMQ
● Handling global notifications with a full-blown broker
49

Spring Integration
50
Spring AMQP
Spring Boot
Reactor
Spring
Spring Integration
Spring Cloud

Spring Integration
● Make application agnostic to messaging technology
● Inbound/Outbound AMQP adapters (1-way)
● Inbound/Outbound AMQP gateway (2-way, for request/reply)
● AMQP-backed channel implementation
● Enterprise Integration Patterns
● Based on Spring AMQP
● Foundation for Spring Cloud Stream
51

Spring Cloud Stream
52
Spring AMQP
Spring Boot
Reactor
Spring
Spring Integration
Spring Cloud

Spring Cloud Stream
● Opinionated framework for
message-driven microservices
● Builds on top Spring Boot and Spring
Integration
● Concepts:
● Input and output bindings for
integration
● Processor for application logic
● Consumer groups and partitioning
for scaling
53
Spring Cloud Stream
Spring
Integration
Spring Boot
Spring AMQP

Spring Cloud Stream
● Where does RabbitMQ fit?
● It binds Spring Cloud Stream applications to each other
● Goodies: partitioning, dead lettering, batch sending, etc
54
Spring Cloud Stream Application Spring Cloud Stream Application

55
Spring AMQP
Spring Boot
Reactor
Spring
Spring Integration
Spring Cloud

● A place to deploy your streams
● Run the stream applications on a variety of runtime platforms
● RabbitMQ is the messaging middleware broker that connects applications
56
SCS App
SCS App
SCS App
SCS App
SCS App
SCS App
Apps run on Cloud Foundry, Kubernetes, Mesos, YARN

Spring Cloud
57
Spring AMQP
Spring Boot
Reactor
Spring
Spring Integration
Spring Cloud

Spring Cloud
● Many projects…
● Spring Cloud Config
58
Spring Cloud
Config
ApplicationApplicationApplicationGit
Get ${...}

Configuration Refresh
● Update @Refresh beans on configuration change
● Use Spring Cloud Config and Spring Cloud Bus
59
Spring Cloud
Config
ApplicationGit
Get ${...}
Push
Consume configuration
updates
POST /monitor

Agenda
● RabbitMQ update
60

Tips for the RabbitMQ Spring developer
● Tame the runtime: seamless RabbitMQ installation on your dev workstation
● Design properly: avoid common pitfalls
● Ship confidently: simulate your workload with PerfTest
61

RabbitMQ installation: Erlang
● RabbitMQ is written in Erlang
● Erlang applications run on the Erlang Virtual Machine
● How to install Erlang?
● On server: use ESL or RabbitMQ Team native packages
● On dev workstation: use packages or kerl
62

Erlang installation with kerl
● Kerl compiles and installs Erlang SDK
● Why not native packages/installers?
● They don’t always ship with the latest patch release
● Hard to have different Erlang versions on the same machine
● Think of kerl as a SDKMAN! for Erlang
63

Erlang installation with kerl
● Compile Erlang patch release from GitHub:
● List the builds on the current machine:
64
$ kerl build git https://github.com/erlang/otp.git OTP-20.3.4 20.3.4
$ kerl list builds
git,19.1.1
git,19.1.5
git,19.2
git,19.2.3
git,20.0.1
git,20.3.4

RabbitMQ installation
● How to install RabbitMQ?
● On server: use RabbitMQ Team native packages
● On dev workstation: use packages or generic Unix binary
● Generic Unix binary
● For Linux, Unix, macOS
● Easy way to have several versions on the same machine
65

With the previous tips...
● Make development easier
● Use different Erlang and RabbitMQ versions
● Test migration scenarios locally
● Start several nodes and cluster them locally
66

Design tips: consuming
● Use auto-acknowledgment only with fast consumers
● Use acknowledgment and set quality of service (QoS) properly
● QoS: number of unacknowledged messages for a client channel
● Prevent overflowing a client with messages
● Make load balancing between consumers better
● Don’t use 1 for QoS, as it usually under-utilizes consumers
67

Design tips: scaling
● A queue has a limited throughput
● It’s an Erlang process ( ~ Java thread)
● Scale by using several queues
● Random/Consistent hash exchange, sharding plugin, Spring Cloud Stream
partition implementation
● Use top plugin to identify bottlenecks
● Process with the highest “Reductions / sec” is most likely a bottleneck
68

Workload simulation with PerfTest
● PerfTest is a throughput testing tool
● It can simulate simple to advanced workloads
● Now an independent project (used to ship with the Java client)
● Uses the Java client
● Eat your own dog food
● Used internally for our long-running environments and use-case-oriented
workloads
69

PerfTest overview
● Configurable publishing and consuming rates
● Topology creation and configuration (exchanges, bindings, queues)
● Message latency calculation
● Consumer latency configuration
● Custom message content to simulate real messages
● TLS configuration support
● Connection and topology recovery support
● Fine-grained threading options for typical IoT workloads
● Monitoring support through Micrometer
● Cloud Foundry template project
70

Simulate throughput workload
10 producers sending 1000 messages / second
10 consumers
10 queues (perf-test-1, perf-test-2, … perf-test-10)
71
$ ./runjava com.rabbitmq.perf.PerfTest --rate 1000
--producers 10 --consumers 10
--queue-pattern 'perf-test-%d'
--queue-pattern-from 1 --queue-pattern-to 10

Simulating IoT workloads
● 10 Ks, 100 Ks connections
● Puts a lot of pressure on the broker… and on the testing tool as well!
● Resource on the testing tool side:
● Memory
● Threads
● Files descriptors (connections)
● Serious optimizations needed to avoid using 10s, 100s of testing instances
72

Simulate IoT workload
100 producers sending 1 message every 5 seconds
Each producer starts between 1 and 120 seconds
300 consumers
=> ~ 1 K threads
73
$ ./runjava com.rabbitmq.perf.PerfTest
--publishing-interval 5 --producer-random-start-delay 120
--queue-pattern 'perf-test-%03d'

Simulate (bigger) IoT workload
1000 producers sending 1 message every 30 seconds
Each producer starts between 1 and 300 seconds
3000 consumers
=> ~ 150 threads
74
--publishing-interval 30 --producer-random-start-delay 300
--queue-pattern 'perf-test-%04d'
--heartbeat-sender-threads 10 --nio-threads 20
--consumers-thread-pools 100

Monitoring with PerfTest
● Expose PerfTest clients metrics, as well as JVM and OS metrics
● JMX, Datadog, and Prometheus supported so far
75
--metrics-prometheus

PerfTest dashboard with Grafana
76

Wrapping up
● RabbitMQ present in many places in Spring & Reactor stacks
● First-class support and integration
● Continuous effort to bring and maintain this support
77

Questions?
78

Thank you!
79

Resources
Code sample: https://github.com/acogoluegnes/spring-rabbitmq
RabbitMQ: http://www.rabbitmq.com/
RabbitMQ Java client: https://github.com/rabbitmq/rabbitmq-java-client
Reactor RabbitMQ: https://github.com/reactor/reactor-rabbitmq
Hop: https://github.com/rabbitmq/hop
Kerl: https://github.com/kerl/kerl
QoS: https://www.rabbitmq.com/blog/2012/05/11/some-queuing-theory-throughput-latency-and-bandwidth/
Queues in RabbitMQ: https://www.rabbitmq.com/queues.html#runtime-characteristics
PerfTest: https://github.com/rabbitmq/rabbitmq-perf-test/
PerfTest and IoT workloads: https://rabbitmq.github.io/rabbitmq-perf-test/stable/htmlsingle/#simulating-high-loads
80

Modern Messaging with RabbitMQ, Spring Cloud, and Reactor

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Modern Messaging with RabbitMQ, Spring Cloud, and Reactor

Similaire à Modern Messaging with RabbitMQ, Spring Cloud, and Reactor (20)

Plus de acogoluegnes

Plus de acogoluegnes (7)

Dernier

Dernier (20)

Modern Messaging with RabbitMQ, Spring Cloud, and Reactor