SlicingDice Documentation

SlicingDice - The All-in-One Solution Documentation

Welcome to the SlicingDice documentation. You'll find comprehensive guides and documentation to help you start working with SlicingDice as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Guides

What SlicingDice is good at

First time checking our docs? You might want to start with the right foot by reading our Documentation Guide first.

In this section, we will introduce some use cases which SlicingDice is good at, if your use case is similar to the ones presented here SlicingDice will probably be greatly helpful to you.

Analytics queries correlating many columns, where SQL databases are too slow

Usually, relational databases struggle with queries that JOIN many tables. Our state-of-the-art database engine allows anyone to run queries with multiple columns and receive the results really fast. As an example, SlicingDice can find out without problems which users accessed sports, news and video-games pages more than 5 times in the last week, even if your website is accessed by millions of users every day.

Big data applications

From day 1, SlicingDice was built to handle billions of rows and thousands of queries without bottlenecks. For applications with large data volumes, SlicingDice will be much faster than the well-known relational or NoSQL databases.

Companies that don't want an entire team to manage data infrastructure

Being a Data Warehouse and Analytics Database as a Service means you don't need to maintain your own infrastructure. Especially in small companies or academic projects, this can save a lot of time and money which can be better applied in your own business.

Applications where the amount of data is much larger than the number of columns

Since one of our two pricing models is based on the number of columns you have on your database (pay-per-column), you will be able to store and query data in a pretty cost-effective way. For example, industries placing sensors and other Internet of Things devices in their factories won't be charged by the amount of data they send to SlicingDice.

Large amounts of temporal data

SlicingDice is perfect when you have lots of temporal data. For instance, you might be interested in monitoring your servers and check their performance and stability in near-real-time. To achieve that, you need to store every server metric product in the last 24 hours and check the average performance and possible outliers.

When you don't want to have a server only to run databases

In some use cases, such as Internet of Things projects, running a database server is undesirable, even more when the data being processed isn’t large. Also, renting a server is usually more expensive than SlicingDice's minimum charge of $ 1.00.

Nevertheless, no database is able to fit every possible use case on Earth, neither does SlicingDice.
Check our section on current SlicingDice restrictions to understand what we don't support yet (but be sure we're working hard to overcome these limitations). If you need special arrangements, simply talk with us.

Still not sure if SlicingDice is a good fit for your needs? Talk to our developers right now.