Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Spring 5.0 By Example

You're reading from   Spring 5.0 By Example Grasp the fundamentals of Spring 5.0 to build modern, robust, and scalable Java applications

Arrow left icon
Product type Paperback
Published in Feb 2018
Publisher Packt
ISBN-13 9781788624398
Length 356 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
 de Oliveira de Oliveira
Author Profile Icon de Oliveira
de Oliveira
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Title Page
Copyright and Credits
Dedication
Packt Upsell
Contributors
Preface
1. Journey to the Spring World FREE CHAPTER 2. Starting in the Spring World – the CMS Application 3. Persistence with Spring Data and Reactive Fashion 4. Kotlin Basics and Spring Data Redis 5. Reactive Web Clients 6. Playing with Server-Sent Events 7. Airline Ticket System 8. Circuit Breakers and Security 9. Putting It All Together 1. Other Books You May Enjoy Index

The docker-compose tool


In the microservices architectural style, the whole solution is decoupled in small and well-defined services. Usually, when we adopt these styles, we have more than one artifact to deploy.

Let's analyze our solution; we have three components to deploy. We have used the Docker containers and we have run these containers using the docker run command. One by one, we have used docker run three times. It is quite complex and very hard to do in the development routine.

docker-compose can help us in this scenario. It is a tool which helps to orchestrate Docker containers in complex scenarios like ours.

Let's imagine our application is growing fast and we need to build four more microservices to achieve the desired business case, it will implicate on four more docker run commands and will probably be painful to maintain, especially during the development life cycle. Sometimes, we need to promote the artifacts to test the environment and we probably need to modify our command...

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 £13.99/month. Cancel anytime
Visually different images