Abstract
We completed the previous chapter with a pending task: finishing user story 3 and letting our users see their progress in the game. The reason is that, in order to build a good microservices architecture, we need the UI part of the system extracted in a new service so it can interact as an independent party with our multiplication and gamification services. We’ll cover the reasoning with more detail in the next section.
Keywords
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsNotes
- 1.
You could also choose Tomcat for consistency with the Spring Boot microservices but, in this case, I picked Jetty since it’s really easy to explain how to download and configure it in the book.
- 2.
Note that it might take some seconds before both instances are registered in Eureka and the load balancer initiates the round-robin strategy. Be patient!
- 3.
- 4.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2017 Moises Macero
About this chapter
Cite this chapter
Macero, M. (2017). The Microservices Journey Through Tools. In: Learn Microservices with Spring Boot. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-3165-4_5
Download citation
DOI: https://doi.org/10.1007/978-1-4842-3165-4_5
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-3164-7
Online ISBN: 978-1-4842-3165-4
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books