Nix vs Trino

No. The package manager runs fine on any Linux distribution and on macOS, and most teams start there with development shells rather than converting their servers.

They share an origin. The original creators left Meta and renamed their fork from PrestoSQL to Trino in December 2020; PrestoDB continues separately under the Linux Foundation. They have diverged in features, connectors and SQL behaviour, so material written for one may not apply to the other.

It solves an adjacent problem. Nix reproduces the contents of an environment exactly; Docker distributes an image. Many teams use Nix to build the image.

Not on its own. It is compute without storage, scheduling or transformation. Paired with Iceberg or Delta on object storage and something like dbt for modelling it can serve as a lakehouse; used alone it is a query layer over what you already have.

They are used in production widely and are stable in practice, but they remain officially experimental, which means the interface can still change and documentation is split.

Usually because a connector could not push a filter or aggregation down, so Trino is pulling whole tables across the network to join them itself. The fix is usually better source-side partitioning or statistics, or ingesting that source rather than federating it.

Lix is a community fork of the Nix implementation created after governance disputes. It is largely compatible; the practical impact is that you must decide which implementation your team standardises on.

It fails. Disk spilling was deprecated in favour of fault-tolerant execution, which checkpoints to an external exchange store such as S3 and lets long queries survive memory pressure and worker loss, at the cost of noticeably slower execution.

Yes, from Starburst, which offers Starburst Enterprise with long-term supported releases and Starburst Galaxy as a managed service. The open source project itself has no long-term support line.