In a typical database, you have many workloads running at the same time. Each workload type dictates a different acceptable level of latency and throughput. For example, consider the following two workloads:
- OLTP (Online Transaction Processing) – backend database for your application:
- A high volume of requests
- Fast processing
- In essence – Latency sensitive
- OLAP (Online Analytical Processing) – performs data analytics in the background:
- A high volume of data
- Slow queries
- In essence – Latency agnostic
Using Service Level CQL commands, database administrators working on ScyllaDB Enterprise can set different workload prioritization (level of service) for each of these workloads without sacrificing latency or throughput. Also, each service level can be attached to your organization’s various roles, ensuring that each role is granted the level of service they require.
This lesson will cover:
- The evolving requirements for operational (OLTP) and analytics (OLAP) workloads in the modern datacenter
- How ScyllaDB provides built-in control over workload priority and makes it easy for administrators to configure workload priorities
- The impact of minimizing integrations and maintenance tasks, while also shrinking the datacenter footprint and maximizing utilization
- Test results of how it performs in real-world settings.
Read more about Workload Prioritization in the documentation and this blog post.
Note that this feature is available to ScyllaDB Enterprise users only.