This is an example app where two Spring Boot (Java) services collaborate on an http request. Notably, timing of these requests are recorded into Zipkin, a distributed tracing system. This allows you to see the how long the whole operation took, as well how much time was spent in each service.
Here's an example of what it looks like
This example was initially made for a Distributed Tracing Webinar on June 30th, 2016. There's probably room to enroll if it hasn't completed, yet, and you are interested in the general topic.
Web requests are served by Spring MVC controllers, and tracing is automatically performed for you by Spring Cloud Sleuth.
This example intentionally avoids advanced topics like async and load balancing, eventhough Spring Cloud Sleuth supports that, too. Once you get familiar with things, you can play with more interesting Spring Cloud components.
This example has two services: frontend and backend. They both report trace data to zipkin. To setup the demo, you need to start Frontend, Backend and Zipkin.
Once the services are started, open http://localhost:8081/
- This will call the backend (http://localhost:9000/api) and show the result, which defaults to a formatted date.
Next, you can view traces that went through the backend via http://localhost:9411/?serviceName=backend
- This is a locally run zipkin service which keeps traces in memory
In a separate tab or window, start each of sleuth.webmvc.Frontend and sleuth.webmvc.Backend:
$ ./mvnw exec:java -Dexec.mainClass=sleuth.webmvc.Frontend
$ ./mvnw exec:java -Dexec.mainClass=sleuth.webmvc.BackendNext, run Zipkin, which stores and queries traces reported by the above services.
wget -O zipkin.jar 'https://search.maven.org/remote_content?g=io.zipkin.java&a=zipkin-server&v=LATEST&c=exec'
java -jar zipkin.jar