Skip to content
EdgeYodha

Case Studies

Three anonymized stories where we moved high‑stakes edge workloads with zero downtime — across 200‑500+ domains — in weeks, not quarters.

B2C • Consumer Brand
200+
Subdomains
1.5 mo
Duration
0
Downtime

200+ subdomains from Akamai → AWS in 1.5 months — zero downtime

Context

  • High‑traffic B2C brand (millions of daily requests) across India & SEA
  • 200+ subdomains with varied cache keys, signed URLs, device/CDN behaviors
  • Heavy Akamai feature usage; rising egress & CDN costs

Problem

  • Performance variability in key regions; limited IaC; vendor lock‑in risk
  • Rules drift and inconsistent cache policies across subdomains

Solution

  • Parity map Akamai behaviors → CloudFront (origins, cache keys, headers)
  • Edge function rewrite: EdgeWorkers → Lambda@Edge
  • WAF: COUNT → tune → BLOCK; bot mgmt mapping; rate limits
  • Cache warming, RUM baseline; blue/green DNS & real‑time dashboards

Outcome

  • Cutover with 0 downtime (windows < 30min)
  • 35% egress/CDN cost reduction
  • Cache hit ratio +12% (to 98–99%)
  • Delivery time p95 improved by 14% in India
Cache hit ratio
Before86%After98%
CDN/Egress cost index
Before100After65
Migration timeline
  1. 1.
    Assess

    Inventory, configs, traffic profile, risks

  2. 2.
    Plan

    Akamai→AWS parity map, rollback paths, KPIs

  3. 3.
    Simulate

    Lab + shadow traffic; WAF COUNT mode

  4. 4.
    Dual‑Run

    Mirrored paths, compare logs/latency, tune rules

  5. 5.
    Cutover

    Cohorts; time‑boxed windows; live dashboards

  6. 6.
    Optimize

    Cache keys, TLS, Brotli/GZIP, cost tuning

Want a risk‑free migration plan for your stack?

We’ll map parity, simulate with shadow traffic, then dual‑run before cutover.

Talk to an expert
Media • News Agency
300+
Domains
1 mo
Duration
0
Downtime

300+ domains from Cloudflare → AWS in 1 month — uninterrupted publishing

Context

  • National news group with 24/7 publishing and breaking‑news surges
  • 300+ domains including regional editions and vanity domains

Problem

  • WAF false positives impacting editorial tools under load
  • Cache drift and inconsistent TTLs; compliance audit pressure

Solution

  • COUNT‑first WAF rollout; tune FP; normalize managed+custom rules
  • Terraform for reproducible CDN/WAF; Log pipelines (Kinesis/Firehose)
  • Staged DNS steering with health checks; synthetic + RUM monitoring

Outcome

  • All domains migrated in 30 days with 0 disruption
  • API error rate ↓ 22% after FP tuning; editorial tools stable
  • Faster regional delivery (p95 −11%)
False positive rate (index)
Before100After42
Latency p95 (index)
Before100After89
Migration timeline
  1. 1.
    Assess

    Inventory, traffic hot paths, newsroom SLOs

  2. 2.
    Plan

    Cloudflare→AWS parity; FP reduction SLOs

  3. 3.
    Simulate

    Shadow traffic; COUNT mode; dashboards

  4. 4.
    Dual‑Run

    Mirror + compare; tune bot mgmt/rate‑limits

  5. 5.
    Cutover

    Staged by edition; off‑hours windows

  6. 6.
    Optimize

    Cost & cache policies; audit artefacts

Want a risk‑free migration plan for your stack?

We’ll map parity, simulate with shadow traffic, then dual‑run before cutover.

Talk to an expert
B2B • Global SaaS
500+
Domains
phased
Duration
0
Downtime

500+ domains from Akamai → AWS — global rollout, zero downtime

Context

  • Enterprise SaaS with partner SLAs and multi‑region user base
  • 500+ domains, heavy API & image traffic

Problem

  • Complex Akamai rules and tokenization; visibility gaps
  • Latency sensitivity and strict error budgets across regions

Solution

  • IaC parity (behaviors, signed URLs/tokens); workers rewrite
  • Active‑active design; DNS steering; health checks
  • Synthetic+RUM baselines; incident playbooks; blue/green DNS

Outcome

  • Zero‑downtime cutovers across regions
  • Cache hit > 99%; p95 latency −18% in EMEA/APAC
  • Operational handover with Terraform + dashboards
Latency p95 (index)
Before100After82
Cache hit ratio
Before90%After99%
Migration timeline
  1. 1.
    Assess

    Config inventory; partner SLA review

  2. 2.
    Plan

    Parity map & rollback; region cohorts

  3. 3.
    Simulate

    Shadow traffic; WAF COUNT; failover drills

  4. 4.
    Dual‑Run

    Compare logs/latency; tune rules; bot mgmt

  5. 5.
    Cutover

    Follow‑the‑sun cohorts; comms playbooks

  6. 6.
    Optimize

    Cost, cache & TLS tuning; runbooks

Want a risk‑free migration plan for your stack?

We’ll map parity, simulate with shadow traffic, then dual‑run before cutover.

Talk to an expert

Want similar results?

We’ll map your parity, simulate safely, and cut over in days to weeks — not quarters.

Book a Migration Assessment