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)

Creating a message producer/message consumer

Having restructured our application to make room for comments, let's get to it!

First of all, we need to add a new dependency to our build file, which is done with the following code:

    compile('org.springframework.boot:spring-boot-starter-amqp')

That will give us access to Spring AMQP, which includes RabbitMQ support.

Adding messaging technology to our application may make us clamor to, well, write some code that talks to RabbitMQ. But that isn't really a good flow. Instead, we should start from one of two perspectives--writing a unit test or writing some UI.

Either approach is aimed at figuring out the use case we are trying to solve. Before solving the problem at hand, we need to noodle out what our exact problem is. In this case, let's start from the UI perspective.

To do that, we can take advantage of...