I use AWS Lambda because it is the most mature of the major cloud platforms for serverless functions. The fact that you can add VPC configs at the start is huge from a security perspective. However, it does take a lot of work to configure the Amazon VPC to work with AWS Secrets Manager and Lambda. It's also nice because it works so well with Amazon API Gateway
I typically use it to connect with databases to insert and extract information for downstream analytics.
I won't be surprised if one day the majority of workloads run on this service. Not having to manage and maintain infrastructure is truly a blessing.
True, yet Lambda does have its drawbacks in term of cold start latency and other arguable deficits. IMO, there is no perfect solution for serverless compute and other offering have their value propositions which should be considered based on need. On this subject though, Secrets Manager and even Parameter Store are great solutions that centralize and eliminate infrastructure (like many AWS offerings). The integration hurdles are relatively the same for any serverless compute environment - you need to integrate with these as 3rd-party services to take advantage of them, and typically in the code.