Spring Cloud Zipkin server and Sleuth
Our solution involves some microservices; it makes our solution easy to deploy and easy to write code. Each solution has a particular repository and codebase.
In the monolith solution, the whole problem is solved in the same artifact to be deployed. Usually, in Java, these artifacts are .jar, .war, or .ear, if the application was written in the Java EE 5/6 specifications.
The logging strategies for these kinds of applications is quite easy to work with (hence problems can be solved easily) because everything happens in the same context; the requests are received from the same application server or web server, which have the business components. Now, if we go to the logs, we will probably find the log entries we want. It makes the trace application easier to find errors and debug.
In the microservices solution, the application behaviors are split in the distributed systems; it increases the trace tasks substantially because the request probably arrives...
