| Hey there ... I've been building serverless applications since 4 years now and have gone through a steep learning curve while the technology was very young. I think today you can easily build scalable serverless services using Lambda and other offerings. There are nuances on how to avoid specific bottle necks and work around them, but you'll only spot them probably once they happen. The database is one of the most important choices you can make. Any database that requires a TCP/IP connection and doesn't work with an HTTP API is out of the picture due to the way lambda functions work with such databases. See more: https://www.webiny.com/blog/using-aws-lambda-to-create-a-mon... The learning curve for DynamoDB is steep, but nothing that a senior developer can't tackle in a few weeks. It's a worthy skill to have, especially if you work in the AWS ecosystem. Vendor locking will always be there, but really, don't worry too much about it, especially in the beginning. There are ways to protect yourself by abstracting your business logic and having a layer between how the logic interacts with the underlying serverless service. Later if you do need to move, the move will still be a bit painful, but not as much. Cold start is not a problem at all if your bundle is not overly big. If needed you can always have a few provisioned concurrency functions. Cost, benchmarks and similar - checkout this page: https://www.webiny.com/docs/performance-and-load-benchmark/i... Disclaimer: I'm one of the authors behind Webiny - enterprise serverless CMS. Happy to answer any additional questions. Hope this helps! |