Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Spring Cloud

You're reading from   Mastering Spring Cloud Build self-healing, microservices-based, distributed systems using Spring Cloud

Arrow left icon
Product type Paperback
Published in Apr 2018
Publisher Packt
ISBN-13 9781788475433
Length 432 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Piotr Mińkowski Piotr Mińkowski
Author Profile Icon Piotr Mińkowski
Piotr Mińkowski
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Introduction to Microservices FREE CHAPTER 2. Spring for Microservices 3. Spring Cloud Overview 4. Service Discovery 5. Distributed Configuration with Spring Cloud Config 6. Communication Between Microservices 7. Advanced Load Balancing and Circuit Breakers 8. Routing and Filtering with API Gateway 9. Distributed Logging and Tracing 10. Additional Configuration and Discovery Features 11. Message-Driven Microservices 12. Securing an API 13. Testing Java Microservices 14. Docker Support 15. Spring Microservices on Cloud Platforms 16. Other Books You May Enjoy

Enabling Eureka on the client side


As on the server side, there is only one dependency that has to be included to enable a Eureka Client for the application. So, first include the following starter to your project's dependencies:

<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-eureka</artifactId>
</dependency>

The example application does nothing more than communicate with the Eureka Server. It has to register itself and send metadata information such as host, port, health indicator URL, and home page. Eureka receives heartbeat messages from each instance belonging to a service. If the heartbeat isn't received after a configured period of time, the instance is removed from the registry. The second responsibility of discovery client is fetching data from the server, then caching it and periodically asking for changes. It can be enabled by annotating the main class with @EnableDiscoveryClient. Surprisingly...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image