We dump a lot of our data, such as every entry created with respect to when a user rides a scooter, every record gets updated to ScyllaDB. It is used as a single source of truth and it manages massive data. We support various business use cases, including mobility, where data about driver allocations get updated. We currently have twenty clusters and more than one hundred nodes.
We use ScyllaDB, a NoSQL database, as a distributed system to store customer data. My last project was in telecommunications, where we stored caller information like phone numbers, names, and scam tags for a scam call protection service. We handled insert, update, and other operations since the back-end AI system needed daily data inputs. We ran scripts to add the data to ScyllaDB across two AWS regions: US East and US West. One Scylla node handled requests, synchronizing data with its peer nodes. During the POC phase, we testedperformance, read/write operations, and latency and chose the right consistency levels for ourneeds. After that, we moved to production.
We use it as a non-relational database. We use it to store two things: * To store audit log data and * blob data, including images with different sizes, like 200kb. We use it as an image database as well, such as user profile pictures and product catalog promotional pictures.
ScyllaDB is a very seamless product within C++ or something. So, it's faster and all that stuff. Even if it is all good, there is more need for marketing on their website than on the original thing. Now, if you are a big company, ScyllaDB is a good, robust product. It's a terabyte/petabyte kind of product. But your cost would be one-third or even less with ClickHouse, and it would be smoother and lighter.
Software Engineer at a computer software company with 1,001-5,000 employees
Real User
Top 5
2023-07-18T05:29:43Z
Jul 18, 2023
Our company currently uses Scylla for our products since we are in the process of migration from Postgres. Our company is reimplementing the user data pipeline and needs faster results. We found Scylla to be preferable for our use case from the alternatives we evaluated.
Scylla is used as a cache. Once the data is ingested into the product during the initial load, a version of it is stored in Scylla DB, and this is then used by the other transformation services to query and make updates during ongoing loads. That is, it is being queried by other services to make the updates whenever deletes occur.
ScyllaDB is an open-source, distributed NoSQL wide-column datastore (a highly scalable NoSQL database), known for its compatibility with Apache Cassandra, and for supporting the same protocols as Cassandra (CQL and Thrift) and the same file formats (SSTable). ScyllaDB is designed for high throughput and low latency, making it suitable for data-intensive applications. Its architecture allows it to deliver remarkable performance on a massive scale, utilizing modern multi-core servers...
We dump a lot of our data, such as every entry created with respect to when a user rides a scooter, every record gets updated to ScyllaDB. It is used as a single source of truth and it manages massive data. We support various business use cases, including mobility, where data about driver allocations get updated. We currently have twenty clusters and more than one hundred nodes.
We use ScyllaDB, a NoSQL database, as a distributed system to store customer data. My last project was in telecommunications, where we stored caller information like phone numbers, names, and scam tags for a scam call protection service. We handled insert, update, and other operations since the back-end AI system needed daily data inputs. We ran scripts to add the data to ScyllaDB across two AWS regions: US East and US West. One Scylla node handled requests, synchronizing data with its peer nodes. During the POC phase, we testedperformance, read/write operations, and latency and chose the right consistency levels for ourneeds. After that, we moved to production.
We use the solution for distributed systems.
We use it as a non-relational database. We use it to store two things: * To store audit log data and * blob data, including images with different sizes, like 200kb. We use it as an image database as well, such as user profile pictures and product catalog promotional pictures.
ScyllaDB is a very seamless product within C++ or something. So, it's faster and all that stuff. Even if it is all good, there is more need for marketing on their website than on the original thing. Now, if you are a big company, ScyllaDB is a good, robust product. It's a terabyte/petabyte kind of product. But your cost would be one-third or even less with ClickHouse, and it would be smoother and lighter.
Our company currently uses Scylla for our products since we are in the process of migration from Postgres. Our company is reimplementing the user data pipeline and needs faster results. We found Scylla to be preferable for our use case from the alternatives we evaluated.
Scylla is used as a cache. Once the data is ingested into the product during the initial load, a version of it is stored in Scylla DB, and this is then used by the other transformation services to query and make updates during ongoing loads. That is, it is being queried by other services to make the updates whenever deletes occur.