I've mainly written simple Lambdas in Python and for that it is easy to "get things done" with the AWS Management Console.
In some sense, when things "get hard" with Lambdas you probably shouldn't be using Lambdas anymore. The tough issues you address can best be addressed by having opinionated answers to them, but if those opinions don't jive with the rest of the systems somebody uses you can take your tool out of the running for some users.
Perhaps the most central idea in AWS architecture is how you keep track of connection information. (e.g. credentials to talk to Dynamo DB or SES or whatever) Life can be sweet if you have a good answer for this, but if you don't you are going to suffer, get hacked, etc.
Yes, Python is easier as it doesn't need compiling. So, you can just copy-paste it to the Console. Yet, there's a lot to be wished. Like instant log access, handling multiple stages (dev, integration, production, demo) etc.
I think Lambdas can be, or better, soon will be suitable for almost all use cases. We are just missing proper tools and good design patterns. Those must to be opinionated.
I've mainly written simple Lambdas in Python and for that it is easy to "get things done" with the AWS Management Console.
In some sense, when things "get hard" with Lambdas you probably shouldn't be using Lambdas anymore. The tough issues you address can best be addressed by having opinionated answers to them, but if those opinions don't jive with the rest of the systems somebody uses you can take your tool out of the running for some users.
Perhaps the most central idea in AWS architecture is how you keep track of connection information. (e.g. credentials to talk to Dynamo DB or SES or whatever) Life can be sweet if you have a good answer for this, but if you don't you are going to suffer, get hacked, etc.