Book Image

Learning Spring Boot 2.0 - Second Edition

By : Greg L. Turnquist, Greg L. Turnquist
Book Image

Learning Spring Boot 2.0 - Second Edition

By: Greg L. Turnquist, Greg L. Turnquist

Overview of this book

Spring Boot provides a variety of features that address today's business needs along with today's scalable requirements. In this book, you will learn how to leverage powerful databases and Spring Boot's state-of-the-art WebFlux framework. This practical guide will help you get up and running with all the latest features of Spring Boot, especially the new Reactor-based toolkit. The book starts off by helping you build a simple app, then shows you how to bundle and deploy it to the cloud. From here, we take you through reactive programming, showing you how to interact with controllers and templates and handle data access. Once you're done, you can start writing unit tests, slice tests, embedded container tests, and even autoconfiguration tests. We go into detail about developer tools, AMQP messaging, WebSockets, security, and deployment. You will learn how to secure your application using both routes and method-based rules. By the end of the book, you'll have built a social media platform from which to apply the lessons you have learned to any problem. If you want a good understanding of building scalable applications using the core functionality of Spring Boot, this is the book for you.
Table of Contents (11 chapters)

Getting started with RabbitMQ

RabbitMQ is an open source AMQP broker. Advanced Message Queuing Protocol (AMQP) is an open protocol that includes the format of messages sent over the wire. This has risen in popularity compared to other messaging solutions like JMS. Why?

JMS is an API, whereas AMQP is a protocol. JMS defines how to talk to the broker but not the format of its messages. And it's confined to Java apps. AMQP doesn't speak about how to talk to a broker but about how messages are put on the wire and how they are pulled down.

To illustrate this point, imagine two different applications. If they were both Java, they could communicate via JMS. But if one of them were Ruby, JMS would be off the table.

To further demonstrate the differences between JMS and AMQP, a JMS-speaking broker can actually use AMQP under the hood to transport the messages.

In fact, I have...