Terality Docs
  • What is Terality?
  • Documentation
    • Quickstart
      • Setup
      • Tutorial
      • Next steps
    • User guide
      • Supported configurations
      • User dashboard
      • Importing and exporting data
        • Reading/writing to storage
        • Reading from multiple files
        • Writing to multiple files
        • Storage services
        • Data formats
        • From/to pandas
      • .apply() and passing callables
      • Caching
      • Best practices and anti-patterns
      • Upgrading your client version
      • Client configuration (CLI)
      • Support for external packages
      • Advanced topics
        • Data mutability and ownership: Terality vs pandas
    • API Reference
      • Conversion from/to pandas
      • Write to multiple files
    • Deploy Terality in your own AWS account
    • Releases
  • FAQ
    • Differences with
      • Terality and Pandas
      • Terality vs Spark
      • Terality vs Dask
    • Pricing
    • Security
    • Support & contact
    • Common setup issues
Powered by GitBook
On this page

Was this helpful?

  1. FAQ
  2. Differences with

Terality vs Dask

PreviousTerality vs SparkNextPricing

Last updated 3 years ago

Was this helpful?

Terality aims to remove the limits of Dask.

Dask

Terality

Dataset size

Small to Mid-size

Small to Large

Infrastructure

Local

Serverless

Pandas' API

Some functions

Most functions (all functions soon)

Syntax

Pandas but Asynchronous

Pandas

Errors

Often hard to understand

Same as Pandas

Data scientist's autonomy

Yes locally, No on VMs

Yes

Support

No

Yes

Here is a medium article comparing Dask and Terality:

Dask vs. Terality — Which Pandas Alternative Is The Best For You?