Should SDKs/APIs automatically create cloud resources when called if they don't exist?
Imagine an SDK that ONLY exposed zero cost cloud services. Theoretically, they could all be created at runtime. There is no infra provisioning step.
-
-
The amount of times you accidentally make a new db will be staggering.
-
But if it costs nothing so what? The framework could actually bridge that gap. It could have a notion of what things are expensive (time or $) to create and error unless you create those in the top level of your app
-
I accidentally put user passwords clear text and then leave them in an old db.
-
That is a bad thing in all universes and means you have other issues. Current DB's don't have backups?
-
¯\_(ツ)_/¯ I just want to do somethings intentionally.
-
let go. transcend the client/server/infrastructure divide and embrace oneness. There is only code.
-
Seriously though I've spent like 40 minutes seeing if
@jedschmidt's dynamodown adapter would work with it's levelup storage on lambda. I think the server has to be single threaded so I can't have my serverless replicated data store. - 5 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.