Softwr

Databases · head to head

BigQuery vs Preact

BigQuery logo

BigQuery

Databases

Google Cloud's serverless analytical warehouse, billed either by bytes scanned per query or by reserved compute slots.

From
Free
Free plan
Yes
Preact logo

Preact

Web Development

3kB alternative to React with the same modern API

From
Free
Free plan
Yes

The short version

  • Preact is free; BigQuery starts at $6.25/mo.
  • Only BigQuery lists serverless compute; only Preact lists 3kB runtime.
  • Where Preact falls short: compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose.
  • Prices and features on this page were last checked on 30 August 2026.

How do BigQuery and Preact differ?

BigQuery and Preact differ on pricing model, platforms (Web, API against Web) and category (Databases against Web Development). Only the attributes on which BigQuery and Preact actually diverge.

Attributes where BigQuery and Preact differ
AttributeBigQueryPreact
Pricing modelUsage-basedOpen source, no licence fee
PlatformsWeb, APIWeb
CategoryDatabasesWeb Development

Identical on both: starting price (Free), free tier (Yes).

Not yet recorded: founded for Preact.

Which features does each one have?

They share no listed features; 10 appear only for BigQuery and 4 only for Preact. 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 BigQuery

  • Serverless compute
  • Separation of storage and compute
  • Two pricing models
  • Partitioning and clustering
  • Materialised views
  • BigQuery ML
  • Storage Write API
  • BI Engine

Only in Preact

  • 3kB runtime
  • preact/compat
  • Same modern API
  • Fast rendering

What is each one used for?

Preact is most often brought in for embedded widgets that load inside someone else’s page and must stay small. The jobs each tool is most often brought in to do.

BigQuery

  • A warehouse for an organisation already on Google Cloud, where identity, logging and billing are consolidated in the same placenot Preact
  • Bursty analytical workloads with long idle periods, where paying per query beats keeping a cluster runningnot Preact
  • Event and clickstream analytics ingested continuously through the Storage Write API and queried without a load windownot Preact
  • Analytics teams with no infrastructure staff, where the absence of anything to tune or patch is worth more than dialect portabilitynot Preact

Preact

  • Embedded widgets that load inside someone else’s page and must stay smallnot BigQuery
  • Marketing and content sites where JavaScript payload affects Core Web Vitalsnot BigQuery
  • Applications targeting low-bandwidth or low-powered devicesnot BigQuery

Where do BigQuery and Preact fall short?

Preact's most cited limit: behavioural differences from React exist in edge cases, particularly around event handling. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

BigQuery

  • On-demand billing charges for bytes read from every column a query references, so an unqualified select or a missing partition filter turns a routine query into a large bill, and the cost is discovered after the fact rather than at review time
  • There is no way to join tables that live in different regions, so a data estate split across regions for residency reasons has to be reconciled with copies and the storage and transfer that implies
  • It is not built for point lookups; retrieving a single row has latency measured in hundreds of milliseconds or more, so BigQuery cannot serve an application's read path and always needs a second store in front of it
  • Frequent small mutations run into DML concurrency limits and the cost of rewriting storage blocks, so a workload that updates individual rows continuously behaves badly compared with an append-only design
  • The compute exists only inside Google Cloud, so while tables can be exported, the accumulated GoogleSQL, scheduled queries, authorised views, ML models and IAM structure do not move, and switching warehouses is a rewrite of the analytical layer

Preact

  • Compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
  • Behavioural differences from React exist in edge cases, particularly around event handling
  • A much smaller community, so unusual problems have fewer existing answers than React

How much do BigQuery and Preact cost?

BigQuery has a free plan, with paid plans from $6.25/mo; Preact is free to use. Plan by plan below, from each vendor's own pricing page.

BigQuery

Free
  • Free TierFree
    • 1TB queries/month
    • 10GB storage/month
    • Standard support
  • On-demand$6.25/tb
    • Pay per query
    • Pay per storage
    • All features

Preact

Free
  • PreactFree
    • Full library
    • Commercial use permitted
    • No usage limits

Which should you pick?

Choose BigQuery if

  • You need serverless compute.
  • You want to start without paying.
  • You work on Web, API.
  • You also want separation of storage and compute.

Choose Preact if

  • You need 3kb runtime.
  • You want to start without paying.
  • You also want preact/compat.

Questions people ask

Is BigQuery or Preact better?
Neither clearly leads. BigQuery starts at Free and Preact at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, BigQuery or Preact?
BigQuery starts at Free and Preact at Free.
Does BigQuery or Preact run on more platforms?
BigQuery runs on Web, API. Preact runs on Web.
Can I use BigQuery for free?
Both have a free tier, so you can try either at no cost before committing.
What is BigQuery best used for?
BigQuery is most often used for a warehouse for an organisation already on google cloud, where identity, logging and billing are consolidated in the same place, bursty analytical workloads with long idle periods, where paying per query beats keeping a cluster running, event and clickstream analytics ingested continuously through the storage write api and queried without a load window, analytics teams with no infrastructure staff, where the absence of anything to tune or patch is worth more than dialect portability. Of those, a warehouse for an organisation already on google cloud, where identity, logging and billing are consolidated in the same place and bursty analytical workloads with long idle periods, where paying per query beats keeping a cluster running are not what Preact is typically brought in for.
What can BigQuery do that Preact cannot?
BigQuery covers Serverless compute, Separation of storage and compute, Two pricing models, Partitioning and clustering. Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering.

Answered from the vendors’ own pages

BigQuery: How is BigQuery actually billed?

Storage is billed separately from compute. Compute is either on-demand, priced by the bytes a query reads from the referenced columns, or capacity-based, where you reserve autoscaling slots. Most cost surprises come from on-demand queries that scan more than expected.

Preact: Is Preact free?

Yes, open source under the MIT licence.

BigQuery: How do I control query cost?

Partition and cluster tables so queries prune data, select only the columns needed, use materialised views for repeated aggregations, and set maximum bytes billed on queries so a runaway scan fails instead of billing.

Preact: Can I use React libraries with Preact?

Most, through the preact/compat layer. Compatibility is good but not complete, so libraries relying on React internals can break.

BigQuery: Can I use it without being on Google Cloud?

The service only runs on Google Cloud. BigQuery Omni can query data held in S3 or Azure storage, but the compute is still Google's and the account relationship is still with Google.

Preact: Why choose Preact over React?

Bundle size, almost always. If payload is not a binding constraint, React’s ecosystem is usually the better trade.

BigQuery: Is it suitable for serving application queries?

No. Latency for single-row reads is far too high. BigQuery is an analytical warehouse and application read paths need a transactional database or a cache in front of it.

BigQuery: When should I move from on-demand to capacity pricing?

When on-demand spend becomes both large and predictable, or when unpredictable spend is a bigger problem than query queueing. The switch trades a variable bill for a fixed one plus contention between workloads.

Share

Related pages

Other head to heads