> What format is it expecting? Do you have the endpoints correct? Is the security scoping accurate? Oh, it didn’t work? Time to embark on a microservices distributed systems murder mystery where the victim is another tiny piece of your soul, because getting coherent logs out of a CloudFront –> API Gateway –> Lambda configuration is CRAP.
I'm trying to figure out what this means because my experience has been the opposite. I find the logs to be generally very code, AWS X-Ray gives you good visibility into the whole process. And you can use third party telemetry / tracing providers too.
Also AWS Cloudwatch is actually pretty powerful for monitoring and supports custom metrics and alarms. It's not the most powerful log system in the world but it is pretty painless to use.
Also, Lambda are just short functions written in the language of your choice (of which there are many) or in a container. What exactly about that is not portable? If I write node.js code it is trivial to run in another environment that runs node.js.
I'm no an AWS super-fan but I feel this article is a rant (and one written without knowing all the actual capabilities of AWS) and not fact based.
I personally use Lambda a lot. The operations effort is near nonexistent saving me countless hours. As I said, I actually like cloudwatch. And economically, if my microservice is unused it uses zero resources and scales up near instantly.
Edit: to add to that, it sounds like the author's real issue is with microservices not serverless.
I'm trying to figure out what this means because my experience has been the opposite. I find the logs to be generally very code, AWS X-Ray gives you good visibility into the whole process. And you can use third party telemetry / tracing providers too.
Also AWS Cloudwatch is actually pretty powerful for monitoring and supports custom metrics and alarms. It's not the most powerful log system in the world but it is pretty painless to use.
Also, Lambda are just short functions written in the language of your choice (of which there are many) or in a container. What exactly about that is not portable? If I write node.js code it is trivial to run in another environment that runs node.js.
I'm no an AWS super-fan but I feel this article is a rant (and one written without knowing all the actual capabilities of AWS) and not fact based.
I personally use Lambda a lot. The operations effort is near nonexistent saving me countless hours. As I said, I actually like cloudwatch. And economically, if my microservice is unused it uses zero resources and scales up near instantly.
Edit: to add to that, it sounds like the author's real issue is with microservices not serverless.