<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Architecture on Technology Enlightened</title>
    <link>https://pprakash.me/tags/architecture/</link>
    <description>Recent content in Architecture on Technology Enlightened</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>&amp;copy; &lt;a href=&#34;https://github.com/p-prakash/&#34;&gt;Prakash P&lt;/a&gt; 2015 - 2023</copyright>
    <lastBuildDate>Fri, 31 Jul 2026 16:00:00 +0100</lastBuildDate>
    <atom:link href="https://pprakash.me/tags/architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Multi-region high availability for Azure Content Understanding</title>
      <link>https://pprakash.me/tech/2026/07/31/multi-region-ha-azure-content-understanding/</link>
      <pubDate>Fri, 31 Jul 2026 16:00:00 +0100</pubDate>
      <guid>https://pprakash.me/tech/2026/07/31/multi-region-ha-azure-content-understanding/</guid>
      <description>&lt;p&gt;Azure Content Understanding and Azure OpenAI Service are regional services. A production document-processing workflow often cannot treat a regional endpoint, its model deployments, or its analyzer definitions as a single point of failure. In this post, we discuss a highly available solution built across multiple regions to handle regional failures.&lt;/p&gt;&#xA;&lt;h2 id=&#34;architecture&#34;&gt;Architecture&lt;/h2&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://pprakash.me/images/2026/07/azure-content-understanding-multi-region-ha.png&#34; alt=&#34;Architecture diagram of implemented regional stacks and cross-region flows&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;Figure 1. Implemented regional stacks and cross-region flows.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;The diagram shows two distinct planes: solid lines represent synchronous request traffic, while dashed lines represent asynchronous analyzer reconciliation. This separation addresses two related resilience challenges: routing requests to a healthy Content Understanding backend and keeping analyzer configurations consistent across regions. API Management selects a local-first backend synchronously within each available gateway, while two queue-driven Azure Functions synchronize analyzers asynchronously.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Scale Azure Databricks secure network access to Azure Data Lake Storage</title>
      <link>https://pprakash.me/tech/2023/12/11/scale-azure-databricks-secure-network-access-to-azure-data-lake/</link>
      <pubDate>Mon, 11 Dec 2023 18:00:00 +0100</pubDate>
      <guid>https://pprakash.me/tech/2023/12/11/scale-azure-databricks-secure-network-access-to-azure-data-lake/</guid>
      <description>&lt;p&gt;Many organisations store their data in a centralised data lake on Azure Storage accounts. In this post we will look at a solution to scale the secure network access between the centralised data lake storage account and Azure Databricks workspaces VNets.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://pprakash.me/images/2023/12/Databricks_Network_Design.png&#34; alt=&#34;Architecture diagram of having storage account with Private Endpoint connected to Azure Databricks workspaces VNets&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;The recommended approach to achieve a scalable and secure network access to the data lake storage is to use Private Endpoints for the storage accounts.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
