Claude Prompt for App Architecture
Evaluate Swift + Vapor for building a healthcare patient portal in the pharmaceuticals space with pros, cons, and alternatives.
More prompts for App Architecture.
Generate a comprehensive system design document covering architecture, data flow, scalability, and deployment strategy.
Design a complete serverless architecture on AWS Lambda, Vercel, or Cloudflare Workers with infrastructure-as-code.
Design a multi-layer caching architecture with cache invalidation, TTL policies, and consistency guarantees.
Design a complete database schema and data strategy for a analytics dashboard serving the parenting industry.
Design a RESTful or GraphQL API for a restaurant ordering system using SQL with best practices and documentation.
Design a complete system architecture for a healthcare patient portal built with Django + PostgreSQL for real-estate.
You are a senior solutions architect analyst. Your job is to provide data-driven insights and actionable recommendations for technology evaluation. Evaluate **Swift + Vapor** as the tech stack for building a healthcare patient portal in the pharmaceuticals industry. **Proposed stack:** Swift + Vapor **Application type:** healthcare patient portal **Industry:** pharmaceuticals **Team experience:** full-stack generalists ## Stack Component Analysis Break down each technology in the Swift + Vapor stack: - What role it plays in the architecture - Maturity level and community size - Learning curve for full-stack generalists developers - Long-term maintenance and support outlook ## Strengths for This Use Case - 5 specific advantages of Swift + Vapor for building a healthcare patient portal - Performance characteristics relevant to pharmaceuticals workloads - Developer experience and productivity benefits - Ecosystem of libraries, tools, and integrations available ## Weaknesses and Risks - 5 potential pain points or limitations - Scalability concerns specific to a healthcare patient portal - Hiring difficulty for Swift + Vapor developers - Vendor lock-in or technology obsolescence risks ## Alternative Stack Comparison Compare Swift + Vapor against 2 alternative stacks: For each alternative, evaluate: - Development speed (time to MVP) - Performance at scale - Operational complexity - Cost (hosting, licensing, developer salaries) - Community and ecosystem - Rate each category on a 1-5 scale ## Recommended Architecture with This Stack - High-level component diagram (text-based) - Key architectural decisions specific to Swift + Vapor - Recommended hosting and deployment approach - Estimated infrastructure costs at 3 scale points ## Decision Framework - Summarize the go/no-go criteria - Under what conditions is Swift + Vapor the best choice - Under what conditions should you choose an alternative - Final recommendation with confidence level (high/medium/low) Structure as a professional report with: Executive Summary, Key Findings, Detailed Analysis, Recommendations, and Next Steps.