Skip to content

Latest commit

 

History

History
71 lines (41 loc) · 3.74 KB

README.md

File metadata and controls

71 lines (41 loc) · 3.74 KB
Raw

09 - Putting it all together, a complete microservice stack

This guide is part of the Azure Spring Apps training

Now that we have made two microservices publicly available, we will incorporate a user interface to see them in action. Then, we will use Azure Monitor to monitor the flow of traffic to and among our services and to track metrics.

Add a front-end to the microservices stack

We now have a complete microservices stack:

  • A gateway based on Spring Cloud Gateway.
  • A reactive city-service microservice, that stores its data in Azure Cosmos DB.
  • A weather-service microservice, that stores its data in MySQL

In order to finish this architecture, we need to add a front-end to it:

  • We've already built a VueJS application, that is available in the "weather-app" folder.
  • This front-end could be hosted in Azure Spring Apps, using the same domain name (this won't be the case in this guide, and that's why we enabled CORS in our gateway earlier).
  • If you are familiar with NodeJS and Vue CLI, you can run this application locally by typing npm install && vue ui.

In order to simplify this part, which is not relevant to understanding Spring Cloud, we have already built a running front-end:

https://spring-training.azureedge.net/

For your information, this website is hosted on Azure Storage and served through Azure CDN for optimum performance.

Go to https://spring-training.azureedge.net/, input your Spring Cloud Gateway's public URL in the text field and click on "Go". You should see the following screen:

VueJS front-end

Review the distributed tracing to better understand the architecture

Distributed tracing is enabled by default on Azure Spring Apps, so your microservices and gateway are already being monitored.

Now, you can use the VueJS application on https://spring-training.azureedge.net/ to generate some traffic on the microservices stack.

💡 Tracing data can take a couple of minutes to be ingested by the system, so use this time to generate some load.

In the "Application Insights" menu in Azure Portal, you should now have access to a full application map, as well as a search engine that allows you to find performance bottlenecks.

Distributed tracing

💡 If your application map looks different from the one above, select the hierarchical view from the layout switch in the top-right corner:

layout switch

Review the performance metrics

Open a more holistic view at the Performance blade where you can see response times and request counts for operations exposed by your applications.

Trace detail

For even more detailed data, navigate to the Dependencies tab in the Performance blade where you can see all your dependencies and their response times and request counts.

Scale applications

Now that distributed tracing is enabled, we can scale applications depending on our needs.

  • Go to the Azure portal.
  • Go to the overview page of your Azure Spring Apps server and select "Apps" in the menu.
    • Select one service and click on "Scale Out" in the menu. Select the service that you want to scale out.
    • Modify the number of instances to manually scale the service. You can also set custom autoscaling based on metrics. Application scaling

⬅️ Previous guide: 08 - Build a Spring Cloud Gateway

➡️ Next guide: 10 - Blue/Green deployment