Folks, I am working on a new design that would allow users to run low latency workflows on Flyte and run existing simple python tasks and reduce / ammortize the overhead of running a pod. Would folks here be interested in helping me refine the design and the UX model? Goal: Users should be able to run sub second tasks and yet get the same level of visibility, fault tolerance and simplicity for their code. We might lose some isolation properties that running an individual pod offers, but we will continue to offer isolated environments, versioning and dynamic infrastructure.

^ @shy-author-52666: I think this would be awesome for bq-runner pipelines for our "local execution" mode. This ^ @swift-animal-75798 @better-air-29727 something interesting to keep in mind.

Thank you @boundless-twilight-37555 , at the moment, I am conflicted in priority. More resounding support would have made it move asap, but I think we will design now, but final implementation maybe in Q2 ish

Discussing this with the team, it's definitely interesting, but can wait Q2. Thanks!

But let's catch up?