<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Zipkin Java Tracing on Roger Welin</title><link>https://rogerwelin.github.io/categories/zipkin-java-tracing/</link><description>Recent content in Zipkin Java Tracing on Roger Welin</description><generator>Hugo -- 0.155.0</generator><language>en-us</language><lastBuildDate>Sun, 06 Aug 2017 11:40:43 +0000</lastBuildDate><atom:link href="https://rogerwelin.github.io/categories/zipkin-java-tracing/feed.xml" rel="self" type="application/rss+xml"/><item><title>Distributed tracing with Zipkin and springcloud-sleuth</title><link>https://rogerwelin.github.io/2017/08/06/distributed-tracing-with-zipkin-and-springcloud-sleuth/</link><pubDate>Sun, 06 Aug 2017 11:40:43 +0000</pubDate><guid>https://rogerwelin.github.io/2017/08/06/distributed-tracing-with-zipkin-and-springcloud-sleuth/</guid><description>&lt;p&gt;Microservice architecture is a common architecture pattern that favors small services that&amp;rsquo;s independantly deployable which communicates with each other most often with a HTTP api.
This architecture pattern has been very popular in our industry and is heavily favoured in opposition to build big monolithic systems that are hard to develop in cooperation and deploy. However the microservice architecture pattern does come with some downsides - it&amp;rsquo;s a lot harder to understand the communication model, i.e which services is comminicating with which service. And it&amp;rsquo;s a lot harder and daunting to find out exactly where in the chain latency is introduced.&lt;/p&gt;</description></item></channel></rss>