4 ms·

As a Deno fan I was surprised to learn that the free tier for Deno Deploy includes 100k requests per day and 100GB of bandwidth monthly. I know I'll be trying i

• benatkin 4y ago
  I think Deno Deploy and using Deno on fly.io could be a powerful combo. Deno has some advantages that definitely lend themselves to having control of your entire MicroVMs. An app could easily be split between serverless-friendly and non-serverless-friendly parts of the stack by using both together.
• mkroman 4y ago
  > Up to 10ms CPU time per request So less than 17 minutes of CPU time per day - not a lot, but also not nothing.. But at 10ms per request, what would one use it for? Just server-side rendering for something simple?
  • crowlKats 4y ago
    proper applications as well. example is the https://deno.land https://deno.land website has an average CPU time of 6ms. CPU time means it doesnt include any IO bound operations, so ie doing a fetch request wont really contribute to the CPU time.
    • yencabulator 4y ago
      Average time 6ms with hard cap at 10ms sounds like a ticking timebomb you don't dare to put in production. I've had to switch multiple webapps to Cloudflare Workers' "unbound" mode to go beyond CPU time limits.
  • ascorbic 4y ago
    Bear in mind this is CPU time, not wall clock time. I work with both AWS Lambda functions and Deno Deploy functions every day. I hit the 10s Lambda timeout all the time (things like slow API calls or network requests), but I never hit the timeout for Deno Deploy. You can even use it for things like Server-Sent Events or Websockets. It'll keep the connection open indefinitely, as long as it's not using the CPU.