<?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>Microservices on blog.ehn.nu</title><link>https://blog.ehn.nu/categories/microservices/</link><description>Recent content in Microservices on blog.ehn.nu</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 23 Mar 2020 19:27:11 +0000</lastBuildDate><atom:link href="https://blog.ehn.nu/categories/microservices/index.xml" rel="self" type="application/rss+xml"/><item><title>Debugging Dapr applications with Visual Studio Code</title><link>https://blog.ehn.nu/2020/03/debugging-dapr-applications-with-visual-studio-code/</link><pubDate>Mon, 23 Mar 2020 19:27:11 +0000</pubDate><guid>https://blog.ehn.nu/2020/03/debugging-dapr-applications-with-visual-studio-code/</guid><description>&lt;p&gt;I’ve been playing around with the &lt;a href="https://dapr.io/"&gt;Dapr&lt;/a&gt; project recently, which is an interesting approach to building distributed, “microservices” applications. Tha main idea with Dapr is to make it easier for developers to implement distributed application running either in the cloud or on “the edge” (e.g. anywhere else), by implementing a lot of the cross-cutting concerns that is a part of every distributed app. Dapr consists of a number of building blocks, such as Service Invocation, State Service, Pub/Sub messaging and distributed tracing.&lt;/p&gt;</description></item></channel></rss>