Teradata launches QueryGrid, one workflow for big, little data
Summary: The effort behind QueryGrid is part of Teradata's ongoing move to bridge the divide between data warehouses, the core of the company's business, with big data, which is likely to take analytic workloads.
Context & Ripple Effects
Teradata's business rests on its data warehouse, but the analytic workloads the industry calls big data have been pulling toward cheaper distributed platforms — a divide that threatens the company's core if customers split their stacks. Its response has been acquisitive and architectural: the 2012 purchase of eCircle pulled marketing data into the fold, and QueryGrid now attacks the integration problem directly by putting warehouse-scale and small-data queries into one workflow.
The pickup was unusually broad for an enterprise product launch — Computerworld, Data Center Knowledge, information-age.com and even the New York Times ran the story on or about the same day — which reflects how high the stakes of the warehouse-versus-big-data question were for incumbent database vendors.
First-order effects
- Teradata's installed base gets a single workflow that spans its data warehouse and big data stores, removing the operational reason to run Hadoop-era analytic workloads entirely outside Teradata's stack.
- QueryGrid turns the warehouse from a walled engine into a coordinator of heterogeneous datasets, so Teradata competes for the whole analytic workflow rather than just the warehouse tier.
Second-order effects
- Rival warehouse and appliance vendors face pressure to ship their own federation or bridging layers rather than cede the workflow layer to Teradata, while big-data platform vendors gain a new class of partner whose products route queries to them.
- Pricing conversations shift from per-engine capacity toward the value of orchestrating across engines — the vendor that owns the unified workflow controls access to both the big and little data tiers.
Third-order effects
- If one-workflow-across-engines becomes the norm, the structural distinction between 'data warehouse' and 'big data platform' erodes into interchangeable query backends behind a common orchestration front end, and vendor lock-in moves up the stack to whoever owns that front end.
- Enterprise buyers gain leverage to mix engines without re-platforming, pushing the industry toward federated architectures where integration quality, not raw engine speed, becomes the deciding procurement criterion.
The trend: Enterprise analytics is consolidating around unified workflows that span traditional warehouses and big data platforms, shifting competitive value from individual engines to the orchestration layer above them.