slrainka

open .

Transactions Per Second.

Always looking to optimize on cost for AWS. But it's a tradeoff of something or the other. Light Sail sounds like a great solution for some use-cases though.

We run this for a Global/North American airline and easily hit 1k TPS just on API and event processing traffic. The spikes can show up anywhere in the multitude of processes due to various business events (high reservation traffic to irregular operations due to weather, pandemics etc.) Performance and reliability wise, serverless has been a very predictable consistent experience. Costs are another story.

Can you share a bit more about the architecture and stack? And a few more details such as Roughly how many TPS do you serve from this setup? Does it scale well? Are response times consistent?

Just a couple of months ago, we were blindsided by a massive AWS bill after turning on encryption for logging (an ask from security team). The encryption relied on using KMS, but because it was a serverless setup and each time a lambda was initialized it would grab the KMS keys. Later we found out that invoking that many KMS calls while doesn't cost that much, however does invoke CloudTrail logs which are quite costly. Sometimes it's hard to model something like that. Following this experience KMS team made some changes to how their service/pricing works given its tight coupling to CloudTrail. We also stopped using KMS and simplified the log encryption approach by writing logs directly into an encrypted S3 bucket.