SnowflakeService
liked
We’ll continue to benefit from Snowflake’s operational and ecosystem ease by using it for most other workloads, particularly those that are insert-heavy and don’t require large-scale denormalized tree traversal.
Notion on keeping Snowflake alongside its new data lake
notion.com ↗·2024-07-01Wrong?
SQLiteSoftware
recommended
Using SQLite improved page navigation times by 20 percent in all modern browsers.
Notion on caching client data with WASM SQLite in the browser
notion.com ↗·2024-07-10Wrong?
PgBouncerSoftware
uses
Between our application web servers and the databases, a proxy layer (PgBouncer) pools connections to the databases.
Notion's database architecture, from its re-shard post
notion.com ↗·2023-07-17Wrong?
PostgreSQLSoftware
mixed
By mid-2020, it was clear that product usage would surpass the abilities of our trusty Postgres monolith, which had served us dutifully through five years and four orders of magnitude of growth.
Notion on its Postgres monolith before sharding it
notion.com ↗·2021-10-06Wrong?
CitusSoftware
mixed
During our initial research, we also considered packaged sharding/clustering solutions such as Citus for Postgres or Vitess for MySQL. While these solutions appeal in their simplicity and provide cross-shard tooling out of the box, the actual clustering logic is opaque, and we wanted control over the distribution of our data.
Notion on why it did application-level sharding instead of Citus
notion.com ↗·2021-10-06Wrong?
FivetranService
disliked
The overhead of monitoring and managing 480 Fivetran connectors, along with re-syncing them during Postgres re-sharding, upgrade, and maintenance periods, became extremely high, creating a significant on-call burden for team members.
Why Notion built its own data lake instead of 480 Fivetran connectors
notion.com ↗·2024-07-01Wrong?