Deploy requires to have AWS configured on your machines (either through aws-cli or exported proper keys to your account). You can quickly check what is best for you on the official guide :)
No worries. Lambda is different. there is no persistent storage => you cannot host database there. Its called serverless, because there is no server running all the time (yes, they are there, but its fundamentally different than having an ec2).
There are a bunch of serverless — ready databases you can use with or you need to…
I have that issue once and it was caused by adding un-related files to the “package”. Some of the libraries might be big though.
What you can do is to explore .serverless folder. You will find a zip (a package which SLS sends to lambda) which you can check. If there are some files unrelated to the code, you can exclude them…
thanks! glad you liked it :)
To be honest, never used DynamoDB with that, but you have few options afaik.
You can use dynamodb-local (https://www.npmjs.com/package/serverless-dynamodb-local) to have a fake server (IMHO there are other options doing the same).
Yes, I did mention that near the end of the article. SQS works well within AWS services. On top that, this 2y old experience — might be unrelated now :)
Monitoring wise — biggest strength of CW are afaik Alarms (Auto-Scaling groups).
Thanks for the article, and mentioning the profiler :)
Just a note, because I remember how we ran in very simillar issue some time ago. There are few extension for Chrome (or even just code snippets you can paste into DevTools console) to show how many “bindings” you have. Every binding is slow-down (in digest cycle) and you…