- Aerospike
- Akamas
- AlloyDB
- ApertureDB
- Arrow
- Berkeley DB
- BlazingDB
- Brytlyt
- Chaos Mesh
- Citus
- CockroachDB
- Convex
- CrateDB
- Databricks
- Datometry
- dbt
- Delta Lake
- Dremio
- DuckDB
- EdgeDB
- Exon
- FASTER
- FeatureBase
- Feldera
- Fluree
- Gaia
- GlareDB
- GoogleSQL
- GreptimeDB
- Heron
- Iceberg
- InfluxDB
- kdb
- ksqlDB
- LeanStore
- LMDB
- MapD
- Materialize
- Milvus
- MonetDB
- Mooncake
- MySQL
- Neon
- Noria
- OceanBase
- Oracle
- OxQL
- Pinecone
- PlanetScale
- PostgresML
- PRQL
- QMDB
- QuestDB
- Redshift
- RisingWave
- Rockset
- rqlite
- Samza
- SingleStore
- SLOG
- Snowflake
- SpiceDB
- SplinterDB
- SQL Server
- SQLite
- Stardog
- Striim
- Swarm64
- Technical University of Munich
- TiDB
- TileDB
- Tokutek
- Umbra
- Vertica
- VoltDB
- Weaviate
- XTDB
- YugabyteDB
- AirFlow
- Alibaba
- Anna
- APOLLO
- Azure Cosmos DB
- BigQuery
- Bodo
- Cassandra
- Chroma
- ClickHouse
- Confluent
- CouchDB
- CrocodileDB
- DataFusion
- Datomic
- Debezium
- Dolt
- Druid
- DVMS
- EraDB
- eXtremeDB
- Fauna
- Featureform
- Firebolt
- FoundationDB
- Gel
- Google Spanner
- Greenplum
- HarperDB
- Hudi
- Impala
- Jepsen
- Kinetica
- LanceDB
- Litestream
- Malloy
- MariaDB
- MemSQL
- Modin
- MongoDB
- MotherDuck
- Napa
- NoisePage
- NuoDB
- OpenDAL
- OtterTune
- ParadeDB
- Pinot
- Polaris
- PostgreSQL
- Qdrant
- QuasarDB
- RavenDB
- RelationalAI
- RocksDB
- RonDB
- SalesForce
- ScyllaDB
- sled
- Smooth
- Spice.ai
- Splice Machine
- SQL Anywhere
- SQLancer
- SQream
- StarRocks
- Summingbird
- Synnada
- TerminusDB
- TigerBeetle
- TimescaleDB
- Trino
- Velox
- Vitesse
- Vortex
- WiredTiger
- Yellowbrick
- Aerospike
- Alibaba
- ApertureDB
- Azure Cosmos DB
- BlazingDB
- Cassandra
- Citus
- Confluent
- CrateDB
- DataFusion
- dbt
- Dolt
- DuckDB
- EraDB
- FASTER
- Featureform
- Fluree
- Gel
- GoogleSQL
- HarperDB
- Iceberg
- Jepsen
- ksqlDB
- Litestream
- MapD
- MemSQL
- MonetDB
- MotherDuck
- Neon
- NuoDB
- Oracle
- ParadeDB
- PlanetScale
- PostgreSQL
- QMDB
- RavenDB
- RisingWave
- RonDB
- Samza
- sled
- Snowflake
- Splice Machine
- SQL Server
- SQream
- Striim
- Synnada
- TiDB
- TimescaleDB
- Umbra
- Vitesse
- Weaviate
- Yellowbrick
- AirFlow
- AlloyDB
- APOLLO
- Berkeley DB
- Bodo
- Chaos Mesh
- ClickHouse
- Convex
- CrocodileDB
- Datometry
- Debezium
- Dremio
- DVMS
- Exon
- Fauna
- Feldera
- FoundationDB
- GlareDB
- Greenplum
- Heron
- Impala
- kdb
- LanceDB
- LMDB
- MariaDB
- Milvus
- MongoDB
- MySQL
- NoisePage
- OceanBase
- OtterTune
- Pinecone
- Polaris
- PRQL
- QuasarDB
- Redshift
- RocksDB
- rqlite
- ScyllaDB
- SLOG
- Spice.ai
- SplinterDB
- SQLancer
- Stardog
- Summingbird
- Technical University of Munich
- TigerBeetle
- Tokutek
- Velox
- VoltDB
- WiredTiger
- YugabyteDB
- Akamas
- Anna
- Arrow
- BigQuery
- Brytlyt
- Chroma
- CockroachDB
- CouchDB
- Databricks
- Datomic
- Delta Lake
- Druid
- EdgeDB
- eXtremeDB
- FeatureBase
- Firebolt
- Gaia
- Google Spanner
- GreptimeDB
- Hudi
- InfluxDB
- Kinetica
- LeanStore
- Malloy
- Materialize
- Modin
- Mooncake
- Napa
- Noria
- OpenDAL
- OxQL
- Pinot
- PostgresML
- Qdrant
- QuestDB
- RelationalAI
- Rockset
- SalesForce
- SingleStore
- Smooth
- SpiceDB
- SQL Anywhere
- SQLite
- StarRocks
- Swarm64
- TerminusDB
- TileDB
- Trino
- Vertica
- Vortex
- XTDB
- Aerospike
- AlloyDB
- Arrow
- BlazingDB
- Chaos Mesh
- CockroachDB
- CrateDB
- Datometry
- Delta Lake
- DuckDB
- Exon
- FeatureBase
- Fluree
- GlareDB
- GreptimeDB
- Iceberg
- kdb
- LeanStore
- MapD
- Milvus
- Mooncake
- Neon
- OceanBase
- OxQL
- PlanetScale
- PRQL
- QuestDB
- RisingWave
- rqlite
- SingleStore
- Snowflake
- SplinterDB
- SQLite
- Striim
- Technical University of Munich
- TileDB
- Umbra
- VoltDB
- XTDB
- AirFlow
- Anna
- Azure Cosmos DB
- Bodo
- Chroma
- Confluent
- CrocodileDB
- Datomic
- Dolt
- DVMS
- eXtremeDB
- Featureform
- FoundationDB
- Google Spanner
- HarperDB
- Impala
- Kinetica
- Litestream
- MariaDB
- Modin
- MotherDuck
- NoisePage
- OpenDAL
- ParadeDB
- Polaris
- Qdrant
- RavenDB
- RocksDB
- SalesForce
- sled
- Spice.ai
- SQL Anywhere
- SQream
- Summingbird
- TerminusDB
- TimescaleDB
- Velox
- Vortex
- Yellowbrick
- Akamas
- ApertureDB
- Berkeley DB
- Brytlyt
- Citus
- Convex
- Databricks
- dbt
- Dremio
- EdgeDB
- FASTER
- Feldera
- Gaia
- GoogleSQL
- Heron
- InfluxDB
- ksqlDB
- LMDB
- Materialize
- MonetDB
- MySQL
- Noria
- Oracle
- Pinecone
- PostgresML
- QMDB
- Redshift
- Rockset
- Samza
- SLOG
- SpiceDB
- SQL Server
- Stardog
- Swarm64
- TiDB
- Tokutek
- Vertica
- Weaviate
- YugabyteDB
- Alibaba
- APOLLO
- BigQuery
- Cassandra
- ClickHouse
- CouchDB
- DataFusion
- Debezium
- Druid
- EraDB
- Fauna
- Firebolt
- Gel
- Greenplum
- Hudi
- Jepsen
- LanceDB
- Malloy
- MemSQL
- MongoDB
- Napa
- NuoDB
- OtterTune
- Pinot
- PostgreSQL
- QuasarDB
- RelationalAI
- RonDB
- ScyllaDB
- Smooth
- Splice Machine
- SQLancer
- StarRocks
- Synnada
- TigerBeetle
- Trino
- Vitesse
- WiredTiger
Nov 8
2021
[Vaccination 2021] Vertica – High Performance Over Varying Terrain (Stephen Walkauskas)
- Speaker:
- Stephen Walkauskas
- System:
- Vertica
- Video:
- YouTube
Vertica is an OLAP database, originally designed when a "beefy" server had 16GB of memory and 8 CPUs, and a 5TB data warehouse was considered to be HUGE. A lot has changed since then. Though CPUs have gotten only a bit faster there are more cores on a die. Applications are commonly run in virtualized environments these days. Data volumes... Read More
Sep 23
2019
[DB Seminar] Fall 2019 DB Group: Stephen Walkauskas (Vertica)
- Speaker:
- Stephen Walkauskas
- System:
- Vertica
You wouldn't run your application on the cloud because it is the cool thing to do. You'd run it there because it makes sense to do so. In this talk you'll hear why some of our customers have moved to the cloud while others have not. You'll also learn how we overhauled Vertica's architecture to become one of the few analytics... Read More
Mar 19
2018
[DB Seminar] Spring 2018: Stephen Walkauskas (Vertica)
- Speaker:
- Stephen Walkauskas
- System:
- Vertica
In the beginning there was a DBMS, a flexible piece of software that could be used for OLTP and OLAP workloads. When transaction throughput increased and data sizes grew the database needed to be split into two, each instance optimized for a particular workload. And so it has been ever since and the distance between the two systems has increased,... Read More