Book Overview & Buying
Table Of Contents
Feedback & Rating

Spring 5.0 By Example

By : de Oliveira

2.7 (3)

Buy this Book

Spring 5.0 By Example

2.7 (3)

By: de Oliveira

Buy this Book

Overview of this book

With growing demands, organizations are looking for systems that are robust and scalable. Therefore, the Spring Framework has become the most popular framework for Java development. It not only simplifies software development but also improves developer productivity. This book covers effective ways to develop robust applications in Java using Spring. The book has three parts, where each one covers the building of a comprehensive project in Java and Spring. In the first part, you will construct a CMS Portal using Spring's support for building REST APIs. You will also learn to integrate these APIs with AngularJS and later develop this application in a reactive fashion using Project Reactor, Spring WebFlux, and Spring Data. In the second part, you’ll understand how to build a messaging application, which will consume the Twitter API and perform filtering and transformations. Here, you will also learn about server-sent events and explore Spring’s support for Kotlin, which makes application development quick and efficient. In the last part, you will build a real microservice application using the most important techniques and patterns such as service discovery, circuit breakers, security, data streams, monitoring, and a lot more from this architectural style. By the end of the book, you will be confident about using Spring to build your applications.

Preface

Who this book is for

What this book covers

To get the most out of this book

Get in touch

Free Chapter

Journey to the Spring World

Spring modularity

Setting up our development environment

Summary

Starting in the Spring World – the CMS Application

Creating the CMS application structure

Running the application

Creating the REST resources

Adding service layer

Integrate with AngularJS

Summary

Persistence with Spring Data and Reactive Fashion

Learning the basics of Docker

Spring Data project

Creating the final data access layer

Creating the Docker image for CMS

Putting in Reactive fashion

Summary

Kotlin Basics and Spring Data Redis

Learning Kotlin basics

Wrapping it up

Creating the project

Running the Redis instance

Understanding Redis

Spring Data Reactive Redis

Creating a Twitter application

Testing APIs

Summary

Reactive Web Clients

Creating the Twitter Gathering project

Starting the RabbitMQ server with Docker

Spring Messaging AMQP

Enabling Twitter in our application

Spring reactive web clients

Changing the Tracked Hashtag Service

Testing the microservice's integrations

Spring Actuator

Summary

Playing with Server-Sent Events

Creating the Tweet Dispatcher project

Server-Sent Events

Reactor RabbitMQ

Filtering streams

Dockerizing the whole solution

Running the containerized solution

The docker-compose tool

Summary

Airline Ticket System

The Airline Ticket System

Spring Cloud Config Server

Spring Cloud service discovery

Spring Cloud Zipkin server and Sleuth

Spring Cloud Gateway

Putting the infrastructure on Docker

Summary

Circuit Breakers and Security

Understanding the service discovery power

Flights microservice

When the services fail, hello Hystrix

Spring Boot Admin

Spring Cloud Zuul

Summary

Putting It All Together

The airline Bookings microservice

The airline Payments microservice

Learning about the Turbine server

Hystrix Dashboard

Creating the Mail microservice

Creating the Authentication microservice

Monitoring the microservices

Dockerizing the microservices

Running the system

Summary

Other Books You May Enjoy

Leave a review - let other readers know what you think

Customer Reviews

2.7 (3)

5 star

33.3%

4 star

3 star

2 star

33.3%

1 star

33.3%

Putting in Reactive fashion

We have been creating an amazing application with Spring Boot. The application was built on the traditional web stack present on Spring Framework. It means the application uses the web servers based on Servlet APIs.

The servlet specification was built with the blocking semantics or one-request-per-thread model. Sometimes, we need to change the application architecture because of non-functional requirements. For example, if the application was bought by a huge company, and that company wanted to create a plan to launch the application for the entire world, the volume of requests would probably increase a lot. So, we need to change the architecture to adapt the application structure for cloud environments.

Usually, in a cloud environment, the machines are smaller than traditional data centers. Instead of a big machine, it is popular to use many...