<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Irina Scurtu on Blog</title><link>https://blog.djvelimir.com/tags/irina-scurtu/</link><description>Recent content in Irina Scurtu on Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 18 Sep 2026 18:08:57 +0200</lastBuildDate><atom:link href="https://blog.djvelimir.com/tags/irina-scurtu/index.xml" rel="self" type="application/rss+xml"/><item><title>.NET gRPC - deep dive</title><link>https://blog.djvelimir.com/post/conferences/dotnet-grpc---deep-dive---irina-scurtu---ndc-london-2024/</link><pubDate>Fri, 18 Sep 2026 18:08:57 +0200</pubDate><guid>https://blog.djvelimir.com/post/conferences/dotnet-grpc---deep-dive---irina-scurtu---ndc-london-2024/</guid><description>&lt;p&gt;With an increasing need for scalability and performance dictated by the modern web, it becomes harder and harder to choose an API paradigm that is suitable for service-to-service communication.&lt;/p&gt;
&lt;p&gt;While the classical models still work and have their own merits, some of them rely heavily on documentation, extensive coordination between teams or code-sharing. We use shared libraries, and over time our projects become intertwined with dependencies. In these cases, we need something to untangle those and reduce coupling. Welcome gRPC.&lt;/p&gt;</description></item></channel></rss>