Just checked out the site, this feels surprisingly refreshing.
Most platforms just wrap Kubernetes or slap on another abstraction layer. Heim looks like it’s actually trying to remove layers instead of adding them.
A few quick questions though:
– Can you run long-lived or stateful services (e.g. websockets, streams)?
– How do you handle secrets or database connections?
– Any way to run Heim locally for testing?
Definitely curious to try it out.
Silesmo · 14h ago
Can you run long-lived or stateful services (e.g. websockets, streams)?
In this initial public beta Heim can only handle stateless services, so you would have to use the usual services such as a key value store or database to store state. However in an upcoming release later this year we will release full support for sateful services that can directly replace containers and kubernetes.
Currently we have a way to pass in secrets and environment variables when you deploy an application and we are working on adding in a full secret store which will load the secrets at the startup of the application and pass them in as env variables to the application. But you can also use existing secret vault services that you are already using.
We actually support running the full experience including the same portal as you get in cloud version of Heim locally all of which is contained in the installer of just ~70 MB.
Silesmo · 14h ago
Hey all! small team here.
We built Heim to remove the layers of complexity we kept facing just to deploy simple code.
No YAML, no containers, no ops teams. Just functions that run deterministically and securely.
Would love your thoughts …especially if you’ve ever been frustrated by how modern cloud infra feels like glue code on glue code.
emelie1997 · 14h ago
What is the cold start performance like?
Silesmo · 13h ago
You can expect cold start times in the range of 150 micro seconds to a few milliseconds in a production setup of Heim.
Most platforms just wrap Kubernetes or slap on another abstraction layer. Heim looks like it’s actually trying to remove layers instead of adding them.
A few quick questions though: – Can you run long-lived or stateful services (e.g. websockets, streams)? – How do you handle secrets or database connections? – Any way to run Heim locally for testing?
Definitely curious to try it out.
Currently we have a way to pass in secrets and environment variables when you deploy an application and we are working on adding in a full secret store which will load the secrets at the startup of the application and pass them in as env variables to the application. But you can also use existing secret vault services that you are already using.
We actually support running the full experience including the same portal as you get in cloud version of Heim locally all of which is contained in the installer of just ~70 MB.