3 ms·
Reminds me of Rundeck and the time we were trying to build something similar. There are more modern take like fiberplane and moment.dev. Not sure about their ad
by debarshri 2y ago
Reminds me of Rundeck and the time we were trying to build something similar. There are more modern take like fiberplane and moment.dev. Not sure about their adoption.
At one point, we were building something like this on top of kubernetes. I think tech is the easy part here. Getting people to leave their existing workflows and use your product is hard.
Secondly, difficult part of our journey was integrations. Until you have integrated all the tools an org uses, product is useless.
Thirdly, it is great that there are building blocks, but users understand use cases. So, expecting end users to build playbooks themselves is tricky. There has to be an intrinsic motivation within the platform.
Fourthly, it is super competitive space if you see it from an internal tool building perspective. There are lot of internal tool builders like appsmith, retool, tooljet, django admin you are competing with where you could run bash scripts, sql queries etc.
Best of luck, with you journey.
- cdchn 2y agoI was looking at using moment.dev for a very similar (internal) application but the lift of using TypeScript and how the whole tool worked was very daunting. Having a simple Jupyter notebook interface (in Python) is much more approachable for a devops background.
- debarshri 2y agoIn my experience, getting devops and infrastructure engineers to use Jupyter notebook specifically for SRE stuff is hard. What is working for is, in our new pivot is, you have to meet where the engineers are at. It could be Jetbrain's tools, VSCode or terminal. Otherwise the lift is always too much. In my opinion, Jupyter way might be better but still not good enough to cross over.