Cloud Stories and Remarks
Miss one uplink and the top floor of a skyscraper floods. Catastrophically expensive.
Just as I was thrust into the world of database application development, a similar situation arose where I found myself specifying, deploying and operating cloud infrastructure. It has to be done right when one has nearly 100k devices in the field that are in constant communications (hundreds of uplinks per second, many millions per day) with your database application and there is little tolerance for dropped messages.
- 9PM on a friday, and an infinite number of lambda function invocations
- A case for using SQS with IOTWireless
- AWS Cloudwatch is expensive and hard to use!
- Launching lambda functions at a 1 second interval - all you need is a DB and pg_cron!
- S3/R2/etc. is underrated
- EC2: who owns this machine?
- EC2: out of memory for a month