Tagged in

CDM Series

Rubrik -  - Superior Architecture for a Cloud-Native World

General Tech

Superior Architecture for a Cloud-Native World

If there’s anything that years of consulting with enterprise clients has taught me, it’s that the world of technology continues to accelerate through iteration after iteration of new architectures, models, and solutions at a pace that is difficult to grasp. We previously lived in a world where all applications resided on bare metal, and waterfall projects took years to release. Now, the rules of small steps and cloud-first are percolating throughout the minds of cloud architects, driving innovation. As Rubrik’s Chief Technologist, I’ve applied a lens to my experiences as an architect to really scratch the surface on this whole cloud data management ideal in an exploratory series of blog posts. In a nutshell, being cloud native, entirely API-driven, infinitely scalable, having instant data access, and, most importantly, being software fueled are the ingredients necessary for moving the needle in the stagnant world of data protection. The Road Traveled Thus Far Two years later, one only has to look so far as incumbent solutions using yet another coat of paint to hide long-tailed technology debts to see the short, dismal future ahead when compared to newer ways of thinking. By wiping the technology slate clean in an effort to make backup…
Rubrik -  - Converged Data Management Unwrapped – Cloud Native


Converged Data Management Unwrapped – Cloud Native

Intelligently placing data into a variety of different formats and across geographical locations is non-trivial. With data protection, however, this isn’t just a nice to have; it’s often a functional design requirement. Doing so provides layers of safeguards against data-specific failures as well as local or regional catastrophes. In this fifth and final deep dive series post, I’m going to pick apart how Converged Data Management offers a truly Cloud Native experience for data protection workflows, and how that differs from the traditional approaches. There’s a fundamental difference between adapting a platform to take advantage of cloud data services, such as public object storage with Amazon S3, versus natively making it part of the platform. This difference can be extrapolated into one metric – simplicity. The amount of complexity that surrounds a platform drives greater inefficiencies and increased chances for error. Additionally, the base foundation of a platform ultimately dictates what features and properties are available for a long-term strategy. Without re-writing the platform from scratch – which is something largely avoided in the enterprise market – the choices are limited. After all, the spin-out and spin-in model used by large corporations to innovate doesn’t exist without reason. In the…
Rubrik -  - Converged Data Management Unwrapped – Instant Data Access


Converged Data Management Unwrapped – Instant Data Access

Now that the Rubrik team has returned from an energizing trip to VMworld Barcelona and TechTarget’s Backup 2.0 Road Tour, it’s time to peel the onion a bit further on Converged Data Management in the fourth installment of this deep dive series. In this post, I’ll put the magnifying glass up against Instant Data Access – which is the ability to see and interact with data in a global and real-time manner – to better understand why it’s a critical property in the architecture shown below: First, let’s take a step back. There’s a lot of hemming and hawing on the Internet about data lakes, big data, the Internet of Things (IoT), and so forth. The rub is that data is growing (exponentially), is largely unstructured, and there’s no way to put our hands around it in any meaningful way without machine learning and a plethora of automation. ImageNet is a great example of this in a real world, practical format. This has led to some really nifty architectures being crafted to deal with large data sets and a rise in the popularity in storage systems that are eventually consistent, such as object storage clustering, rather than strongly consistent as typically…
Rubrik -  - Converged Data Management Unwrapped – API-Driven Architecture


Converged Data Management Unwrapped – API-Driven Architecture

Welcome to the third post in the Converged Data Management series: API-Driven Architecture. To best understand how this property impacts the modern data center, it’s important to take a step back and view how today’s services – meaning the various number of servers that construct an application offered to the business or its clients – are created, consumes, and retired. This is often referred to as lifecycle management.As a service is instantiated, there are a number of lifecycle milestones to reach. These include the details needed to request a service from a portal or catalog, the provisioning tasks to build the service, various care and feeding events while the service runs, and ultimately the retiring and archival aspects of the service. More often than not, these milestones are wrapped into various orchestration engines and front-ended by a Cloud Management Portal (CMP) for administrative and tenant based consumption. In other scenarios, there are still automation workflows being utilized by way of point-and-click scripts and customization tasks. An API-Driven Architecture comes into play as IT professionals work to progress a service through the various lifecycle milestones along with other third party tools and infrastructure stacks. As technical teams attempt to piece together…
Rubrik -  - Converged Data Management Unwrapped – Infinite Scalability


Converged Data Management Unwrapped – Infinite Scalability

In the second part of my series on Converged Data Management, I’m putting another property under the microscope – Infinite Scalability. The underlying premise is that the fabric that is providing data management can be deployed in a shared-nothing manner with a limitless architecture focused on linear growth. Woah, what does that all mean?Let’s pick these ideas apart, one by one. A shared-nothing system is one built of a series of nodes that have no dependency upon each other. If a node fails, or parts of a node fail, the fabric remains healthy and operational without any negatively impacting penalties. Ideally, this architecture is expanded beyond the node itself, expanding out to the enclosure, rack, or even entire data centers. Contrast this to systems that are reliant upon dependencies and use alternative tricks to hide or protect them – load balancers, failover clustering, and so forth. If a failure occurs, performance suffers due to the need to ingest data into a central choke point – such as a master server, quantity of proxy nodes, or a database instance. Availability is also put at risk, especially considering that most components in a dependency chain have only a single failover counterpart because of…
Rubrik -  - Converged Data Management Unwrapped – Software Converged


Converged Data Management Unwrapped – Software Converged

As a technologist, I find a certain amount of joy comes from learning about what’s new in the market. This could be as simple as a new code or hardware release for a solution that has been around for a while, driving me to absorb the new features. Or, on the other end of the spectrum, it could be an entirely new way of thinking about how to tackle a challenge within the data center by learning from startups who are looking to shake things up with an interesting idea. A common pain point is figuring out exactly what it is that the young company does, as often the technical bits get blended in with a bunch of marketing jargon and buzzwords (see my buzzword bingo parody video) that dilute the transfer of information. In this series, I’m going to get a little nerdy about a relatively new term that is hitting the market, Converged Data Management, and dive into the five important properties that build into this solution. The goal is to provide a clear view into each feature with real meat on the bone, along with why and how the solution is important in today’s modern data center,…