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)

Making local changes and seeing them on the target system

So far, we've seen how to speed up developer time by using automatic restarts, and we have gathered information on what Spring Boot is up to, courtesy of its autoconfiguration report.

The next step for developers is often using the debugger of their IDE. We won't go into profuse detail about that because it's highly specific to which IDE you use. However, something of extended value offered by Spring Boot is the opportunity to remotely connect to an application and make changes.

Imagine we have built up our application and pushed it to the cloud. We test a key feature in this environment because it's the only way to tie it to a particular resource or in a certain configuration. Well, the process for making changes is much more expensive. We would have to bundle things up, redeploy, restart, and re-navigate...