presto-gateway VS clutch

https://www.youtube.com/watch?v=-5mlZGjt6H4

All use the Lyft "Presto but really Trino"-Gateway project to run different clusters to handle various workloads. They go into various details for how this is achieved.

https://github.com/lyft/presto-gateway

Regarding the Trino/Presto split. I recommend looking at this blog to better understand why these two communities aren't mergeing. TL;DR Presto is a Facebook-driven project that mainly considers running on the Facebook infrastructure. Trino is community-driven which is why you see a higher velocity there.

https://trino.io/blog/2022/08/02/leaving-facebook-meta-best-...

How do you compare this to [lyft/clutch](https://github.com/lyft/clutch) and would you ever consider integrating with [backstage](https://github.com/backstage/backstage)

We didn't have enough time for testing, but there's also Clutch, coming from the Lyft team. (Checking right now I'm not able to see a "releases" page with versions and that stuff...)

https://clutch.sh/

I was working on an idea to use a chatbot to direct you to the right resource - e.g. put more logic into something like https://clutch.sh, so you could say !botname maintenance and it'll return a set of services in maintenance (read-only) and link to a clutch page (has proper RBAC) that is populated with options you have permissions to, e.g. start a maintenance.