Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: make place for the architecture section #3852

Open
wants to merge 4 commits into
base: release-2.18.0-main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 47 additions & 3 deletions about/index.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,50 @@
---
title: About Timescale
excerpt: Learn about Timescale Cloud and TimescaleDB, including pricing, release notes, feature overview, and contribution guidelines
title: Timescale product overview
excerpt: Timescale Cloud is a cloud-based PostgreSQL platform for resource-intensive workloads
products: [cloud, mst, self_hosted]
keywords: [architecture, pricing, changelog, contribute]
tags: [architecture, pricing, changelog, contribute]
---

# About Timescale
import CloudIntro from "versionContent/_partials/_cloud-intro.mdx";

# Timescale product overview

$CLOUD_LONG is a cloud-based PostgreSQL platform for resource-intensive workloads. We help you build faster, scale further, and stay under budget.
A $SERVICE_LONG is a single optimized 100% PostgreSQL database instance that you use as is, or extend with capabilities specific to your business
needs.

All $SERVICE_LONGs include the tooling you expect for production and developer environments: [live migration][live-migration],
[automatic backups and PITR][automatic-backups], [high availability][high-availability], [read replicas][readreplica], [data forking][operations-forking], [connection pooling][connection-pooling], [tiered storage][data-tiering],
[usage-based storage][how-plans-work], secure in-Console [SQL editing][in-console-editors], service [metrics][metrics]
and [insights][insights], [streamlined maintenance][maintain-upgrade], and much more.

This section explains the:

* [Timescale architecture for real-time analytics][timescale-architecure]: the architecture of Timescale, and the design choices that optimize PostgreSQL for real-time analytics.
* [Pricing plans and account management][pricing-plans]: manage billing and account information for your Timescale account
* [Changelog][changelog]: a summary of the latest changes to all Timescale products.
* [Timescale editions][editions]: compare different editions of TimescaleDB
* [Contribute to Timescale][contribute]: how to contribute to Timescale
* [Release notes][release-notes]: find the release notes in the Timescale GitHub repositories

[timescale-architecure]: /about/:currentVersion:/timescale-architecture
[pricing-plans]: /about/:currentVersion:/pricing-and-account-management/
[changelog]: /about/:currentVersion:/changelog/
[editions]: /about/:currentVersion:/timescale-editions/
[contribute]: /about/:currentVersion:/contribute-to-timescale/
[release-notes]: /about/:currentVersion:/release-notes/
[what-is-time-series]: https://www.timescale.com/blog/what-is-a-time-series-database/#what-is-a-time-series-database
[create-service]: /getting-started/:currentVersion:/services/
[live-migration]: /migrate/:currentVersion:/live-migration/
[automatic-backups]: /use-timescale/:currentVersion:/backup-restore/
[high-availability]: /use-timescale/:currentVersion:/ha-replicas/high-availability/
[readreplica]: /use-timescale/:currentVersion:/ha-replicas/read-scaling/
[operations-forking]: /use-timescale/:currentVersion:/services/service-management/#fork-a-service
[connection-pooling]: /use-timescale/:currentVersion:/services/connection-pooling
[data-tiering]: /use-timescale/:currentVersion:/data-tiering/
[how-plans-work]: /about/:currentVersion:/pricing-and-account-management/#how-plans-work
[in-console-editors]: /getting-started/:currentVersion:/run-queries-from-console/
[metrics]: /use-timescale/:currentVersion:/metrics-logging/service-metrics/
[insights]: /use-timescale/:currentVersion:/metrics-logging/insights/
[maintain-upgrade]: /use-timescale/:currentVersion:/upgrades/
25 changes: 15 additions & 10 deletions about/page-index/page-index.js
Original file line number Diff line number Diff line change
@@ -1,27 +1,27 @@
module.exports = [
{
title: "About Timescale",
title: "Timescale product overview",
href: "about",
filePath: "index.md",
pageComponents: ["featured-cards"],
excerpt:
"Additional information about Timescale, including how to contribute, and release notes",
children: [
{
title: "Changelog",
href: "changelog",
excerpt: "A summary of the latest changes to all Timescale products.",
},
{
title: "Release notes",
href: "release-notes",
excerpt: "Release information for TimescaleDB v2.0.0 - v2.15.1",
title: "Timescale architecture for real-time analytics",
href: "timescale-architecture",
excerpt: "The architecture of Timescale, and the design choices that optimize PostgreSQL for real-time analytics",
},
{
title: "Pricing plans and account management",
href: "pricing-and-account-management",
excerpt: "Pricing plans for Timescale Cloud services",
},
{
title: "Changelog",
href: "changelog",
excerpt: "A summary of the latest changes to all Timescale products.",
},
{
title: "TimescaleDB editions",
href: "timescaledb-editions",
Expand All @@ -31,7 +31,12 @@ module.exports = [
title: "Contribute to Timescale",
href: "contribute-to-timescale",
excerpt: "Contribute to the Timescale codebase",
}
},
{
title: "Release notes",
href: "release-notes",
excerpt: "Release information for TimescaleDB v2.0.0 - v2.15.1",
},
],
},
];
37 changes: 37 additions & 0 deletions about/timescale-architecture.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
---
title: Timescale architecture for real-time analytics
excerpt: The architecture of Timescale, and the design choices that optimize PostgreSQL for real-time analytics.
products: [cloud, mst, self_hosted]
keywords: [Apache, community, license]
tags: [learn, contribute]
---



