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

Spring Cloud service discovery


The service discovery is one of the key points of the microservices architecture. The basis of the microservices architecture is to decouple the monolithic application into smaller pieces of software which have well-defined boundaries.

This impacts our system design in the monolithic application. In general, the application logic stays in a single place with regards to the code. It means the procedure or methods calls are invoked in the same context when the application is running.

When we adopt the microservices architectural style, these invocations are typically external, in other words, they will invoke the service through HTTP calls, for example, in another application context or web server.

Then, the services need to call other services through HTTP, for instance, but how do the services call the others if the instances of these services change with a considerable frequency? Remember, we are creating distributed and scalable systems, where the instances...