# Reducing Lambda Cold Starts for a Ticketing Platform

> 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.

- Publisher: TechSupport Team
- Canonical page: https://techsupport-team.com/case-studies/ticketing-saas-lambda-cold-starts/
- Updated: 2026-11-16

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

## 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

Related services: [DevOps support](https://techsupport-team.com/services/devops-support/)

## 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

Table: Reported results and their measurement scope

| Metric | Baseline | Result | Units | Measurement window | Source and scope |
| --- | --- | --- | --- | --- | --- |
| Cold-start P95 | 3.1 s | 560 ms | Baseline: s; Result: ms | 4 months | Client Datadog |
| Compute cost | — | -27% | Result: % | 4 months | Client AWS |
| Scaling incidents | 6/q | 0/q | /q | 4 months | Client 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](https://techsupport-team.com/contact/) or explore [DevOps support](https://techsupport-team.com/services/devops-support/).

## Related pages

- [DevOps support](https://techsupport-team.com/services/devops-support/): The related service for this engagement.

## Contact

Request engineers from TechSupport Team or ask a question: https://techsupport-team.com/contact/
