Welcome to Spring Microservices in Action, Chapter 3. Chapter 3 introduces the Spring Cloud Config service and how you can use it managed the configuration of your microservices. By the time you are done reading this chapter you will have built and/or deployed:
- A Spring Cloud Config server that is deployed as Docker container and can manage a services configuration information using a file system or GitHub-based repository.
- A organization service that will manage organization data used within EagleEye.
- A licensing service that will manage licensing data used within EagleEye.
- A Postgres SQL database used to hold the data for these two services.
- Docker (http://docker.com). I built the code examples in this book using Docker V1.12 and above. I am taking advantage of the embedded DNS server in Docker that came out in release V1.11. New Docker releases are constantly coming out so it's release version you are using may change on a regular basis.
- Git Client (http://git-scm.com). All of the source code for this book is stored in a GitHub repository. For the book, I used version 2.8.4 of the git client.
To build the code examples for Chapter 4 as a docker image, open a command-line window change to the directory where you have downloaded the chapter 4 source code.
Run the following gradle command. This command will execute the Gradle Docker plugin defined in the build.gradle file.
./gradlew clean buildImage
This is the first chapter we will have multiple Spring projects that need to be be built and compiled. Running the above command at the root of the project directory will build all of the projects. If everything builds successfully you should see a message indicating that the build was successful.
Now we are going to use docker-compose to start the actual image. To start the docker image, change to the directory containing your chapter 3 source code. Issue the following docker-compose command:
docker-compose -f docker/common/docker-compose.yml up
If everything starts correctly you should see a bunch of Spring Boot information fly by on standard out. At this point all of the services needed for the chapter code examples will be running.