I recently started worked as a consultant at a tech company, where the general consensus is to move away from a monolith application running on EC2 towards building microservices on AWS Lambda. I frankly have no experience working with Lambda and only have heard horror stories from friends and acquaintances who have used it for working with large sets of scrapped data. Having a history of burnt fingers jumping into new services and technology I often read pros and cons about what I am going to work with in order to a have a general idea about what I can expect.The problem I face is that I am unable to find any form of content on an engineer's experience on how building microservices on AWS lambdas scale along with mistakes that I should/can avoid while building microservices on it. I would appreciate any opinions or comments provided on the topicHere is what I know based on what I have read,
Pros: Only need to allocate processing bandwidth when needed such as peak hours. Being able to deploy with less code. Ability to handle flow of control/data on GUI via AWS Step functions.
Cons: Local testing/debugging not simple but possible via services such as www.serverless.com, Cold starts(there are ways to keep the lambda warm, but that is equivalent to just having it up all the time).