Azure SaaS Workflow Architecture Plan
Budget: ₹12,500 – ₹37,500 INR
I’m putting together a comprehensive system-level architecture for a new SaaS platform that runs entirely in Microsoft Azure. The core objective is to design a rock-solid data-processing workflow that ties ingestion, transformation, and—most critically—data storage into a seamless, highly scalable pipeline.
Here’s what I need from you:
• A clear, vendor-agnostic architecture diagram that shows every Azure service you recommend—whether that’s Event Hubs, Service Bus, Data Factory, Functions, AKS, or native PaaS options.
• A storage strategy that explains where structured, semi-structured, and unstructured data will live (e.g., Azure SQL Database, Cosmos DB, Blob Storage, Data Lake), how data will be partitioned, encrypted, and lifecycle-managed, and what patterns you’ll employ for high availability and disaster recovery.
• Written rationale for each decision, covering performance targets, cost optimisation, and operational monitoring with Azure Monitor or other tooling.
• A brief roadmap outlining deployment steps and how the design can evolve as load grows.
Because the major emphasis is on data storage, your plan should dive deep into schema design, indexing, retention-policy enforcement, and how the storage layer plugs into the wider workflow.
I value proven hands-on experience above all else—especially if you hold a current Microsoft Azure Solutions Architect certification. Point me to past architecture work of similar scale, say how many tenants or daily transactions you designed for, and highlight any trade-offs you navigated.
I’m ready to move quickly once I see the right expertise, so feel free to outline the high-level approach you’d take in your first reply.
Here’s what I need from you:
• A clear, vendor-agnostic architecture diagram that shows every Azure service you recommend—whether that’s Event Hubs, Service Bus, Data Factory, Functions, AKS, or native PaaS options.
• A storage strategy that explains where structured, semi-structured, and unstructured data will live (e.g., Azure SQL Database, Cosmos DB, Blob Storage, Data Lake), how data will be partitioned, encrypted, and lifecycle-managed, and what patterns you’ll employ for high availability and disaster recovery.
• Written rationale for each decision, covering performance targets, cost optimisation, and operational monitoring with Azure Monitor or other tooling.
• A brief roadmap outlining deployment steps and how the design can evolve as load grows.
Because the major emphasis is on data storage, your plan should dive deep into schema design, indexing, retention-policy enforcement, and how the storage layer plugs into the wider workflow.
I value proven hands-on experience above all else—especially if you hold a current Microsoft Azure Solutions Architect certification. Point me to past architecture work of similar scale, say how many tenants or daily transactions you designed for, and highlight any trade-offs you navigated.
I’m ready to move quickly once I see the right expertise, so feel free to outline the high-level approach you’d take in your first reply.