Jason Lopez: Kutchibhotla says there are four properties of a database. He uses the acronym acid, shich stands for atomicity, consistency, isolation, and durability.
Bala: That means that you cannot afford to lose the data. Let's say you put $10,000 in the bank, that transaction is committed forever. If I take $10,000 but not credit the other account, then there is a problem. Those are what we call the relational databases with certain type of what I call acid properties: atomicity consistency, isolation, durability. That means that you cannot say that, “Hey, I know what the transaction is committed, but I don't know. I can't commit it. I don't know.” You cannot say that for that database.
Jason: He was born in India and grew up amid the development of the country’s IT boom. He says being an engineer — a good engineer — is something many aspire to in a very competitive landscape.
Bala: I love computer science for sure and more so databases. And that's how I've been traveling for the last 20 years with databases. All the way from my master thesis, which is an object database kernel. And that's how I got into my first job in India. By the way, the company was managed by Ben Trainer who runs the Google cloud and then from there moved to Oracle about 14 years back and then doing all the database management stuff there.
Jason: Databases are in Kutchibhotla’s DNA. He thinks a lot about the future of the technology and lately his focus has been on virtualizing databases.
Bala: Virtualization was a trend about fourteen years back. But everyone moved to cloud and database virtualization has not fully taken off. So you need cloud like simplicity.
Jason: Virtualizing a database requires more than slapping one into the compute node.
Bala: Why do you do virtualization, right? Like to consolidate. But the struggle that I see is databases need to be virtualized at the data level to really reap the benefits of virtualization. If you create more database compute nodes, but the data is not virtualized, your pain points are moving towards data. So when you're trying to deal with cloning of the data, but just because you have compute node virtualization but the databases are not virtualization then you're actually creating bigger problems. When we're talking about honest database virtualization, the innovation has to happen on both sides. The compute side as well as the data side.
Jason: This question of innovating on the data side is one reason Kutchibhotla decided to bring his vision to Nutanix. The company made its name simplifying storage and making infrastructure invisible. He wants to revolutionize database ops in a similar way and create a product release using the cloud. The project is called ERA.
Bala: ERA I would say a true database virtualization to start with and then extending it to more like cloud like experience for database as service. So we kind bring the true database. virtualization when I said true database, virtualization and how do you do snapshots, how do you manage your data, not just running your database servers in your virtualized compute environment.