compute

Compare serverless, container, VM, and edge platforms for application workloads.

3|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/mauriciodelrio/delriodev-skills --skill compute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compute
Source: https://github.com/mauriciodelrio/delriodev-skills/tree/main/es-skills/software/architecture/compute
Command: npx skills add https://github.com/mauriciodelrio/delriodev-skills --skill compute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams decide where to run code by comparing serverless functions, container tasks, virtual machines, and edge functions against workload needs, cost, latency, and operational constraints.

Core Features & Use Cases

  • Decision trees for frontend/SSR, APIs, and background workers to pick between AWS Lambda, ECS Fargate, EC2, and Vercel Functions/Edge.
  • Platform guidance with limits, cost estimates, and when to prefer each option (e.g., stateless short jobs → Lambda; long-running or persistent connections → Fargate/EC2).
  • Deployment patterns and CI/CD recommendations for common flows (Serverless Framework/SST, Docker → ECR → ECS, Vercel deploys).
  • Operational tradeoffs & gotchas including cold starts, VPC impacts, timeouts, and cost floors to inform architecture decisions.

Quick Start

Ask the compute skill to evaluate a specific workload by describing its type (frontend/API/worker), expected latency, execution duration, concurrency, budget, and compliance constraints.

Frequently Asked Questions about compute

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

FAQPage Schema
How do I choose the best compute platform for my application workload?

To choose the best compute platform, evaluate your workload type, execution duration, concurrency, and budget against serverless, container, VM, and edge options to match operational constraints and scale requirements.

When should I use AWS Lambda versus ECS Fargate or EC2 for my API?

Use AWS Lambda for stateless short jobs, while ECS Fargate or EC2 is better for long-running processes or persistent connections. Evaluate execution duration, cold start tolerance, and VPC access to decide.

What are the operational tradeoffs and gotchas of serverless functions versus containers?

Serverless functions tradeoffs include cold starts, VPC impacts, timeouts, and cost floors, whereas containers offer more control but require deployment management. Compare these limits against your scale and latency constraints.

How do I deploy serverless functions and container tasks using CI/CD?

Deploy serverless functions and container tasks using patterns like Serverless Framework, SST, or Docker to ECR to ECS. Apply recommended CI/CD steps to automate deployments for AWS Lambda, Fargate, and Vercel.

Does execution duration and concurrency determine whether I need edge functions or virtual machines?

Execution duration and concurrency directly determine if edge functions or virtual machines are needed. Short, stateless jobs suit edge or serverless, while high concurrency and long durations require VMs or containers.