We’re running a Java function on AWS Lambda that handles a small number of latency-sensitive requests. Most requests are quick, but occasional cold starts push response times well beyond our target.

For teams running Java on Lambda, how did you decide whether to use provisioned concurrency, SnapStart, or a combination? I’d like to hear what you measured in production, including how predictable the traffic needed to be before the added cost made sense.