title: How can I keep Google Cloud Functions warm?
body: <p>I know this may miss the point of using Cloud Functions in the first place, but in my specific case, I'm using Cloud Functions because it's the only way I can bridge Next.js with Firebase Hosting. I don't need to make it cost efficient, etc.</p>
  <p>With that said, the cold boot times for Cloud Functions are simply unbearable and not production-ready, averaging around 10 to 15 <em>seconds</em> for my boilerplate.</p>
  <p>I've watched this video by Google (<a href="https://www.youtube.com/watch?v=IOXrwFqR6kY" rel="noreferrer">https://www.youtube.com/watch?v=IOXrwFqR6kY</a>) that talks about how to reduce cold boot time. In a nutshell: 1) Trim dependencies, 2) Trial &amp; error for dependencies' versions for cache on Google's network, 3) Lazy loading.</p>
  <p>But 1) there are only so many dependencies I can trim. 2) How would I know which version is more cached? 3) There are only so many dependencies I can lazy load.</p>
  <p>Another way is to avoid the cold boot all together. What's a good way or hack that I can essentially keep my (one and only) cloud function warm?</p>