Well, sort of. Fugue overall is a scaling engine like ray. The specific link to yet another SQL access layer to a dataset doesnt really have an analog on ray, but has some nice features.

I love these SQL layers but they can obfuscate how they implement their transforms. So, they can speed up filter and join creation and coding... til something breaks and then you have to go atomic anyway.

Fugue is a translation layer from SQL to underlying runtime: pandas, dask, spark.

Each of the runtimes, supported by Fugue, can be compared to Ray, but Fugue is a tool of a different kind.

That is very true. Thank you.

Fugue SQL is one way, and it also has functional API. They both can be translated into the underlying runtime. You can choose based your preference and real need.

Much better worded than my post above. Yup to this.