libaws

i dunno. moving off heroku to another provider marking up aws or pretending to seems counterproductive. a go binary in a zip builds and uploads to lambda in 1 second. handle routing and everything else in binary, don’t use aws features. you don’t need em. lambda, s3, and dynamo all scale to zero with usage based billing. toss in rds if you really miss sql or dislike scale to zero. once this is too expensive, move to ovh metal, which sells significantly faster compute, ie epyc 4244p ddr5 5200. more importantly, they sell bandwidth for $0.50/TB instead of $0.10/GB, which is aws price before paas wrapper markup. the ovh price is after the 1Gbps unmetered you get for free with any server. most companies will never even need metal, and between lambda and metal is ec2 spot, which might be of use anyway for elasticity. ovh metal bills monthly, e

i used to write code like this[1]. now i write code like this[2]. mostly what changed is the way i read code. if err != nil is a friend now, not the abomination i first thought it was. 1. https://github.com/nathants/s4/blob/15eb67158cdc03ee1983d060... 2. https://github.com/nathants/libaws/blob/affb1d6002250e35c5ba...

i print the error along with file and line number every time i return it. clunky, but it works. in fact i print file and line with every log message. https://github.com/nathants/libaws/blob/87fb45b4cae20abd1bb1...