# Timescale architecture for real-time analytics

Today's applications require real-time analytics to process high-ingestion workloads while ensuring low-latency query performance. Built on PostgreSQL, Timescale is an application database that extends Postgres with real-time analytics capabilities on time series and event data while preserving its full transactional capabilities and SQL compatibility.

This document describes the architecture of Timescale and the design choices that optimize PostgreSQL for real-time analytics. It explores the implementation of TimescaleDB, an open-source time series query engine for Postgres, and Timescale Cloud, a cloud-native database as a service product, detailing innovations that enhance scalability, query execution, operational experience, and data lifecycle management for mission-critical real-time analytics.


## What is a Real-Time Analytics Database?

A real-time analytics database processes incoming data as soon as it arrives, enabling immediate queries and insights with minimal latency. This approach contrasts with batch-based analytical systems, which rely on scheduled ETL processes and can delay analytics by hours or days. By prioritizing low-latency reads and writes, real-time databases ensure that applications can respond quickly to fast-changing conditions.

However, real-time analytics does not focus solely on an append only workload for newly arrived events. Many operational scenarios require mutable data, such as backfilling late-arriving records, correcting previously ingested measurements, or revising event logs to fix inaccuracies. This means the underlying storage engine must efficiently handle both high-throughput inserts and point updates, all while still supporting queries that blend fresh data with historical context. Achieving this balance ensures that real-time workloads can adapt to ongoing data revisions without compromising overall performance.


## The Limitations of Traditional Real-Time OLAP Databases

Efforts to deliver real-time queries on fresh data often rely on “real-time OLAP” databases, which combine analytical processing with near-current information. While they can reduce query latency compared to batch-based or data warehouse solutions, these databases generally remain separate from transactional systems, creating several challenges:



1. **Complex Architecture and Operational Overhead \
**Most real-time OLAP setups require two separate systems (OLTP and OLAP), plus ETL pipelines to synchronize data. This increases complexity, inflates costs, and slows development as teams juggle multiple environments and tooling.
2. **Delayed Data Availability \
**Data typically arrives in a stream from the transactional system to the OLAP store for loading. This introduces a lag between when data is written and when it becomes queryable, undermining truly immediate insights in time-critical scenarios. Because ingestion is often asynchronous, recent writes may also be lost on crash causing silent data drift from the souce database.


Etc
2 changes: 1 addition & 1 deletion use-timescale/integrations/apache-airflow.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Integrate Apache Airflow with Timescale Cloud
excerpt: How to integrate Apache Airflow with Timescale Cloud and create a data pipeline
excerpt: Apache Airflow is a platform to programmatically author, schedule, and monitor workflows. Integrate Apache Airflow with Timescale Cloud and create a data pipeline
products: [cloud, mst, self_hosted]
keywords: [connect, integrate, apache, airflow]
---
Expand Down