Chapter 1. An introduction to microservices
Figure 1.1. Scaling a monolithic application
Figure 1.2. Scaling a microservice independently of the main application
Figure 1.3. Each service is part of the big picture.
Figure 1.4. Each microservice is still part of the picture but is isolated within a separate environment.
Figure 1.5. Each service communicates by defined protocols.
Figure 1.6. Resilient design using circuit breakers
Figure 1.7. The basic microservice components
Figure 1.8. The resource component publicly exposes the service.
Figure 1.9. The business-domain component is your service’s business logic.
Figure 1.10. The remote resources component is the gateway to other services.
Figure 1.11. The persistence component is for data storage.
Figure 1.12. Predominantly solitary unit-test components
Figure 1.13. Predominantly sociable unit-test component
Chapter 2. Application under test
Figure 2.1. Gamer application schema
Figure 2.2. Gamer application entity relationship
Figure 2.3. Game service overview
Figure 2.4. Collection of comments
Figure 2.5. Comments service overview
Figure 2.6. Video URLs cached in Redis
Figure 2.7. Video service
Figure 2.8. Game aggregator service relations to other services
Figure 2.9. Architecture diagram of our project
Figure 2.10. Detailed microservice structure
Figure 2.11. ECB pattern
Figure 2.12. Example of the ECB pattern applied to Gamer microservices
Figure 2.13. Aggregator pattern
Chapter 3. Unit-testing microservices