Book Image

Spring 5.0 By Example

By : Claudio Eduardo de Oliveira
Book Image

Spring 5.0 By Example

By: Claudio Eduardo de Oliveira

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.
Table of Contents (17 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Contributors
Preface
Index

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 small machines and try to scale applications horizontally. In this scenario, the servlet spec can be switched to an architecture...