From 5dbb40804bc3be653c18ae145e18091927105ca9 Mon Sep 17 00:00:00 2001 From: atovpeko <114177030+atovpeko@users.noreply.github.com> Date: Wed, 20 Nov 2024 11:22:11 +0200 Subject: [PATCH] Removed the concept of Dynamic Postgresql (#3500) * removed the concept of Dynamic Postgresql --------- Signed-off-by: Iain Cox Co-authored-by: Iain Cox --- _partials/_cloud-intro.md | 38 +++++++---- _partials/_service-overview.md | 3 +- getting-started/index.md | 2 - getting-started/services.md | 9 +-- use-timescale/page-index/page-index.js | 5 -- use-timescale/services/dynamic-postgresql.md | 72 -------------------- use-timescale/services/index.md | 2 - 7 files changed, 29 insertions(+), 102 deletions(-) delete mode 100644 use-timescale/services/dynamic-postgresql.md diff --git a/_partials/_cloud-intro.md b/_partials/_cloud-intro.md index 96116d5167..1f5c9e9498 100644 --- a/_partials/_cloud-intro.md +++ b/_partials/_cloud-intro.md @@ -1,17 +1,31 @@ -Timescale Cloud is a cloud-based PostgreSQL platform for resource-intensive workloads. We help you build faster, -scale further, and stay under budget. Timescale Cloud offers the following PostgreSQL optimized database services: +$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. The available capabilities are: -- **[Time-series and Analytics][create-service]**: a Timescale DB instance optimized for your - [time-series and analytics][what-is-time-series] workloads. Get automated dynamic data partitioning, hybrid - row-columnar storage, advanced compression techniques, incremental up-to-date materializations, and specialized - analysis functions as well as cloud-only features like transparent tiering and low-cost object storage. -- **[Dynamic PostgreSQL][create-service]**: for all other workloads. A PostgreSQL instance with a - [dynamic compute range][what-is-dynamic-postgres] aligned to your business needs. You select a compute range, only - paying for the base and the amount of extra CPU as you scale. +- **[Time-series and analytics][create-service]**: PostgreSQL with TimescaleDB. The PostgreSQL you know and love, + supercharged with functionality for storing and querying [time-series data][what-is-time-series] at scale for + analytics and other use cases. + Get faster time-based queries with hypertables, continuous aggregates, and columnar storage. Save on storage with + native compression, data retention policies, and bottomless data tiering to Amazon S3. +- **[AI and vector][create-service]**: PostgreSQL with vector extensions. Use PostgreSQL as a vector database with + purpose built extensions for building AI applications from start to scale. Get fast and accurate similarity search + with the pgvector and pgvectorscale extensions. Create vector embeddings and perform LLM reasoning on your data with + the pgai extension. +- **[PostgreSQL][create-service]**: the trusted industry-standard RDBMS. Ideal for applications requiring strong data + consistency, complex relationships, and advanced querying capabilities. Get ACID compliance, extensive SQL support, + JSON handling, and extensibility through custom functions, data types, and extensions. -All databases are extended with lightning fast vector search, and include all the cloud tooling you'd expect for production use, -with automatic backups, high availability, read replicas, data forking, connection pooling, usage-based storage, and much more. +All $SERVICE_SHORTs include all the cloud tooling you'd expect for production use: +[automatic backups][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], and much more. [what-is-time-series]: https://www.timescale.com/blog/what-is-a-time-series-database/#what-is-a-time-series-database -[what-is-dynamic-postgres]: https://www.timescale.com/dynamic-postgresql [create-service]: /getting-started/:currentVersion:/services/ +[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 diff --git a/_partials/_service-overview.md b/_partials/_service-overview.md index 202e4ca4b4..9588148b44 100644 --- a/_partials/_service-overview.md +++ b/_partials/_service-overview.md @@ -1,5 +1,4 @@ -Each Timescale Cloud service is a single 100% PostgreSQL database with [usage-based storage][how-plans-work]. You -manage your services and interact with your data in Timescale Console using the following modes: +You manage your $SERVICE_LONGs and interact with your data in $CONSOLE using the following modes: diff --git a/getting-started/index.md b/getting-started/index.md index 3209f400ca..8fe5d5f27a 100644 --- a/getting-started/index.md +++ b/getting-started/index.md @@ -14,8 +14,6 @@ import WhereNext from "versionContent/_partials/_where-to-next.mdx"; -Each database instance in Timescale is called a service. - This section shows you how to: 1. [Create and connect to a Timescale service][services-create] diff --git a/getting-started/services.md b/getting-started/services.md index d4ace31e1a..9dedc3b91a 100644 --- a/getting-started/services.md +++ b/getting-started/services.md @@ -10,16 +10,12 @@ import Install from "versionContent/_partials/_cloud-installation.mdx"; import Connect from "versionContent/_partials/_cloud-connect.mdx"; import CreateAHypertable from "versionContent/_partials/_create-hypertable.mdx"; import ServiceOverview from "versionContent/_partials/_service-overview.mdx"; +import CloudIntro from "versionContent/_partials/_cloud-intro.mdx"; # Create your first $SERVICE_LONG -$CLOUD_LONG offers the following PostgreSQL optimized database services: + -- **Time-series and Analytics**: a $TIMESCALE_DB instance optimized for your - [time-series and analytics][what-is-time-series] workloads. -- **Dynamic PostgreSQL**: for all other workloads. A PostgreSQL instance with a - [dynamic compute range][what-is-dynamic-postgres] aligned to your business needs. -- **Vector and AI**: for apps that require fast search on vector embeddings and metadata, like semantic search, image search, RAG and Agents. Powered by $COMPANY Vector and available on Time-series and Dynamic PostgreSQL services. @@ -82,7 +78,6 @@ And that is it, you are up and running. Enjoy developing with $COMPANY. [create-a-hypertable]: /getting-started/:currentVersion:/services/#create-a-hypertable [create-service]: https://console.cloud.timescale.com/dashboard/create_services [what-is-time-series]: https://www.timescale.com/blog/what-is-a-time-series-database/#what-is-a-time-series-database -[what-is-dynamic-postgres]: https://www.timescale.com/dynamic-postgresql [hypertables]: /use-timescale/:currentVersion:/hypertables/about-hypertables/#hypertable-partitioning [timescaledb]: https://docs.timescale.com/#TimescaleDB diff --git a/use-timescale/page-index/page-index.js b/use-timescale/page-index/page-index.js index 7973f6cb29..a6ab18284f 100644 --- a/use-timescale/page-index/page-index.js +++ b/use-timescale/page-index/page-index.js @@ -22,11 +22,6 @@ module.exports = [ href: "service-overview", excerpt: "Timescale services overview", }, - { - title: "Dynamic PostgreSQL", - href: "dynamic-postgresql", - excerpt: "Dynamic PostgreSQL overview", - }, { title: "Service explorer", href: "service-explorer", diff --git a/use-timescale/services/dynamic-postgresql.md b/use-timescale/services/dynamic-postgresql.md deleted file mode 100644 index 876d471d98..0000000000 --- a/use-timescale/services/dynamic-postgresql.md +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: Dynamic PostgreSQL -excerpt: How Dynamic PostgreSQL works -products: [cloud] -keywords: [services, create, postgresql, dynamic] -cloud_ui: - path: - - [services] - - [create_services] ---- - -# Dynamic PostgreSQL - -Dynamic PostgreSQL is a managed PostgreSQL offering on Timescale that is built -for your production workloads. Dynamic PostgreSQL is 100% PostgreSQL with no -alterations to the core database. It comes with Timescale's dynamic compute and -usage-based storage, giving you the scalability of a serverless database with -the performance and cost-effectiveness of a statically allocated DBaaS. - -## Dynamic compute - -Dynamic compute means you choose a compute range with a -minimum and maximum instead of a single static compute option. Your database always has the minimum compute -allocated to it. As your load increases and your application demands more of -your database, your database can use up to the maximum of your range with zero -delay. - -With dynamic compute, your database always has the effective memory -corresponding to the maximum of the compute range. For example, in a 4 - 8 CPU -configuration, your database has 32 GB of effective memory. - -In this model, you only pay for your minimum compute, and are metered for any -usage above your minimum. - - -Dynamic PostgreSQL is currently using early access pricing, -where any metered usage above the minimum is free. - - -## Usage-based storage - -Dynamic PostgreSQL comes with Timescale's usage-based storage. With usage-based -storage, you only pay for the storage saved on disk, rather than the amount of disk space allocated. -Usage-based storage is billed hourly per gigabyte of data. - -## Who is Dynamic PostgreSQL for? - -Dynamic PostgreSQL is designed for continuous production workloads. There are -four main types of database workloads: uniform, variable, bursty, and -intermittent. - -Uniform workloads have a constant CPU usage. Dynamic PostgreSQL serves these -workloads efficiently if the usage is provisioned within the compute range. -This allows you to only pay for the compute you use, rather than -overprovisioning. - -Variable and bursty workloads have some kind of seasonality or spikiness. -Dynamic PostgreSQL is great for these workloads as it allows you to scale -seamlessly and only pay for the usage fluctuation above your minimum. - -Intermittent workloads are workloads that happen only occasionally, don't need -in-memory caching, and can tolerate a cold start. Serverless databases are -generally a better fit for these workloads. - -## Billing - -With Dynamic PostgreSQL, your bill has 2 components: -* Your storage costs, billed in GB/hours -* Your compute costs, which is your base compute plus any fractional - CPU usage above your base, up to your max, in CPU/hours - - diff --git a/use-timescale/services/index.md b/use-timescale/services/index.md index 0bfe9d1f39..cbf365864f 100644 --- a/use-timescale/services/index.md +++ b/use-timescale/services/index.md @@ -18,7 +18,6 @@ import CloudIntro from "versionContent/_partials/_cloud-intro.mdx"; Read about Timescale features in the documentation: -* Determine if you want a time-series or [Dynamic PostgreSQL][dynamic-pg] database * Create your first [hypertable][hypertable-info]. * Run your first query using [time_bucket()][time-bucket-info]. * Trying more advanced time-series functions, starting with @@ -62,4 +61,3 @@ the supported service configurations and operations, see the [time-bucket-info]: /use-timescale/:currentVersion:/query-data/advanced-analytic-queries#time-bucket [terraform-provider-docs]: https://registry.terraform.io/providers/timescale/timescale/latest/docs [terraform-provider]: https://registry.terraform.io/providers/timescale/timescale/latest/ -[dynamic-pg]: /use-timescale/:currentVersion:/services/dynamic-postgresql/