Client: EventNest · DevOps, SRE & Cloud · UK ticketing SaaS (60 staff)

Reducing Lambda Cold Starts for a Ticketing Platform

By TechSupport Team. Published November 16, 2026. Updated .

TechSupport Team supported EventNest’s AWS Lambda functions for ticket-sale launches. Over four months, client Datadog records show p95 cold-start time falling from 3.1 seconds to 560 ms. AWS billing reported a 27% reduction in compute costs.

Client and engagement facts

Client
EventNest
Industry
DevOps, SRE & Cloud
Business context
UK ticketing SaaS (60 staff)
Delivery model
Cloud engineering support
Application
Ticketing platform on AWS Lambda
Supplied geography
UK
Company size in source
60 staff

Application stack and tools

Application stack

  • Node.js
  • AWS Lambda
  • DynamoDB
  • API Gateway

Tools used

  • Datadog
  • AWS billing
  • PagerDuty
  • Terraform

Why Support Was Needed

Three high-traffic functions needed capacity in place before a sale opened. The engineers enabled provisioned concurrency for those functions and right-sized the remaining workloads.

Technical Work

  • Added provisioned concurrency to three hot Lambda functions.
  • Right-sized the rest to cut compute cost 27%.
  • Built a scaling runbook for the sale-launch pattern.

Representative Incident

An AWS regional limit triggered a scaling incident in month two. Raising the limit took eight days. The engineers documented the dependency and added it to periodic checks.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSource and scope
Cold-start P953.1 s560 msBaseline: s; Result: ms4 monthsClient Datadog
Compute cost—-27%Result: %4 monthsClient AWS
Scaling incidents6/q0/q/q4 monthsClient PagerDuty; Scope: The four-month scaling-incident comparison excludes one regional-quota incident.

Evidence and Limitations

The four-month scaling-incident comparison excludes one regional-quota incident. Compute cost is a relative change in the client’s AWS records.

Provider Quota Checks

The engineers documented provider quotas as a dependency and scheduled quarterly limit checks.

Scope a Similar Engagement

Share your busiest launch window and the functions, quotas and scaling checks it depends on. Request a support plan or explore DevOps support.

Get a technical support plan

Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.

  • We reply by email.
  • We agree a call about the roles, your stack and the hours.
  • If there is a fit, we propose engineers after an assessment.

A short outline is enough. Add your stack and coverage hours if you know them. Do not include credentials or customer data.

Add coverage and team details

We use these details only to reply to you. Describe the application, stack and hours you need covered. Keep credentials and sensitive technical data out of this form. We save the brief for delivery and use Telegram to notify our team.