Book Image

Building Microservices with Spring

By : Dinesh Rajput, Rajesh R V
Book Image

Building Microservices with Spring

By: Dinesh Rajput, Rajesh R V

Overview of this book

Getting Started with Spring Microservices begins with an overview of the Spring Framework 5.0, its design patterns, and its guidelines that enable you to implement responsive microservices at scale. You will learn how to use GoF patterns in application design. You will understand the dependency injection pattern, which is the main principle behind the decoupling process of the Spring Framework and makes it easier to manage your code. Then, you will learn how to use proxy patterns in aspect-oriented programming and remoting. Moving on, you will understand the JDBC template patterns and their use in abstracting database access. After understanding the basics, you will move on to more advanced topics, such as reactive streams and concurrency. Written to the latest specifications of Spring that focuses on Reactive Programming, the Learning Path teaches you how to build modern, internet-scale Java applications in no time. Next, you will understand how Spring Boot is used to deploying serverless autonomous services by removing the need to have a heavyweight application server. You’ll also explore ways to deploy your microservices to Docker and managing them with Mesos. By the end of this Learning Path, you will have the clarity and confidence for implementing microservices using Spring Framework. This Learning Path includes content from the following Packt products: • Spring 5 Microservices by Rajesh R V • Spring 5 Design Patterns by Dinesh Rajput
Table of Contents (22 chapters)
Title Page
Copyright
About Packt
Contributors
Preface
Index

Understanding the reactive pattern


Today, the modern applications must be more robust, more resilient, more flexible, and better positioned to meet the requirements of the organizations, because, in the recent couple of years, the requirements for applications have changed dramatically. As we have seen in the last table, 10 to 15 years ago, a large application had 10 server nodes, the response time taken to serve a request was in seconds, we required a couple of hours of downtime for maintenance and deployment, and the data was in gigabytes. But today, an application requires thousands of server nodes, because it is accessed by multiple channels such as mobile devices. The server responses are expected within milliseconds, and the downtime for deployment and maintenance is near to 0%. Data has been increased from terabytes to petabytes.

Ten-year old systems cannot fulfill the requirements of today's applications; we need a system that can fulfill all user's requirements either at the application...