I think the example given in this blog post might need a "health warning" that steps should, generally, be doing more than just printing "hello".
I can imagine that the reads and writes to Postgres for a large number of workflows, each with a large number of small steps called in a tight loop, would cause some significant performance problems.
The examples given on their main site are a little more meaningful.
Yes, that's totally fair. Usually, a step is a meaningful unit of work, such as a API call that performs an external state modification. Because each step is a fair chunk of work, and the overhead is just one write per step, this scales well in practice--as well as Postgres scales, up to 10K+ operations/second.
Your intuition is good - having worked with something similar to this, it works great but does not scale very well. The step journaling is pretty brutal to postgres/rdbms , and you hit vertical scaling limits quicker than you would like
I really dislike this. Sure...it's fun, but where did I "sign up" to allow others to see where my mouse pointer is? How do I disable it? What else, from my machine, is being captured and broadcast?
I spotted a typo on your site. It was then I realised that you have nothing in the way of "contact us" or "who are we?" or any other way to get hold of you.
I'm not sure I'd want to give my infra keys to a team where the only way I can contact you is Trello, and I have no idea who I'm working with.
Do you give customers more details before signing up, or is the idea to remain this anonymous?
ps. The "How This Works" FAQ has the typo "udpates"
Regarding contact, on the website there is an option to schedule a call where we can talk so you can see I'm real person. During that I'm happy to share any information about me. I completely missed that there is no email on the website, right now it's visible on calendly page if you go to book call. I'll add it somewhere there. Thanks!
If I were you I'd create a brand new HN account and ask for advice there.
That's the most compassionate and un-troll-like thing I can imagine anyone doing.
(I really hope you're not seriously asking HN for advice on this. If this is a genuine request for advice, you have plenty of it now. Please go and be a compassionate human and support your co-founder. Consider deleting this post before they get to see it for themselves)
I don’t know that it was the main issue - but yes I think this is common with Shopify hires. I’ve seen a number of similar complaints on Blind’s Shopify board.
I can imagine that the reads and writes to Postgres for a large number of workflows, each with a large number of small steps called in a tight loop, would cause some significant performance problems.
The examples given on their main site are a little more meaningful.