<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Csharp on Rylee George</title>
    <link>https://ryleeg.com/tags/csharp/</link>
    <description>Recent content in Csharp on Rylee George</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 31 Jul 2026 00:00:00 +1000</lastBuildDate>
    <atom:link href="https://ryleeg.com/tags/csharp/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building a Virtual Power Plant with Microsoft Orleans - Part 1 Architecture &amp; Data Model</title>
      <link>https://ryleeg.com/posts/building-vpp-part-1/</link>
      <pubDate>Fri, 31 Jul 2026 00:00:00 +1000</pubDate>
      <guid>https://ryleeg.com/posts/building-vpp-part-1/</guid>
      <description>&lt;p&gt;&lt;strong&gt;How the virtual actor model maps perfectly to managing thousands of distributed energy resources&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;A Virtual Power Plant is a geographically dispersed energy assets solar panels, batteries, EV chargers, heat pumps orchestrated through a single Command And Control software to behave like a single power plant.&lt;/p&gt;&#xA;&lt;p&gt;But here&amp;rsquo;s the engineering problem: each asset has its own identity, its own state, its own schedule, and its own hardware communication protocol. Sarah&amp;rsquo;s Tesla Powerwall should never stop charging her EV because Bob&amp;rsquo;s SolarEdge battery in a different suburb received a conflicting dispatch command. The software must manage state for hundreds or thousands of assets, independently, concurrently, and without data loss during failures.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
