skills.rest
TheViziusGroup
TheViziusGroupOFFICIAL
Explore all skills by this author →
WebsiteGitHub

architecture-patterns

Recommends Azure architecture patterns for compute, data, messaging, resilience, and AI workloads.

1|Updated Aug 10, 2026
Search Tags:#microservices#rag#azure#resilience#event-driven#architecture patterns#cloud design
One-click install
npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill architecture-patterns-theviziusgroup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-patterns
Source: https://github.com/TheViziusGroup/vibe-engineering-skills/tree/main/plugins/software-architecture/skills/architecture-patterns
Command: npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill architecture-patterns-theviziusgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing the wrong architecture pattern or Azure service leads to costly re-platforming, especially for irreversible decisions like Cosmos DB partition keys, event schemas, and multi-tenancy isolation models. This Skill provides a decision-oriented reference that maps architecture patterns to concrete Azure implementations with production gotchas and migration deadlines. ## Core Features & Use Cases - Pattern-to-Azure Mapping: Covers compute (monolith, microservices, serverless, EDA), communication (REST, gRPC, GraphQL, messaging), data (relational, Cosmos DB, vector search, lakehouse), resilience (retry, circuit breaker, saga, outbox), security (Zero Trust, IAM, encryption), and AI/ML (RAG, AI gateway, agents). - Decision Frameworks: Provides decision ladders and matrices, such as App Service to Container Apps to AKS, and load balancer selection across L4, L7, and global DNS options. - Production Gotchas & Deadlines: Flags real constraints like Flex Consumption subnet rules, Istio add-on CNI incompatibility, and retirements such as Prompt Flow (April 2027) and Front Door classic (March 2027). - Use Case: When designing a new microservices system on Azure, use this Skill to decide between Container Apps and AKS, select Service Bus versus Event Hubs versus Event Grid, and apply the outbox pattern to avoid dual-write inconsistencies. ## Quick Start Ask the assistant to recommend an Azure architecture for your workload, for example: help me choose between Azure Container Apps and AKS for a microservices application with event-driven processing.

Frequently Asked Questions about architecture-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between Azure Container Apps and AKS for microservices?▼

Azure Container Apps is the recommended default for most microservices, offering KEDA autoscaling and Dapr without cluster management. Choose AKS only when you need the full Kubernetes API, custom operators, a service mesh, or fine-grained node and GPU control.

What is the difference between Service Bus, Event Grid, and Event Hubs?▼

Service Bus handles enterprise queues with ordering, transactions, and dead-lettering. Event Grid provides reactive pub/sub including MQTT broker capabilities. Event Hubs is for high-throughput streaming with a Kafka-compatible endpoint. Most event-driven architectures use all three together.

Why is the Cosmos DB partition key decision so critical?▼

The partition key cannot be changed in place after container creation; a poor choice causes hot partitions and throttling regardless of provisioned RUs. Fixing it requires migrating data to a new container, making it one of the most irreversible architecture decisions.

Does the AKS Istio service mesh add-on work with all network configurations?▼

No. The Istio add-on does not work on clusters using Azure CNI Powered by Cilium, alongside the deprecated OSM add-on, or with self-managed Istio. It also blocks several CRDs including EnvoyFilter and WasmPlugin, and does not yet support Ambient mode.

When should I use the outbox pattern in event-driven architecture?▼

Use the outbox pattern whenever you publish events from a database write. It writes the business change and the event in one local transaction, then relays to the broker, solving the dual-write problem where independent writes can leave systems inconsistent.

What Azure services are recommended for RAG retrieval?▼

Azure AI Search with hybrid BM25 plus vector search and the semantic ranker is Microsoft's recommended retrieval stack for most scenarios. Alternatively, co-locate vectors in Cosmos DB (DiskANN), Azure SQL (native VECTOR type), or PostgreSQL with pgvector to avoid a separate service.

Related Skills

Explore More Software Engineering Skills→
manu14357manu14357
16

azure-compute

Select the appropriate Azure compute service for a workload.

Community
Advanced
404kidwiz404kidwiz

azure-infra-engineer

Automates Azure infrastructure provisioning using Bicep/ARM templates and Hub-and-Spoke networks.

Community
Advanced
aws-samplesaws-samples
12

aws-plan

Plan AWS architecture workflows from discovery through delivery.

Official
Advanced
JhabbigJhabbig

multi-cloud-architecture

Design multi-cloud architectures across AWS, Azure, GCP, and OCI.

Community
Intermediate