3 ms·
Can someone ELI5; deploying CRDB to AWS ec2 instances as beneficial over, say, redshift? Or are they completely different solutions? How easy is deployment/sca
by samstave 9y ago
Can someone ELI5; deploying CRDB to AWS ec2 instances as beneficial over, say, redshift? Or are they completely different solutions?
How easy is deployment/scaling/sharding with cockroach?
Aside from cost, where is the best use case for cockroach over anything else??
- korzun 9y agoI'm sure somebody else will nitpick this, but on a high level it's cost and control.
- manigandham 9y agoThere are 2 distinct use-cases: OLAP (data warehouse) vs OLTP (operational database). If you want a data warehouse to run SQL analytics over lots of data, stick with RedShift, BigQuery, Snowflake, MemSQL, MapD that use column-stores, vectorized operations, compiled queries and other features for fast performance. Also more options like Apache Drill, Dremio, SnappyData, MapR DB,... if you want SQL but over unstructured/random files stored somewhere. For an operational database to hold your core active data and to do small/mid-data analysis, CRDB is an option along with PostgreSQL, MySQL, MariaDB, SQL Server, and others. Advantage is cloud-native and distributed architecture so you can get high-availability, multi-master, and easy scaling out of the box, even across multiple data-centers. All the other traditional RDBMS either don't support this or require 3rd-party software to come close, although some will never match the same level of distributed functionality. In exchange, CRDB doesn't support the same performance, data types, and rich feature set of a single node PostgreSQL, for example. If you can tolerate downtime, need complex SQL statements, or already have solid tooling with the existing systems, then stick with them. If you're running a globally distributed app, or a new app that can work with simpler SQL statements, or need availability and scaling with less work, then CRDB is a good fit. If you're looking for something in the middle, then CitusDB (postgres extension) allows for automatic sharding across multiple instances. Keep most of the PostgreSQL functionality with single-region horizontal scaling, but more work and complexity without the distributed features of CRDB.