When working with a customer, I have a belief that cloud is simply two things: Cloud is where your data lives. Cloud is where your applications run. From there, it’s your technical team’s job to collaborate and deliver services and a service delivery model that aligns with your business’s needs.
The way companies get off the ground has often fascinated me. Companies start with an idea, but building a company requires really hard work to turn that idea into a product that is consumable by a customer. That hard work costs money. Where does it come from? This post will use a recent startup, “Rubrik,” to walk through how the process works.
Rubrik calls themselves the “Cloud Data Management Company”. This provoked Eric Shanks to ask the question, “What are the characteristics of a cloud product?” This is a very difficult question to answer and leaves too much room for ambiguity. This lack of formal definition creates the opportunity for almost any product vendor to call their product “Cloud Ready.” In this article, Eric sets out some definitions to see if Rubrik truly is a cloud solution.
Jeff Bezos has always advised to let your customers guide how you develop a product. In fact, one of the core missions of Amazon is to ensure, “every day to make every important aspect of the customer experience a little bit better.” This is clearly what you see when peeling back the onion on the data management company, Rubrik. Like the winged monkeys marching in the “Wizard of Oz”, Rubrik has charted a course in the data ocean that’s taken them from a scrappy startup with a very intriguing scale-out based value prop, to a clear contender for Enterprise data management needs. While there has been a lot of buzz around features and functionality within the product, I’d like to take a step back to analyze how I feel they hit the mark for enterprise deployments today in the first of a few blog posts focusing on the product directly.
Rubrik’s that new backup solution that makes traditional backups a snap – pun intended. I’m a former Systems Administrator and there was absolutely nothing I hated more than managing backup jobs and reviewing why the backups failed all the time. I viewed backups as that thing I had to do each day as fast as possible, so I could get to the interesting parts of being a Systems Administrator like fielding support calls and patching servers. Hey, I was young and it was a phase I was going through, back off.