title: AWS: How often Lambda face Cold Starts in production?
body: <p>My company is developing a game using aws and I'm only backend developer.</p>
  <p>Since I'm alone, I thought that going serverless would be easiest and safest solution for me.
  I'm using .net core Lambdas with dynamodb as database as backend stack.</p>
  <p>However, whenever cold start occurs response time of my login function takes around 16s 20s since dynamodb client initialization takes long. I load only 2mb data from db.</p>
  <p>For development purposes, I have scheduled a lambda to avoid cold starts and I also know that I can provision some ready instances. But I think that scheduled calls will provision only one container and in production need will be a lot more. My company is also an advertising company so we expect a lot of users.</p>
  <p>How much percentage of calls might face cold starts in production? Is is more then %20?</p>
  <p>Also, I'm using terraform to manage infrastructure and I'm using route 53 + regional apigateways + custom domains setup to have multiple region latency based routing.</p>
  <p>Would you recomment me to go beanstalk in stead of lambda? Its first time for me to create such environment that should be highly scalable.</p>
  <p>Thank you
  Kind regards</p>