Pretty good actually. We started using AWS Lambda as a tool for a cron job. Then we implemented a RESTful API with API Gateway and Lambda. The Lamdbas are str

Pretty good actually. We started using AWS Lambda as a tool for a cron job. Then we implemented a RESTful API with API Gateway and Lambda. The Lamdbas are straightforward to implement. API Gateway unfortunately has not a great user experience. It feels very clunky to use and some things are hard to find and understand. (Hint: Request body passthrough and transformations). Some pitfalls we encountered: With Java you need to consider the warmup time and memory needed for the JVM. Don't allocate less than 512MB. Latency can be hard to predict. A cold start can take seconds, but if you call your Lambda often enough (often looks like minutes) things run smooth. Failure handling is not convenient. For example if your Lamdba is triggered from a Scheduled Event and the lamdba fails for some reason. The Lamdba does get triggered again and again. Up to three times. So at the moment we have around 30 Lambdas doing their job. Would say it is an 8/10 experience.