6 comments

  • bob102922 minutes ago
    I strongly recommend never using functions as a service unless you genuinely have some client edge compute requirement that absolutely cannot be solved via some other means.<p>Everything about running software is made more difficult this way. You might think it would make certain infrastructure aspects easier, but it just changes the semantics of the same problem. It&#x27;s the same quantity of mess to clean up, but now it&#x27;s in these really weird piles that are often much harder to access.<p>&gt; up to 128 concurrent requests per environment<p>I am fairly confident I could support more capacity with a single t3a.nano instance.
    • vermilingua3 minutes ago
      I seem to have had the opposite experience. Using Lambda (I can&#x27;t speak for many of the other FaaS platforms) is so straightforward to me that there need to be some strong arguments for hosting code&#x2F;containers in my projects.<p>My guess is that the IaC is the special sauce that&#x27;s missing; you do need to go all in with some IaC solution to make using Lambda easy, but it doesn&#x27;t take a lot of it to make it slick.<p>Cost&#x2F;compute is obviously strictly worse for FaaS, but most web workloads don&#x27;t _really_ need to be optimal.
  • jack_sunsetless21 minutes ago
    Finally Lambda without the adapter layer.. Now please add .NET and Java with those concurrent requests
  • chaz628 minutes ago
    Being able to handle concurrent requests with one worker is nice. I hope this becomes available for Python too.
  • cowlevel1 hour ago
    How is this different from a container?
    • kichik29 minutes ago
      The scaling part. You don&#x27;t need to do anything. It just runs as many instances of the Lambda as needed for you.
      • cowlevel24 minutes ago
        Does Elastic Container Service not do that?
        • kichik19 minutes ago
          No, not really. You can attach auto scaling to it. But it doesn&#x27;t scale as fast. And it&#x27;s not very straightforward to scale to zero. And you have to maintain all of it yourself.
          • oblio14 minutes ago
            Fargate does, though. And it&#x27;s been doing it for at least 5 years, if not more.
    • Callumk7759 minutes ago
      Skip the docker part I guess? More approachable for new vibe-orientated developers
    • vends53 minutes ago
      [flagged]
  • HatchedLake7211 hour ago
    looks like an answer to Cloudflare Workers
    • ZiiS1 hour ago
      Isn&#x27;t this a move in the other direction. Workers and traditional Lambda need to you write short lived event handlers; this is about running a standard server.
    • beastman8240 minutes ago
      And appengine
      • cowsandmilk23 minutes ago
        A response to App Engine 18 years after its release?
        • beastman8219 minutes ago
          It&#x27;s the same idea however you characterize it.
    • Imustaskforhelp1 hour ago
      Also vercel, railway, render etc<p>Cloudflare workers wasn’t always an 1:1 option for simple hosting (iirc) and people used to think it was more complicated than vercel etc but it has changed in recent years and right now they have made things smoother and simpler to compete with vercel and others.<p>Now that AWS has entered into the field as well, given that vercel and others already build on top of AWS. It will be interesting to see how this all goes.<p>I wonder if more og hyper scalers like say hetzner&#x2F;ovh and others will also target this audience
  • quietFalcon1 hour ago
    [dead]