3 ms·

- Clickhouse would be really nice. It's frequently being hosted anyways for something else so using the same cluster for this would be great. Wouldn't have to m

- Clickhouse would be really nice. It's frequently being hosted anyways for something else so using the same cluster for this would be great. Wouldn't have to manage more infra. It's true that pg also exists frequently, but idk that I'd want to risk bogging down the OLTP. -being able to spec a workflow w/ Go is really nice. yaml always feel cumbersome to me, but I also don't use it regularly in my day to day. - love that it's MIT -the Slack use case is cool, but I'd kill for Matrix or maybe Zulip. Feels like there isn't a simple way to do this w/ the other team comm apps beyond Slack rn. -more use-case examples in the README might be a good idea too. Workflow is an overloaded term in my head and I did struggle to figure out where I'd reach for the "hatchet" in my day to day.

abelanger 3y ago
Thanks for the feedback! Going to take a look at what integrating with Matrix would involve. > -more use-case examples in the README might be a good idea too. Workflow is an overloaded term in my head and I did struggle to figure out where I'd reach for the "hatchet" in my day to day. Agreed, can't really find a better term than workflow to describe a set of tasks that execute and are dependent on each other. To execute a single step it's basically a background job runner/task queue, but it's chaining those tasks together and sending the output of one task to the input of another which makes it more powerful. Regardless, I'll add some more use-cases to the README.