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

Building a messaging system


I think that the most suitable way to introduce main Spring Cloud Stream features is through the sample microservices-based system. We will lightly modify an architecture of the system that has been discussed in the previous chapters. Let me provide a short recall of that architecture. Our system is responsible for processing orders. It consists of four independent microservices. The order-service microservice first communicates with product-service in order to collect the details of the selected products, and then with customer-service to retrieve information about the customer and his accounts. Now, the orders sent to order-service will be processed asynchronously. There is still an exposed RESTful HTTP API endpoint for submitting new orders by the clients, but they are not processed by the application. It only saves new orders, sends it to a message broker, and then responds to the client that the order has been approved for processing. The main goal of the...

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