Book Image

Mastering Spring Cloud

By : Piotr Mińkowski
Book Image

Mastering Spring Cloud

By: Piotr Mińkowski

Overview of this book

Developing, deploying, and operating cloud applications should be as easy as local applications. This should be the governing principle behind any cloud platform, library, or tool. Spring Cloud–an open-source library–makes it easy to develop JVM applications for the cloud. In this book, you will be introduced to Spring Cloud and will master its features from the application developer's point of view. This book begins by introducing you to microservices for Spring and the available feature set in Spring Cloud. You will learn to configure the Spring Cloud server and run the Eureka server to enable service registration and discovery. Then you will learn about techniques related to load balancing and circuit breaking and utilize all features of the Feign client. The book now delves into advanced topics where you will learn to implement distributed tracing solutions for Spring Cloud and build message-driven microservice architectures. Before running an application on Docker container s, you will master testing and securing techniques with Spring Cloud.
Table of Contents (22 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Introduction to HTTP API resources


The Config Server provides the HTTP API, which may be invoked in various ways. The following endpoints are available:

  • /{application}/{profile}[/{label}]: This returns data in a JSON format; the label parameter is optional
  • /{application}-{profile}.yml: This returns the YAML format
  • /{label}/{application}-{profile}.yml: A variant of the previous endpoint, where we can pass an optional label parameter
  • /{application}-{profile}.properties: This returns the simple key/value format used by properties files
  • /{label}/{application}-{profile}.properties: A variant of the previous endpoint, where we can pass an optional label parameter

From a client point of view, the application parameter is the name of the application, which is taken from the spring.application.name or spring.config.name property, and profile is an active profile or comma-separated list of active profiles. The last available parameter label is an optional property, important only while working with Git...