3 ms·

Was there a specific service or reason with high cost that stood out?

• PragmaticPulp 6y ago
  The cost become a politically sensitive, and ultimately secretive, topic after it became clear that the costs were growing. I was less involved with that team over time. I got the impression that serverless was quick and easy for the simple server-side operations that could be mapped easily to AWS' serverless building blocks. Of course, this is where they started and showed initial promise. It broke down as they started taking more complicated server-side functions and forcing them into serverless style. It felt like a square peg / round hole situation that ballooned in complexity just to make it serverless. If I did it again, I'd have the teams start with the most complicated server-side functions instead of picking the low hanging fruit first. And, of course, be open to using regular old servers where it made sense to do so. AWS Serverless provided a lot of internal political ammunition because the cloud team could show up in a meeting with complicated diagrams exactly like what you see in this article, whereas previously we just showed single blocks for servers and another block for databases. The complexity did a great job of convincing execs that the AWS experts knew what they were doing, but then of course they were committed to going with the serverless options.