Softwr

Databases · head to head

Apache Hadoop vs Convex

Apache Hadoop logo

Apache Hadoop

Databases

The original open source framework for distributed storage and batch processing on commodity servers, now largely a legacy platform.

From
Free
Free plan
Yes
Convex logo

Convex

Databases

Reactive backend combining a document database, TypeScript server functions and live queries, source-available under the Functional Source Licence.

From
Free
Free plan
Yes

The short version

  • Apache Hadoop is free; Convex starts at $25/mo.
  • Only Apache Hadoop lists HDFS federation and high availability; only Convex lists reactive queries.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Apache Hadoop and Convex actually diverge.

Attributes where Apache Hadoop and Convex differ
AttributeApache HadoopConvex
Pricing modelOpen-sourceSubscription

Identical on both: starting price (Free), free tier (Yes), platforms (Web), category (Databases).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Apache Hadoop

  • HDFS
  • YARN
  • MapReduce
  • HDFS federation and high availability
  • Kerberos security
  • Rack awareness
  • S3A and object store connectors
  • Ecosystem compatibility

Only in Convex

  • Reactive queries
  • TypeScript server functions
  • ACID transactions
  • Document database
  • Scheduling and workflows
  • File storage
  • Text and vector search
  • End-to-end types

What people use each for

The jobs each tool is most often brought in to do.

Apache Hadoop

  • Operating an existing multi-petabyte on-premises estate where data residency or egress costs rule out moving to cloud object storagenot Convex
  • Running Spark or Flink under YARN on hardware you already own, using HDFS as the storage layernot Convex
  • Keeping long-lived regulated archives on infrastructure entirely within your own data centres and legal jurisdictionnot Convex
  • Maintaining legacy Hive and MapReduce workloads during a staged migration to a lakehouse or cloud platformnot Convex

Convex

  • Collaborative applications where several users see the same data and every client must reflect a change immediatelynot Apache Hadoop
  • Agent backends that need durable state, scheduled work and transactional writes without assembling a queue, a database and a cachenot Apache Hadoop
  • Small product teams who need a complete backend, including auth integration, file storage and subscriptions, without hiring infrastructure engineersnot Apache Hadoop
  • Prototypes that must become production without a rewrite of the data layer, where end-to-end TypeScript types remove a class of integration bugsnot Apache Hadoop

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Apache Hadoop

  • The free vendor distributions no longer exist: Cloudera's CDH and Hortonworks' HDP have reached end of support and the successor CDP is subscription-only, so running Hadoop without paying now means assembling, testing and security-patching Apache releases yourself
  • HDFS couples storage to compute, so adding capacity means buying whole nodes with CPU and memory you may not need, and the entire industry moved to object storage precisely because it lets the two be bought separately
  • The NameNode holds all filesystem metadata in memory, so a cluster with tens of millions of small files exhausts heap long before it exhausts disk, and the remedy is a file compaction job that somebody has to write, schedule and own indefinitely
  • Operating it is a distinct specialism covering Kerberos, YARN queue tuning, JVM garbage collection and the compatibility matrix between Hive, HBase, Ranger, Oozie and the core, and an upgrade touches all of them at once rather than one at a time
  • MapReduce is maintained for compatibility rather than actively developed, and new work goes to Spark or Flink, so a job written against MapReduce today is written against an API that will not gain anything further
  • Hiring is against you: the talent pool has moved to cloud data platforms over the past decade, so a Hadoop estate increasingly depends on a small number of individuals, which makes it a succession risk before it is a technical one

Convex

  • The Functional Source Licence is not an OSI open source licence: competing use is prohibited until each release reaches its second anniversary and converts to Apache 2.0, so you may self-host but you may not build a service on it
  • Transactions are bounded at one second of user code, 16 MiB read and written, 32,000 documents scanned and 16,000 written, so every backfill, migration or bulk import has to be chunked into scheduled batches rather than written as a single operation
  • There is no SQL and no query planner; you declare up to 32 indexes per table and traverse them, and joins are loops in TypeScript, so an unanticipated access pattern requires a schema and index change rather than a new query
  • It is not an analytical database, so reporting means streaming data out to a warehouse and BI tools cannot be pointed at Convex directly, which adds a pipeline the architecture diagram did not originally include
  • The application is written against Convex's function and client APIs rather than a standard protocol, so leaving means rewriting the data access layer and replacing the reactivity model, not repointing a connection string

