メニュー
Decision framework for selecting the right Azure hosting platform (App Service, AKS, Container Apps) based on application characteristics. Use when helping users choose a hosting platform or comparing Azure compute options.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Analyzes legacy .NET Framework applications (WinForms, WebForms, MVC, WCF) for migration readiness. Use when analyzing C# code structure, identifying framework-specific patterns, extracting business logic, or understanding legacy .NET architectures.
Provides patterns and guidance for migrating .NET Framework applications to .NET 8+. Use when performing framework upgrades, converting WCF to REST, modernizing authentication, or transforming configuration files.
Analyzes legacy Java applications (Java EE, Servlets, JSP, EJB, Spring) for migration readiness. Use when analyzing Java code structure, identifying framework-specific patterns, or understanding legacy Java architectures.
Analyzes SQL Server stored procedures to extract business logic, map data flows, and document dependencies. Use when reverse-engineering stored procedure business rules, analyzing SP call chains, or documenting database-layer business logic.
| name | azure-hosting-selection |
| description | Decision framework for selecting the right Azure hosting platform (App Service, AKS, Container Apps) based on application characteristics. Use when helping users choose a hosting platform or comparing Azure compute options. |
Provide a structured decision framework for selecting the optimal Azure hosting platform based on application type, complexity, team capabilities, and operational requirements.
| Factor | App Service | Container Apps | AKS |
|---|---|---|---|
| Complexity | Low | Medium | High |
| Best for | Web apps, APIs | Microservices, event-driven | Complex distributed systems |
| Scaling | Built-in auto-scale | Event-driven auto-scale (KEDA) | Full Kubernetes HPA/VPA |
| Container required | No (code deploy) | Yes | Yes |
| Custom networking | Limited | Moderate | Full control |
| Ops overhead | Minimal | Low-Medium | High |
| Cost | Predictable (plan-based) | Pay-per-use | Cluster + node costs |
| CI/CD | Built-in deployment slots | Revisions-based | Helm/Kubectl/GitOps |
| Team skill needed | Web dev | Containers + basics | Kubernetes expertise |
Is the app a simple web app or API?
├── YES → Do you need custom containers?
│ ├── NO → Azure App Service ✅
│ └── YES → Azure Container Apps ✅
└── NO → Is it a microservices architecture?
├── YES → Do you need full Kubernetes control?
│ ├── YES → AKS ✅
│ └── NO → Azure Container Apps ✅
└── NO → Is it a background/batch workload?
├── YES → Azure Container Apps (scale to zero) ✅
└── NO → Azure App Service ✅
| Tier | App Service | Container Apps | AKS |
|---|---|---|---|
| Dev/Test | Free/Basic tier | Pay only for usage | Dev/test node pool |
| Production (small) | Standard S1 ~$75/mo | ~$50-150/mo variable | ~$200+/mo (min cluster) |
| Production (large) | Premium P1V3 ~$150/mo | Scales with demand | Scales with nodes |