--- title: "Platform architecture | Dhruv Doshi" description: "Paved roads, decision models, reusable contracts, governance, and enterprise platform delivery." canonical: https://doshidhruv.com/topics/platform-architecture/ author: Dhruv Doshi --- [Skip to content](#main-content) [Dhruv Doshi](/) [Work](/projects)[Experience](/resume)[Notes](/notes)[Guides](/guides)[Research](/research)[About](/about)[Contact](/contact)[Search /](/search)dark mode # Platform architecture Paved roads, decision models, reusable contracts, governance, and enterprise platform delivery. - [Platform architecture: from standards to a usable product](/guides/platform-architecture) · Guide · A practical guide to turning architecture standards into paved roads, reusable contracts, and measurable platform outcomes. - [Observability systems: design the telemetry path before the dashboard](/guides/observability-systems) · Guide · A systems guide to telemetry contracts, collection, routing, storage boundaries, and operational feedback at scale. - [Cloud migration: sequence decisions, not just workloads](/guides/cloud-migration) · Guide · A practical guide to cloud migration boundaries, dependency mapping, landing zones, observability, cutovers, and exit criteria. - [Staff engineering practice: create leverage through clear systems](/guides/staff-engineering-practice) · Guide · A practical guide to technical direction, decision records, cross-team delivery, mentoring, and operational credibility. - [Architecture Solution Blueprint platform](/projects#architecture-blueprints) · Project · Designed and led the zero-to-one delivery of an enterprise platform that turns 1,000+ architecture patterns into real-time service recommendations, solution blueprints, and automated architecture workflows. - [Vendor-neutral observability platform](/projects#observability-platform) · Project · Architected a vendor-neutral OpenTelemetry and telemetry-routing platform designed for approximately 150 TB/day across 10,000+ systems, enabling governed collection and routing without coupling teams to a single observability vendor. - [ASB Assist](/projects#asb-assist) · Project · Building an LLM and RAG architecture assistant that turns natural-language requirements into architecture recommendations and diagrams using retrieval, tool integration, evaluation, grounding controls, guardrails, and auditable workflows. - [Healthcare verification platform](/projects#health-platform) · Project · Joined as the first engineer and built the platform across React and TypeScript, Node.js APIs, verification workflows, document-classification integration, and AWS EKS in a regulated healthcare environment. - [Staff Software Developer & Enterprise Architect — Royal Bank of Canada](/resume#experience-royal-bank-of-canada) · Experience · Building enterprise platforms and standards across architecture automation, observability, cloud infrastructure, and responsible AI. - [Blockchain Architect & First Full Stack Engineer — HealthCard](/resume#experience-healthcard) · Experience · Built the acquired startup’s initial product and cloud architecture across frontend, APIs, verification, and deployment. - [IT Developer / Software Developer Co-op — Canada Revenue Agency](/resume#experience-canada-revenue-agency) · Experience · Modernised federal tax-platform interfaces and contributed to accessible digital services used by Canadians. - [Teaching Assistant & Research Assistant — Dalhousie University](/resume#experience-dalhousie-university) · Experience · Supported software development, algorithms, and graduate cloud-computing courses while researching call-stack decision algorithms. - [Blockchain Developer — CryptoVantage](/resume#experience-cryptovantage) · Experience · Built on-chain event processing and wallet-risk analysis for anti-money-laundering workflows. - [Measure whether an internal platform creates leverage](/notes/measure-whether-an-internal-platform-creates-leverage) · Note · An internal platform can look successful while moving work from one team to another. Repository count, portal visits, and cluster utilisation show activity, but they do not prove that… - [Pattern matching algorithms for architecture recommendations](/notes/pattern-matching-algorithms-for-architecture-recommendations) · Note · An architecture recommendation platform must translate incomplete requirements into a small set of compatible patterns and services while explaining why each result fits. This is not… - [FINOS CALM and architecture as code](/notes/finos-calm-and-architecture-as-code) · Note · Architecture diagrams are useful for communication, but a diagram alone is difficult to validate, compare, or connect to delivery controls. The Common Architecture Language… - [Architecture governance should operate through evidence](/notes/architecture-governance-should-operate-through-evidence) · Note · Architecture governance is useful when it improves decisions and makes system risk visible. It becomes harmful when every change waits for a central meeting that lacks the context to… - [Treat Terraform modules as versioned interfaces](/notes/treat-terraform-modules-as-versioned-interfaces) · Note · A reusable Terraform module is an internal product interface. Its inputs, outputs, defaults, provider constraints, state behavior, and upgrade path affect every stack that consumes it.… - [Manage secrets without creating secret sprawl](/notes/manage-secrets-without-creating-secret-sprawl) · Note · Secret management is not solved by moving passwords from source code into a central vault. The larger goal is to reduce the number, lifetime, reach, and human handling of credentials… - [Zero Trust begins with service identity](/notes/zero-trust-begins-with-service-identity) · Note · Network location is a weak security identity. A request originating inside a cluster, virtual network, or corporate boundary is not automatically trustworthy. A Zero Trust design… - [Design the platform as a product](/notes/design-the-platform-as-a-product) · Note · An internal platform is successful when product teams choose it because it removes work, not because governance forces them to use it. That changes the architecture question from “what… **Dhruv Doshi** · Toronto, Canada · [work@doshidhruv.com](mailto:work@doshidhruv.com) [Resume](/resume)[Notes](/notes)[Guides](/guides)[Topics](/topics)[Search](/search)[Research](/research)[LinkedIn](https://www.linkedin.com/in/dhruvdoshi25071999)[GitHub](https://github.com/DhruvDoshi) [Sitemap](/sitemap.xml)[RSS](/feed.xml)[LLMs](/llms.txt) © 2026 Dhruv Doshi