4 ms·
Love Temporal. Hope you solve the infrastructure and cloud story with this. The biggest pain point is still deploying and configuring a production environment.
by ctvo 5y ago
Love Temporal. Hope you solve the infrastructure and cloud story with this.
The biggest pain point is still deploying and configuring a production environment. I started suspecting it was so awful and poorly documented to push us to using the cloud offering, but then I couldn’t even find a link to sign up for cloud.
- swyx 5y agoyup. we are equal opportunity awful! real answer is it's just really hard. even for us, much less the general developer audience. i wrote the docs we do have, and yeah it shows and I'm not proud of it. Temporal's initial demographic was entirely self sufficient in terms of devops knowledge to take the helm charts and docker stuff we have and translate it to their environment, and read source code/talk to us to fill in any gaps. But as we grow then we'll have to provide more and more rails for people who don't do that stuff. tldr we hear you and a big chunk of this money will go toward both better docs and training for both open source and cloud users.
- ctvo 5y ago> Temporal's initial demographic was entirely self sufficient in terms of devops knowledge to take the helm charts and docker stuff we have and translate it to their environment, and read source code/talk to us to fill in any gaps. I ended up writing a set of AWS CDK constructs internally to provision clusters via ECS + EC2, with best practices baked in, but knowing what the best practices are is a little more difficult. I would prefer not learning through getting burned :)
- swyx 5y agowe’re working with users to identify what those are. mostly when you understand the moving parts of the system you can drive them from first principles. but of course as we grow we should try to do better.