Nagananda Anur

An example, that's what I was saying in the beginning, right?

I'm a solution developer.

I'm a DevOps solution developer or an IoT solution developer.

I need storage.

So all I do is that, you know,

Maybe I call an API, just give the storage, and then I build my solution around it, and when I'm done, I say, you know, delete storage.

That's what I do.

So, essentially, today, we expose these constructs.

We still call file share, latency, and those kind of things.

We got to, in the long run, we got to abstract it even further to the level where

end applications doesn't even know that you know there's a netapp platform behind it all they have to do just they can just build solution developers can build solutions without even knowing storage and then what it does is it gives capability for netapp to position the netapp platform to the various workloads we haven't traditionally been doing it could be a devops workload io code or any analytics workload

It doesn't matter because people are building solutions.

Partners are building solutions around this because it's so easy for them to build.

Just to give you a sample example, recently there was a hackathon done by one of the NetApp teams, and they had several teams building solutions, and then the feedback what we got was, oh, God, it's so easy to build any solution using your APIs because

They just don't have to know anything about data platform.

All they have to know is just give you storage and, you know, they get storage.

So, essentially, it's almost like an infrastructure as a code.

If you look at it, right, today, people build solutions, I guess, stable platform like Apprenda and Cloud Foundry and those kind of things, you know?

Essentially, the reason is because of the stable API set and then,

You know, we can just go in the long run.