Comments by "TeeKay" (@teekay_1) on "Serverless was a big mistake... says Amazon" video.

  1. Exactly. How this video extrapolated this to say "Serverless is bad and more expensive" is a mystery.
    2
  2. Actually what the finding was that for streaming video (which has unique requirements) serverless turned out to be more expensive. To expand that to every use case is just silly. Serverless for many (if not most) architectures is better, faster, and has less administrative overhead. Now I will say that Lambdas are almost always misused by programmers who aren't smart enough to understand that when you use more than one Lambdas in an architecture you must ensure that the architecture is deterministic, and you need to model it correctly to ensure you understand the implications of these design choices. For example, one anti-pattern that I see with Lambdas all the time is programmers using a Lambda to kick off another process blissfully unaware that the process works in the context of the Lambda, not in a separate context, often with failures that they don't understand and can be hard to debug unless you know that little fact.
    1
  3.  @greggles_b  Amazon Prime and AWS probably don't feel any sense of allegiance to each other.
    1
  4.  @thewhitefalcon8539  yes, just bad architecture. Like someone just learned about lambdas and thought it would be nifty to use them in a new way. Obviously no prototyping to understand the impact, just build it and go.
    1
  5.  @thewhitefalcon8539  " Because really what's the difference between a lambda and a throwaway server? " Significant limits on memory usage and time allowed to run. Lambda also spread business logic in multiple and can make it so understand the outcome of a lambda call unless the design is fully deterministic.
    1
  6.  @thewhitefalcon8539  Actually, what you want to do at that point is use containers with Fargate, which is much quicker, and is durable throughout the transaction lifespan. Fargate is a much better option for transactions than an EC2.
    1
  7.  @thewhitefalcon8539  For transactional processing you don't want durable. You want it to go away once the transaction finishes. If you're setting up transactions to be stateful, in most cases you need to refactor to make your transactions stateless. Containerize your code, use the API gateway to instantiate the container in Fargate. This is very scalable and if you architect correctly not very costly at all.
    1