Pricing, plan by plan

Apache Hadoop

Free

No published plan breakdown. See the Apache Hadoop review.

Convex

Free
  • Free & StarterFree
    • Supports 1-6 developers
    • Reactive database
    • File storage
  • Professional$25
    • Supports up to 20 developers
    • All Starter features
    • Log streaming
  • Business & Enterprise$2,500/month minimum
    • Supports 50+ developers
    • SAML/SSO
    • Service SLAs

Which should you pick?

Choose Apache Hadoop if

  • You need hdfs.
  • You want to start without paying.
  • You also want yarn.

Choose Convex if

  • You need reactive queries.
  • You want to start without paying.
  • You also want typescript server functions.

Questions people ask

Is Apache Hadoop or Convex better?
Neither clearly leads. Apache Hadoop starts at Free and Convex at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Apache Hadoop or Convex?
Apache Hadoop starts at Free and Convex at Free.
Does Apache Hadoop or Convex run on more platforms?
Both run on Web, so platform support will not decide this one for you.
Can I use Apache Hadoop for free?
Both have a free tier, so you can try either at no cost before committing.
What is Apache Hadoop best used for?
Apache Hadoop is most often used for operating an existing multi-petabyte on-premises estate where data residency or egress costs rule out moving to cloud object storage, running spark or flink under yarn on hardware you already own, using hdfs as the storage layer, keeping long-lived regulated archives on infrastructure entirely within your own data centres and legal jurisdiction, maintaining legacy hive and mapreduce workloads during a staged migration to a lakehouse or cloud platform. Of those, operating an existing multi-petabyte on-premises estate where data residency or egress costs rule out moving to cloud object storage and running spark or flink under yarn on hardware you already own, using hdfs as the storage layer are not what Convex is typically brought in for.
What can Apache Hadoop do that Convex cannot?
Apache Hadoop covers HDFS, YARN, MapReduce, HDFS federation and high availability. Convex covers Reactive queries, TypeScript server functions, ACID transactions, Document database.

Answered from the vendors’ own pages

Apache Hadoop: Is Hadoop dead?

No, but it is legacy. Large on-premises HDFS estates still run and are still supported, and Spark and Flink still run on YARN. What has ended is Hadoop as a default choice for new platforms, which now start on object storage.

Convex: Is Convex open source?

It is source-available under FSL-1.1-Apache-2.0. You may read, modify and self-host it, but competing use is prohibited until each release converts to Apache 2.0 on its second anniversary.

Apache Hadoop: Can I still get a free packaged distribution?

Not a maintained one. CDH and HDP reached end of support and Cloudera's CDP is a paid subscription. The remaining free route is building and patching Apache releases yourself, which is a real engineering commitment.

Convex: Can I self-host it?

Yes. The backend, dashboard and CLI can run on your own infrastructure, with most of the features of the cloud product. Self-hosted instances include a telemetry beacon that can be disabled.

Apache Hadoop: Do I need Hadoop to run Spark?

No. Spark runs standalone, on Kubernetes and on managed cloud services, and reads object storage directly. Many Spark deployments include Hadoop client libraries for the filesystem connectors without running a Hadoop cluster at all.

Convex: Does it support SQL?

No. Data is accessed through a TypeScript query builder over declared indexes. Relationships are traversed in code, which is explicit and type-safe but means no ad hoc querying.

Apache Hadoop: What replaced HDFS?

Object storage, typically S3 or a compatible system, combined with an open table format such as Apache Iceberg or Delta Lake. Apache Ozone exists as an object store within the Hadoop ecosystem for organisations staying on-premises.

Convex: What happens if a mutation exceeds the limits?

It fails rather than running longer, so bulk work must be split into batches and scheduled. The limits are per transaction: one second of user code, 16 MiB read and written, 32,000 documents scanned and 16,000 written.

Apache Hadoop: Is it cheaper than the cloud?

It can be at multi-petabyte scale with steady, predictable utilisation, particularly where egress charges would be large. Include the staffing cost honestly, because the specialist operators a Hadoop cluster requires are scarce and therefore expensive.

Convex: How does reactivity actually work?

Queries are deterministic functions and Convex records the data each one read. When a mutation changes that data, affected queries are re-run and subscribed clients receive the new result, so cache invalidation is handled by the platform.

Share

Related pages

Other head to heads