Tag: cloud

It’s snowing here on New Year’s Eve 2017 as I sit here in Northern Virginia, reflecting on the multitude of things that crammed themselves into the past 364 days. Turning the lens to Rubrik, I thought about all the features, enhancements and team members we added this year, and I wanted to take a moment to highlight my favorites. I think they’re pretty spectacular, while also being merely a few peaks that crested this year’s clouds.

#1: Cloud Cluster for AWS and Azure (BrikOS 3.2)

Rubrik Cloud Cluster was the culmination of a dream. It is the feature that truly transformed vision into reality. Rubrik’s tagline is “Cloud Data Management”, but to me, it felt shallow…nominal when that was limited to cloud archive (“CloudOut”) for long-term retention. Cloud Cluster changed everything.

It brought the same beautiful software stack to a highly flexible cloud platform (two, in fact: AWS and Azure), made protection of cloud-native applications possible, cloud mobility real, and terrestrial-free ascendance tangible.

Like the AWS and Azure clouds in which it runs, Rubrik Cloud Cluster is a subscription-based model with a low entry threshold, granular scale-out expansion (1TB at a time), and lean resource design. Contrary to industry collateral, “cloud” isn’t free, so the architecture choices we make should be conservative in their approach. We can’t afford to just lift-and-shift our resource demands and expect customers to pay the price for that laziness. That’s just one of the reasons I like Rubrik Cloud Cluster.

#2: The Ranger Team (January ’17)

2017 was an year of immense growth across all teams in Rubrik, but one team in particular was born near the beginning. The Rangers. At least one New Hire Bootcamp misunderstood the name to mean Park Rangers which brought more than a few laughs and groans on our part (especially in light of the mountains, river, and font, Smokey the Bear-style, in the PowerPoint slide). The true alignment and tribute is to the Army Rangers.

The Ranger team members are the blasting caps to the dynamite of Rubrik’s API-first architecture. They unlock the incredible potential of a platform entirely exposed via RESTful APIs.

Customers and partners are all over the spectrum on their DevOps journeys, but most have initiatives at some level of the organization to eliminate repetitive processes, introduce self-service capabilities, and enable cloud mobility. Rangers leverage languages like Python, Ruby, and PowerShell* to streamline workflows, aggregate analytics, and tie Rubrik into other ecosystem products.

Here are just a few examples of Ranger projects in 2017:

(*with some internal debate as to whether this is actually a language… :)



This afternoon when I saw @scott_lowe‘s tweet about the attack on Code Spaces, I was shocked. The injustice, violation, and unrecoverable impact of the event hit hard.  That might seem odd, since I frankly didn’t know Code Spaces existed a moment earlier. But like anyone who doesn’t want to see work lost, especially on such a vast scale, I sympathized deeply with the customers who lost code and the Code Space operators who lost their livelihood. Someone burned their digital house to the ground.

After reading the account on www.codespaces.com, I began processing what it means to the cloud community. What should we learn about our dependence on Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), and Infrastructure-as-a-Service (IaaS)? Code Spaces thought they were safe with highly available cloud services, snapshots, and off-site backups…