Chapter 1. Welcome to the cloud, Spring
Figure 1.1. Monolithic applications force multiple development teams to artificially synchronize their delivery because their code needs to be built, tested, and deployed as an entire unit.
Figure 1.2. Using a microservice architecture our CRM application would be decomposed into a set of microservices completely independent of each other, allowing each development team to move at their own pace.
Figure 1.3. Spring Boot abstracts away the common REST microservice task (routing to business logic, parsing HTTP parameters from the URL, mapping JSON to/from Java Objects), and lets the developer focus on the business logic for the service.
Figure 1.4. Your Spring Boot service will communicate the endpoints exposed and the port of the service via the console.
Figure 1.5. The response from the /hello endpoint shows the data you’ve requested represented as a JSON payload.
Figure 1.6. The different cloud computing models come down to who’s responsible for what: the cloud vendor or you.
Figure 1.7. Microservices are more than the business logic. You need to think about the environment where the services are going to run and how the services will scale and be resilient.
Figure 1.8. When designing your microservice, you have to think about how the service will be consumed and communicated with.
Figure 1.9. Service discovery and routing are key parts of any large-scale microservice application.