gcp alloydb - ghdrako/doc_snipets GitHub Wiki
- https://www.youtube.com/watch?v=o5pKfH0Tonw Citus and Timescale are postgres extensions that focus on partitioning data primarily. Citus focused on scaling out across multiple nodes based on whatever primary key you wanted. Timescale focused on single-node and then added multiple nodes later, focused on time (or other integer-based values) and more utilities around time-based analysis. The Citus team also had a columnar data storage extension that's finally more production ready and Timescale created their own implementation by using columnar data but still storing it in the default rowstore and handling the differences in the query layer.
Aurora Postgres and AlloyDB are fundamentally the same thing and involve taking the "top" portion of actual PostgreSQL (wire protocol, parser, query planner, etc) and attaching it to their own rebuilt storage layer. Since storage is the bottleneck, they can scale that out using their cloud architecture and make it seamless to the DB compute layer on top. Other open-source databases like Yugabyte also follow this approach with their own data layer implementation to add distribution and replication.
- https://cloud.google.com/alloydb/pricing
- https://cloud.google.com/alloydb/docs/columnar-engine/about
- https://cloud.google.com/alloydb/docs/omni/omni-cli
- https://cloud.google.com/alloydb/docs/cluster-create#gcloud
AlloyDB Omni - Downloadable edition of AlloyDB, designed to run anywhere—in your data center, on your laptop, at the edge, and in any cloud.