sheetsj’s avatarsheetsj’s Twitter Archive—№ 3,998

      1. Lambdas with Promise.all() making remote calls without try/catch blocks makes for some really difficult to debug bugs! levelup.gitconnected.com/avoiding-the-pitfalls-of-async-node-js-functions-in-aws-lambda-941220582e7a
        Permalink On twitter.com Twitter logo sheetsj’s avatar ❤️ 1 Favorite Mood -1 🙁
    1. …in reply to @sheetsj
      But once you understand that AWS freezes the context before finishing it in the next request, it makes sense. But it’s a big gotcha compared to the traditional node context management
      Permalink On twitter.com Twitter logo sheetsj’s avatar Mood +1 🙂
  1. …in reply to @sheetsj
    Lambdas will really start shining once frameworks are built that take care of the cognitive rough edges by default
    On twitter.com Twitter logo sheetsj’s avatar Mood +2 🙂
    1. …in reply to @sheetsj
      Absolutely love the general experience of using Lambdas for our entire API backend (no ops, serverless, dynamodb, SQS)
      Permalink On twitter.com Twitter logo sheetsj’s avatar ♻️ 2 Retweets ❤️ 2 Favorites Mood +2 🙂
      1. …in reply to @sheetsj
        🔥 95% of the time, cold-starts don’t matter. Even when backing web & mobile apps. Lots of misguided shade thrown on lambdas for these use cases, as the benefits outway the negatives
        Permalink On twitter.com Twitter logo sheetsj’s avatar ❤️ 1 Favorite Mood +5 🙂
        1. …in reply to @sheetsj
          Not having to think about k8s or docker is mind opening and frees room to focus on everything else
          Permalink On twitter.com Twitter logo sheetsj’s avatar ❤️ 1 Favorite Mood 0