Blog Archives

DriveScale Composable Infrastructure: Elastic and Efficient Resources for Modern Workloads

Modern workloads such as Hadoop, Kafka and machine learning are demanding in terms of the volume of data that must be processed, the speed at which that data much be processed, and the fact that their capacity and performance requirements

Tagged with: , , , , , , , , , , , ,
Posted in Blog

Is NVMe Enough for Efficient Hyperscale Data Centers?

Hyperscale architectures typically sacrifice resource efficiency for performance by using direct attached storage instead of a shared storage solution. That lost efficiency though, means the organization is spending money on excess compute, graphics processing units (GPUs) and storage capacity that

Tagged with: , , , , , , , , , ,
Posted in Blog

The Problems with Hyperscale Storage

Direct attached storage (DAS) is the default storage “infrastructure” for data intensive workloads like Elastic, Hadoop, Kafka and Splunk. The problem, as we detailed in the last blog, is using DAS creates a brittle, siloed environment. Compute nodes can’t be

Tagged with: , , , , , , , ,
Posted in Blog

The Problems that Scale-Out Architectures Create

Data intensive workloads like Elastic, Hadoop, Kafka and Splunk, are unpredictable, making it very difficult to design flexible storage architectures to support them. In most cases, scale-out architectures utilize direct attached storage (DAS). While DAS delivers excellent performance to the

Tagged with: , , , , , , , , , , , , ,
Posted in Blog

15 Minute Webinar: Composing Infrastructure for Elastic, Hadoop, Kafka and Cassandra to Drive Down Cloud Data Center Costs

Hyperscale applications like Elastic, Hadoop, Kafka and Cassandra typically use a shared nothing design where each node in the compute cluster operates on its data. Hyperscale architectures, to maximize storage IO performance, keep data local to the compute node processing

Tagged with: , , , , , , , , , ,
Posted in Webinar

Simpler is Better – Solving Rack Scale Storage Problems – DriveScale Briefing Note

The storage infrastructure for multi-rack scale applications like Hadoop Spark, Cassandra, and CouchBase, are typically built using directly attached flash-based storage instead of a shared flash array. The motivation for using direct-attached storage (DAS) is simple. Media inside a server

Tagged with: , , , , , , , , , ,
Posted in Briefing Note

Using Software Composable Infrastructure for RackScale Application – DriveScale Briefing Note

Rackscale applications like Hadoop, Spark, Cassandra and others count on using commodity storage that is typically internally available to the node processing the data. The idea is to reduce storage costs and network complexity. The problem is these designs create

Tagged with: , , , , , ,
Posted in Briefing Note

Breaking Down Hadoop, Spark, Cassandra Silos – DriveScale Briefing Note

The storage architecture of most next generation applications, like Hadoop, Spark and Cassandra, leverage local, direct attached storage to avoid excessive storage traffic on the network and keep costs down. While this architecture does accomplish its goals, it also re-creates

Tagged with: , , , , , , , ,
Posted in Briefing Note

Disaggregated Hadoop Clusters – DriveScale Briefing Note

Web-scale applications are designed to run on dozens, if not thousands, of small commodity servers, which expect direct-attached storage. As a result storage performance and capacity is directly tied to the purchase of more compute (servers). Over time almost every

Tagged with: , , , , ,
Posted in Briefing Note