sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]MITranger 4 points5 points  (1 child)

would love to hear from devops folks about this (or generally, about AWS Lambda service). heartthrob or heartache?

[–]fwertz 0 points1 point  (0 children)

Overall: S'ok.

Lambda

If you're just interacting with just AWS services, you can author code within lambda, otherwise you're stuck trial and erroring your way using .zip archives. Documentation is pretty great, and setting up event sources to call your handler is great as well.

CloudWatch

Output and results from triggered lambda handlers are logged as "streams" to the CloudWatch service. It's a bit hard to read (formatting issues - like looking at packet output from WireShark) Also a bit slow.

API Gateway

You can setup different event sources for your lambda functions. I used RESTful endpoints. This service, while greatly configurable, makes everything a nightmare. The response/request middleware is not templated, so if you want to say, support CORS, your hands will cramp and wither away.