In this concluding part of the podcast, "Pitfalls in Serverless," we continue to discuss two major issues in serverless, this is more to deal with Boundary scenarios of Throttling limits

1- Queue of Death (from 5:50) - SQS routing valid messages to Dead queue as Lambda couldn't process it in the throttling stage, this essentially translates to loss of revenue/business. By balancing Concurrency limit, Max receive count and visibility time out we can minimize the impact but cannot completely eliminate it 

Reference:  https://data.solita.fi/lessons-learned-from-combining-sqs-and-lambda-in-a-data-project/?utm_source=thenewstack&utm_medium=website&utm_campaign=platform

2- Million Dollar Problem (From 18:20) - How a startup saved million dollar in AWS bills by cutting short Dynamo DB partitions and elevated its performance which was dropping down, all due to missing data, a common error in IT applications

Reference:  https://segment.com/blog/the-million-dollar-eng-problem/?utm_source=thenewstack&utm_medium=website&utm_campaign=platform

For part -1 of this podcast, you can refer to this link - https://anchor.fm/tech-padasala/episodes/Caution---Serverless-el1n68

For questions or feedback pls feel free to write to me at [email protected]

 #cloud #cloudcomputing #cloudarchitecture #awscloud #cloudapplications #performanceengineering #aws