If things scale to zero and are fast to spin up, then yes? Unlikely you want to automatically create a SQL service that costs hundreds of dollars at idle.
-
-
Show this thread
-
I'm thinking about next-gen APIs and the divide between infrastructure CRUD and calling infrastructure from application code. Right now most cloud SDKs contain both. But does it have to be that way?
Show this thread -
Imagine an SDK that ONLY exposed zero cost cloud services. Theoretically, they could all be created at runtime. There is no infra provisioning step.
Show this thread
End of conversation
New conversation -
-
-
Does that mean you have to make calls (so write boilerplate code) to make sure they exist!?
-
The opposite. I'm saying you would never have to do that.
-
I say no



-
But did you see the rest of my thread? If all you have are cloud primitives that scale to zero cost then why not?
-
I did. It’s never zero cost in the long run though is it?
-
disagree. I've got plenty of old cloud resources that are costing me nothing at this moment. The only cost is my pride when I open the UI and am reminded of all my failed-to-launch ideas.
-
Haha good point if they’re not used like a queue
-
That's where I'm going with this. What if all resources could scale to zero. What if a cloud provider only offered that. What would the dev experience look like? I think it could be awesome.
End of conversation
New conversation -
-
-
for cfn/terraform-like APIs, for sure. otherwise, hmmm.
-
ok flip the question. Assume all calls to a resource created them. What does that cloud provider look like?
-
it would also create on read, and not just on mutate?
-
Good Q. Maybe not. Reading things that don't exist should return empty results?
-
maybe such APIs would just look like global, idempotent versions of s3 or dynamo, etc. ie, creating a bucket is like creating a folder, and creating a database is like creating a partition.
-
creating (anonymous) lambdas with cfn already kinda feels like this.
End of conversation
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.