AWS Serverless Components for Event-Driven Workloads: A Comparative FaaS Performance Evaluation

🚀 I’m excited to share insights from my latest research paper: AWS Serverless Components for Event-Driven Workloads: A Comparative FaaS Performance Evaluation.
This study evaluates AWS Lambda, AWS Fargate, and AWS Step Functions under consistent, event-driven workloads—providing developers, architects, and cloud strategists with data-backed guidance.

📄 Full Paper: Read on ResearchGate


🎯 Why This Study?

AWS offers multiple serverless-capable components, each with unique trade-offs in performance, scalability, and cost.
For event-driven architectures—where workloads are triggered by real-time events—choosing the right component can dramatically affect latency, cost efficiency, and developer experience.


📊 What We Evaluated

We benchmarked each service across four dimensions:

  1. Cold Start vs Warm Start Latency
    How quickly functions start when idle vs. when warmed.

  2. Execution Performance
    CPU-bound and I/O-bound task throughput.

  3. Cost Trade-Offs
    Comparative pricing under different workloads.

  4. Scalability & Orchestration Overhead
    How services handle concurrent requests and orchestration complexity.


🔍 Key Findings

1. AWS Lambda

  • Best for: Short-lived, bursty workloads
  • Strengths: Automatic scaling, pay-per-use cost model
  • Limitations: Cold start delays for infrequently invoked functions

2. AWS Fargate

  • Best for: Long-running or stateful workloads
  • Strengths: Consistent performance, container flexibility
  • Limitations: Higher cost for sporadic usage compared to Lambda

3. AWS Step Functions

  • Best for: Complex workflows with multiple tasks
  • Strengths: Simplifies orchestration, integrates with many AWS services
  • Limitations: Latency per state transition adds up in high-frequency workflows

📌 Recommendations

Workload Type Recommended Service Rationale
Bursty, lightweight functions AWS Lambda Low cost, quick scale-out
Long-running compute tasks AWS Fargate Consistent throughput
Multi-step orchestrations AWS Step Functions Visual workflow & service integration

🛠️ Practical Implications for Architects

  • Hybrid Approach Wins – Mix Lambda for triggers, Fargate for heavier processing, Step Functions for orchestration.
  • Optimize for Cold Starts – For Lambda, use provisioned concurrency for latency-sensitive workloads.
  • Model Costs Early – Understand request frequency, execution time, and orchestration complexity to avoid bill shock.

🔮 Future Work

This research opens the door to:
* Comparing serverless options across cloud providers
* Adding GPU-based workloads into the benchmark
* Evaluating sustainability metrics like carbon footprint