SNIA Experts on Data

SNIA Setting the Standard for Storage Innovation

November 29, 2023 SNIA Episode 5
SNIA Setting the Standard for Storage Innovation
SNIA Experts on Data
More Info
SNIA Experts on Data
SNIA Setting the Standard for Storage Innovation
Nov 29, 2023 Episode 5
SNIA

Philip Alsop, Digitalisation World Editor, interviews Dr. J Metz, Chair of the SNIA Board of Directors on the many ways SNIA is setting the standard for storage innovation. Listen as they discuss several new exciting innovations, including computational storage devices, DNA data storage and SDXI (Smart Data Acceleration Interface).

SNIA is an industry organization that develops global standards and delivers vendor-neutral education on technologies related to data. In these interviews, SNIA experts on data cover a wide range of topics on both established and emerging technologies.

About SNIA:

Show Notes Transcript Chapter Markers

Philip Alsop, Digitalisation World Editor, interviews Dr. J Metz, Chair of the SNIA Board of Directors on the many ways SNIA is setting the standard for storage innovation. Listen as they discuss several new exciting innovations, including computational storage devices, DNA data storage and SDXI (Smart Data Acceleration Interface).

SNIA is an industry organization that develops global standards and delivers vendor-neutral education on technologies related to data. In these interviews, SNIA experts on data cover a wide range of topics on both established and emerging technologies.

About SNIA:

Speaker 1:

Welcome to the SNEA on Data Podcast. Each episode highlights key technologies related to handling and optimizing data. You were listening to SNEA on Data Podcast SNEA setting the standard Restorage innovation. In this episode, philip Alsop of Digitalization World interviews Dr Jay Mett, chair of the SNEA Board of Directors, discussing several recent exciting innovations at SNEA. So SNEA.

Speaker 2:

You have just released a new set of standards around a new type of storage product with the title Computational Storage Devices, or CSXs for short. Can you just give us a bit of an insight as to what's going on there?

Speaker 3:

Yeah, absolutely. The idea behind computational storage is a little bit of an advancement of some of the things that have been happening over the last several years. Specifically, what we have been realizing as part of the industry trends is that storage and memory are starting to become somewhat similar, and if you can have memory and storage using similar semantics or the same semantics, there's no reason why you can't have compute right next to it and you can't have networking right next to it. So the ultimate idea here at the bottom line is that if you want to be able to do any kind of computing on data, it makes sense to have the computer as close to the data as possible. And there are a lot of scenarios where having data right at the computer processors makes a great deal of sense, because you don't necessarily want to move data from one place to the other if you don't have to. So even over a short distance, like you find inside of a server, any IO that you don't have to send saves quite a bit more IO in retransmissions, retiming and that kind of thing and, more importantly, it allows you to put the processing capabilities where it's needed most. So sometimes you want to have processing on metadata, sometimes you want to have processing on data itself, sometimes you want to have processing in the control plane, and so on. There's a lot of different processes that go on, but there's also a lot of different storage that goes on.

Speaker 3:

Not all storage is created equal. So what you want to do is you want to find the right tool to place the right job. What computational storage does is it gives you a series of options that allows you to do just that. I mean, for instance, right now people think of computational storage as a drive with a nice little processor on it, and while that's true, that is computational storage, that's not all it is. So storage is more than just data. It's more than just storing data. It includes all the protection that you have to have to make sure that you get the correct bit back that you asked for. It means that you have to have the services like encryption and compression and that kind of thing. It means you have to have the file systems being able to operate on All of these things. That all work together to make storage have a wide swath of responsibilities, and placing them where they're best used is what computational storage is all about. So it's the very beginning stages of what's promising.

Speaker 2:

And I'm wondering is that? I mean, everyone's been talking about the edge computing for quite a while. Is it one of the main drivers, or is that a happy coincidence that bringing computing storage together, which I guess is making, will make sense of the edge? Is it just a happy coincidence, or is it that people have been looking at and saying, hey, isn't this a good idea? That's one of the major benefits, or, as you've explained in many other places, it makes sense as well.

Speaker 3:

Well, it's kind of serendipitous. I don't think it was a coincidence and I don't think it was necessarily by design, but I do think that when you get technologies that happen to evolve along similar timelines, you're likely to find those kinds of intersections. Now, any kind of edge computing situation, whether it be automotive, whether it be mobile devices or edge of a data center all this IoT stuff that's been happening and just the sheer amount of information doesn't necessarily have to be sent somewhere to be processed, if it doesn't have to be. Some of it does. Sometimes you really do want to have massive collections of data to be able to do the kind of number crunching that a handheld device can't really do. But if you want to, let me give you an example of what some of the things you can do. So, for instance, in machine learning, where you actually have to transform the data to be able to process it, you can't just do analytics on object storage, not natively. You have to make the data transform so that the analytics engines can use it. Well, what we normally have to do without any kind of computational devices is you have to send it somewhere for that pre-processing to be done and then you have to run the models.

Speaker 3:

But that first step, that pre-processing element, could very well be done at the edge, so that you're not necessarily sending all that data over into a centralized location. So one really good example for that is facial recognition software for cameras. So if you think about the way that that would work, you have a centralized server that does the processing for facial recognition. The camera sends the feeds back to that central location, that application starts to do the facial processing and then it has to communicate with all the different devices. However, with a computational storage solution, you could run the facial net recognition right on the camera and then only send back the information that you wanted to find, as opposed to just sucking in the ocean and trying to find that small little bit that you're looking for. Being able to do that separation of duties is a major time saver, which of course saves processing power, saves cooling, saves network. Overall the long term it just does an awful lot of saving of energy and economics.

Speaker 2:

Okay, and then I mean you've been very busy so I'm aware as well. You've just published version I think 1.0, of the I'll have to read this computational storage architecture and programming models. So can you give us the background on that?

Speaker 3:

Well, in order to give vendors the general concepts that they want to use in order to develop a computational storage device, it helps to be able to understand A what it is, b what you can do with it and C how you can access it.

Speaker 3:

So what this does is it provides a model of computational storage that allows you to create different form factors that the nature of the relationship between a processor, the storage that it uses, the memory that it uses and the corresponding form factors come as a result of it.

Speaker 3:

The APIs is simply a way of having a programmer be able to access a computational storage device to operate it from any kind of host or remote location. Now, that's different than what's being done inside of the NVM Express group. By the way, demo will make it clear that there's a separation. So the model and the architecture and the APIs are being handled inside a SNEA and the commands for NVME are being done inside of NVM Express. So the NVM Express is a slightly more narrowly focused version. It's really focusing on the drives at the moment, not so much the arrays or the processors or any of the kinds of broader flexibility. Like I said, we're at the beginning stage of this, but NVME is responsible for their own command sets, their own theory of operation, which is outside the scope of SNEA. So we're working together with that organization to make sure that everything is aligned.

Speaker 2:

OK, and just for a little bit of understanding with both the things we've covered so far, is it vendors start producing these new types, the new ideas, and then you get involved if you're like referee, to come up with open stands that we're going to work to, or do you foresee or anticipate something coming along and then step in early, just for people to understand where does SNEA get involved at what stage?

Speaker 3:

Well, the ideas can come from anywhere. There really is no one way to start an idea, but the process of once an idea gets done, you get a couple of other companies or other members to think that yeah, that's something that's worth working on. And then, if you get a critical mass, they come together and they start to identify what is it that we should do to make this work for the long term, for the long haul, I mean? Ultimately, if you're looking just to have a solution that two vendors can work together, you don't need a standards body. But once you get beyond that, you start to realize that I need to make sure that if I'm going to get a computational storage device from vendor A and I'm going to get another computational storage device from vendor B, outside of the special sauce that they want to have to make it work, you kind of want it to be relatively similar in the structure, like the electric plug in your wall. You don't want several different plug sizes, you don't want several different plugs themselves. So at the very fundamental level you have to agree on what that's going to look like. Now that doesn't prevent you from being innovative by working to build on top of that.

Speaker 3:

But in this particular case, you have a couple of companies who are trying to develop computational storage models that they're interested in, and so they get together with other companies who want to do this and they kind of hash out the basics so that they can actually go onto the market and say I have this device, and then the customers and the administrators will kind of have a general idea of what you're talking about.

Speaker 3:

For example, in NVMe we started off with NVMe Express for PCIe devices, and the whole purpose was that if you want to have that kind of really fast storage device and you want to stick it into a PCIe slot, you don't want to have to rewrite a driver for every single thing that you want to put in there. Well, computational storage is the same way. You don't want to have to have a very specific solution for every single one that comes down the road Because, quite frankly, there are a lot of different possibilities and options and you've got to have some place to start with. So in this particular case, we actually have 52 different members who happen to have a very similar idea and they came together to start working on the specification.

Speaker 2:

OK, and in a slightly similar vein, I see that the DNA data storage alliance have become an associate member. Yeah, technically OK. So, and I'm just interested, I think there was a track on DNA storage in your recent Storage Developers conference. But again, for those of us myself include that maybe I'll sit too up to speed on that, what is it, and is it as exciting as I'm imagining it could be?

Speaker 3:

I think it is personally. I mean, I have to confess I'm no biologist, so I don't really understand a lot of the very specific things or chemist, I guess, is probably the best way to, I don't know. It's. It covers a lot of technical areas but, in a nutshell, one of the things that's been concerning a lot of people is the fact that we have just had an explosion of information in the last 10 years. Right, we've, we've, we've developed what we've, we have created more information in the last three or four years than all of human existence At the mind boggling.

Speaker 3:

You know, you know, it's just one of those. It's one of those weird things where you know the numbers stop me having any meaning but where we were doing long term retention and archiving of this data, it was reasonably straightforward. I mean, you have tape, you've got the hard drives, you've got other types of records that you can keep for the long term no-transcript. But this type of data, this amount of data, means you've got to really start thinking outside the box. You really have to start figuring out. What does it mean to have truly long-term archiving information that's going to last a very long time and going to be retrievable in the future. What DNA storage is trying to do is say look, the DNA molecule can actually act as a storage medium for that long-term. Now it's still in the very early stages.

Speaker 3:

What that means, and if you think about it from a very basic common sense perspective, you have to be able to access that DNA strand. You have to be able to encode it in such a way that's readable in 40, 50 years or 100 years or whatever it is. You have to be able to make the machinery that can do all that work. You have to be able to identify the standards of access, the software that's supposed to be, or what's it going to look like? What do you need? Because you're not going to read DNA the same way that you would read data off of a platter, for example. It's not exactly the block storage that we're used to with an SSD. All of these things need to be defined. That's where the DNA data storage alliance has been starting off, and what Sneo brings to this is the umbrella to be able to do that work in the atmosphere of a storage related context. We can provide the support necessary for them so that they can focus on the work that they want to do.

Speaker 2:

I'm a student of the storage industry for quite a while and I think it was a holographic storage was out there for a while. I think people were storing on glass as well at one point. I'm not sure whether those are still going, but they seemed a bit more pie in the sky. Do you think this is a real concrete thing that's going to happen, or is it still too early to actually work out whether it's going to have the impact that it might have?

Speaker 3:

Well, anytime you start talking about science fiction-like stuff, you always run the risk of it either petering out or hitting a roadblock that you couldn't have anticipated. I'm not sure what happened with holographic storage. I thought it was really interesting as a concept and I remember they were talking about this back in I think it was like late 90s, if I remember if they started it. And there's also molecular storage, which doesn't sound all that unrelated. I can't say for sure because I really don't know anything about that, but I do think that once you hit a critical mass of interest and the amount of investment that goes into it's not just in terms of money but human investment and being able to put this together, eventually the need will outweigh the risk and you'll have to get something to work over time.

Speaker 3:

We just simply don't have the capacity in our existing storage media to handle the influx of data that's coming in for any kind of long-term science, especially when you start to think about the skill and shriveless of privacy and retention and the need to hold on to all this data for regulatory purposes. So you wind up with this kind of external influence that would perpetuate this and an internal motivation to keep going. I think that, from what I've seen from the people and the companies that are involved in DNA storage, that there is a critical mass of people who are looking to make this work, and work successfully. They've organized themselves in such a way that they're obviously in this for the long haul.

Speaker 2:

OK, so that was, I say, one of the main themes, I think, at your Storage Developers Conference. I think the other tracks were around SRM or, dare I say, old friends, storage Resource Management although I'm sure there was something new to say about that and also cloud storage. So can you just give us I think you've just come back from there, but can you give us just a bit of a highlights of what those topics brought to light, if you like?

Speaker 3:

Well, yeah, sure. So let's talk about the management for a second, because you're right, it is a major issue that needs to be resolved. I think, in general, people tend to think of management as an afterthought when they're promoting storage. Because, let's face it, management really isn't sexy unless you're an administrator, and it makes your life easier. The end user is the one that's really going to get excited about this kind of thing, like the same way that an accountant would be excited about a spreadsheet, just to make the lives easier.

Speaker 3:

Well, management in the storage world has been needing to evolve to keep up with the changes that are going on, because what used to be the storage management of choice, which was something called SMIS, was designed to be around large arrays, centralized storage devices. Well, since that time, we've actually moved into other forms of storage, including disaggregated storage, ethernet, attached SSDs, ebofs, those kinds of Ethernet bunch of flash, and you've got to be able to provision those somehow. So the DMTF has its Redfish specification for server management, and so SNEA has a relationship with DMTF to create the swordfish extensions for Redfish. So swordfish is really Redfish, but for storage. So, if you want to manage these new types of devices, these NVMe, ethernet, attached SSDs or the eBofs or the disaggregated storage.

Speaker 3:

Swordfish will allow you to do this without having to reinvent the wheel, especially if you're already using Redfish for your servers. So if you have a storage server, which is basically a box full of sword devices, you can manage the whole thing with one basic management structure. And so we just released the latest version of swordfish as an ISO specification, and that just happened a couple of weeks ago, I believe. So we are heavily promoting the compliance testing programs for Swordfish. I think before we were trying to find the overlapping time because companies still use SMIS, but the development for us has shifted over to Swordfish, but it's never a clean transition from one to the other. What we've done this year is that look, this is where we think we need to go. We're spending a lot of time promoting and helping people understand how to use Swordfish to get the best management structure for their devices.

Speaker 2:

Cloud storage again. That's been around for a while. Was there anything particularly new there, or was it just more of the same, do I say?

Speaker 3:

Well, I have to confess, when it comes to the cloud storage, it came at a conflict of some other things that I was doing and I didn't get a lot of chance to really spend it. But the cloud storage is in and of itself is rather vague. You've got the storage devices, for instance. You've got the storage access. You've got the storage protocols, object stores, those kinds of things. I think that one of the things that is striking the cloud storage folks is that it's more than just more performance.

Speaker 3:

The issue with cloud storage in general is that you've got to go through an awful lot of layers to get to the storage from the cloud applications. What's been happening, especially recently, is that when you wind up with these applications that don't quite work the way a double-arbit wants it, they just build another layer of abstraction. I don't know if you've spent a lot of time going through all of the different layers of how to get a single application in the container to talk to its actual storage, but it's impressive how many layers there are. From an application's perspective, all they want is more raw power. They want more raw processing power, and so you eliminate all of the benefits and features. That is built into the protocol that's built into the devices, that's built into the processors.

Speaker 3:

Excuse me, what we were talking about in part was well, how do you capitalize on those? You're just ignoring a lot of things that could make your life easier, but most software developers really don't know about it. We were tying the strings together and hopefully aren't knots but we're trying to get them to start paying attention to the idea that there are things that you can do in storage that you may not necessarily be aware of because it's been hidden from you for so long. I hope personally that the developers and the software authors and the people who are in the living in the container world can realize that we've been doing this for a long time and can help. We can actually help you get the performance you need without just waiting for the next Uber processor from AMD or Intel. I think that, ultimately, what you want to do is you want to work smarter, not necessarily work harder, and that's where the cloud storage stuff really tends to shine.

Speaker 2:

Okay, it sounds as if you're very busy as an organization, but are there any other things on the road map we need to be aware of at this moment in time, or with what we've discussed? Is that keeping you pretty much fully occupied?

Speaker 3:

Well, as a chair, I have a desire to see the organization expand and grow in terms of the strength of its quality of offerings, not necessarily become bigger, but definitely become much more resilient and reliable for those who are depending upon us. So, for example, we're talking about the cloud storage stuff. One of the really, really interesting things that's happening is something called SDXI, which stands for the Smart Data Accelerator Interface, and effectively what it does at a very high level is it actually going back to the cloud storage conversation? It does that very thing that we were talking about with the application being able to use the smarts of the hardware. So let's say, for example, if you were to, let's say you have a storage VM and a regular VM and you need to move the data from one back to the other. In an environment with a lot of layers of abstraction, you effectively have this Pachinko chip that has to go all the way down to the hardware and all the way back up to the other virtual machine. But with SDXI, what you can do is you can tell the hardware, using a strict API, to effectively do the data movement from one memory location to another privileged memory location. Once you set up the privileged relationship. It'll just happen because the hardware can do it for you. You don't have to go through all of these layers of APIs to get that layer to do this and then that layer to do this and then pass the copy down all the way down to the hardware and then back up again. Just tell the hardware to move it, hardware moves it and you can really speed up and accelerate that data movement.

Speaker 3:

Let's say you want to zero out a location, a memory location. You don't need anywhere. These containers are ephemeral. You want to zero it out and make it nice and secure and start all over from scratch. Tell the hardware to do it. Don't just have to go through and cycle through the software. To have it done in that fashion Can save up an awful lot of time. There's work that's being done inside of SNEA to help assist that in a vendor neutral way, so that you're not dependent on any one particular type of hardware vendor, any type of software vendor. It's all basically part of an open standard for that kind of data memory movement.

Speaker 3:

That's one example what we've already talked about Swordfish, we talked about computational storage. We've talked about some cloud security and data privacy are a big part of it. I think energy efficiency is as well. So one of the things that's happening all over the world is the movement of government regulations and, as most people know, either intuitively or through experience and if it's from experience, I share their pain but government regulations are not always consistent and so oftentimes you'll come across very strict rules that conflict with each other.

Speaker 3:

So one of the things that we're trying to do, especially with the energy efficiency stuff and especially with the data privacy and protection, is we're trying to make that approachable for people. So we have something called the Green Storage Initiative, which allows companies to run compliance of their machinery against the energy star requirements that are here in the United States. There are some EU and UK mostly the EU, not more than the UK work that is being done for handling data location, where the data actually gets stored, how it gets stored, what the energy needs to be for those. We're working with those different governments as well as the United States, to make sure that it's easy for vendors to comply, or easier. They'll always build a more interesting regulation. But those are the kinds of things that we're doing that aren't necessarily sexy, but the penalties could be rather severe.

Speaker 2:

Yeah, okay. And yet mention of energy efficiency. I mean, the world is heading towards net zero at varying paces depending where you are, what industries, what, I suppose, responsibility do you think SNEA has as an organization? You mentioned the energy efficiency, but that sounds as if, at least at one level, you're responding to strict sort of government requirements. But more generally, the industry, are you helping them move towards that sort of target? And in terms of data, I know obviously your vendors are there to provide storage and there's more and more data as you discuss being produced ridiculous amounts. Do you think you have any sort of requirement, obligation, to start some kind of debate or enter into the debate as to should we just be storing all this information forever and ever, or do we actually need to start thinking about the life cycle of data a bit more seriously? Would you just some thoughts on what your association's role is in the sustainability debate?

Speaker 3:

That requires a shift in our focus a little bit, and it's a shift we've been talking about. So from my perspective, I have always taken the stance that, as the quote unquote storage experts, I think we have a moral responsibility for being able to lend that experience into the world, where these types of regulations can have deleterious effects on whether or not you're storing the data or whether or not you're storing the data properly. And I do think that different governments may have the best intentions, or they may not you never really know but a lot of them are making decisions that don't make an awful lot of sense from a technical perspective. And I think that SNEA is an organization that has a moral duty to be a friend of those courts, to be able to offer some recommendations and some guidance. We're not a lobbyist organization, so we don't go onto K Street and we don't meet with anybody in the governments, but we do send out statements and white papers and position papers for certain things, when probably we've done a few of them this summer, as a matter of fact, for some of the security things that have come out with regards to some of the changes that have been going on For standards.

Speaker 3:

It's really kind of funny because you have this overarching umbrella of accountability, right? So when you talk to somebody who's in standards, they get very mired in the word shall or the word should and it seems like minutia to the layperson. But that becomes the basis for a lot of this regulation, right? So if the regulation says you shall do something, or you should do something, or you must do something, you're never gonna see something that's like, well, you may do it.

Speaker 3:

It doesn't really quite work out very well when you start using the word like yeah, you can or you may find the language every once in a while slip through, but very rarely. But our role is to make that be nice and clear, right? Because if the government resolves and the government needs to know what's doable, you can't just say do this and have it be an impossibility. At the same time, when they do pass these kinds of regulation, we need to tell our members this is what it means, this is how you'd actually start applying this. So we act as kind of an intermediary of information. And no, I have to confess it's not sexy, it's not the kind of thing that attracts a lot of people, but it does have a fundamental purpose that needs to be an ongoing solution.

Speaker 2:

And out of the pandemic. I mean sustainability. I'm not saying it came out of the pandemic, but it's become a bigger topic. So, similarly, the supply chain has come under sort of intense scrutiny and some people, I guess, maybe hoping, once the situation in Eastern Europe et cetera, calms down, things will go back to normal, whatever that might mean. But do you think supply chains your members are already on need to start re-evaluating where they're getting their resources from? Or, as you say, do you think if they're sitting out for another six months, everything's back to normal? Or do you think it's a long-term issue that needs addressing?

Speaker 3:

I would caution anybody into thinking that they can wait and expect things to go back to normal, Because what constitutes normal nowadays? It's not the way it was two years ago. We have the geopolitical impact on supply, for data and communication has radically changed in the last three years, so the Eastern Europe situation is actually a little bit more dire than people realize. There are a lot of software houses in the Ukraine. There's a lot of information that are coming out of that area of the world. Even Russia itself has offered considerable amounts of positive technology contributions into the industry. There's China, there's Taiwan. There's the global impact of the tensions going on there. We still have some of the sanctions on Chinese companies. In the United States we have new regulations about what can and can't be sent into and out of the Chinese territories. So that's not going away in six months.

Speaker 3:

I think anybody who thinks that it's gonna take a six month hiatus and then have everything go back to perfection is probably fooling themselves. What I think we have to do is we have to. We can't just try to accept all this in one lump sum. We have to be vigilant, excuse me. We have to be diligent and vigilant. Say that three times fast. We need to be aware of what's happening in the tensions in India and Pakistan, and all of these things have a much greater impact all the way into Poughkeepsie. I mean, it's one of those things or leads. Either way, it's going to be impacted somewhere, whether it's going to be at the service level, it's going to be impacted at the price level, it's going to be impacted on the regulation level.

Speaker 3:

I think one of the other things that's happening too is the content of the data is starting to get more scrutiny. There are things that are happening with unelected governmental, non-governmental organizations that are starting to make people question what kind of data can be sent to whom and when. Who should be able to have it, who shouldn't be able to use it? Those all have really profound impacts. So I honestly think that we don't have all the answers. I'm not pretending that we do, but I do think that you need to have somebody. You can ask a question to somebody who is also taking ongoing attention to what's happening, Because if you're not careful, you could wind up being on the business end of his event, and I don't think anybody really wants that.

Speaker 2:

Okay, and then maybe, just as we finish, the storage industry more generally. I mean, I've sort of followed it on and off since the early days of Fiber Channel, which is a wee while ago, and there's plenty of names that were like, if you like, the bedrock of the industry then and no longer around. It's a classic, I guess, technology that there were a lot of people in early. Then it's consolidated. Do you worry at all that the consolidation has perhaps gone too far and that the gene pool, if you like, is too small, so there's not enough innovation, because whenever somebody does something clever, it seems to be hoovered up, dare I say, but one of the large organizers. Or do you think the industry is very healthy and, as we discussed earlier, there are some innovative ideas going on and therefore all is good in the garden?

Speaker 3:

Well, I don't know how good the garden is, but I think that if you look at the history of technology, you'll see that there's a bit of an accordion effect. Expansion and contraction has been normal and it's been going on ever since the days of Univac. So if you follow through the history of any technology all the way back, if you want to go all the way back to the telegraph, it's exactly the same thing. The history has been consistent. Same thing with hardware and software.

Speaker 3:

There was a period of time not too long ago, when people said that hardware was completely irrelevant. All you needed to do is software. And now, where has really the innovation come? Through Hardware, we now have the universal chiplet consortium that started out. We've got SNEA, we've got Enviom Express, we've got CXL, which has really taken the server world by storm. You have all of these technologies that are hardware-oriented, hardware-related. That will make the software better and then the software will improve as well. And then the software will get better and we'll start to eliminate some of those layers of abstraction, because that got too big. The software component is. I mean, if you would just look at a stack diagram of all the latency, software is huge and pretty soon. People want to get better performance, so they reduced that software and they start focusing on the hardware.

Speaker 3:

The accordion starts to come back. As long as the accordion is moving, we're healthy. It's when people start to artificially try to stop it, then things get into trouble. And from SNEA's perspective, we are perfectly happy to play the accordion. We are happy to go ahead and encourage the development where it needs to be, like the DNA data storage lines. Perfect example. That is real, true, innovative thinking is truly thinking outside the box and literally as it turns out. So I think that there's always going to be somebody who wants something more or something better, something more efficient, something less costly, and they're going to have an idea to do it. Some of them will win, some of them won't, and by winning I mean just be used. It doesn't have to be the best, it doesn't have to be the greatest, it just has to be something that people are working on. From our perspective, we're perfectly happy to be home for those kinds of things, and that's, I think, where we're going to be focusing in the future.

Speaker 2:

Okay, and then maybe just finally. Finally, in terms of the end user, I always feel slightly sorry for them because they're getting bombarded with all these great new ideas and things going on. They're one day being told to be on the premise and then the next go in the cloud and all the rest. I know it's very difficult to limit yourself, maybe, to one or two, but if you had a couple of pieces of advice, when users, faced with this enormous portfolio of storage technologies and stuff, where do you think they should concentrate to get the quickest results? Or what do they need to be looking at, do you think, to improve their storage performance?

Speaker 3:

Well for all. Number one don't panic and bring your towel. Number two SNEA has been doing an awful lot of work over the last several years to try to break a lot of this down into plain English. So we have probably a library of hundreds of hours of plain English content that they can go to by going to the website or, because we have a YouTube video, you can go into YouTube and go to our YouTube channel too. It's vendor neutral. It's technology neutral, which means that there's no promotion of any one vendor over another or anyone technology over another.

Speaker 3:

So if you want to find out about the pros and cons of Fiber Channel, which is still very strong storage technology, you can do that. If you want to find out about XPUs, which are brand new and very confusing to a lot of people SmartNix, computational storage these are just some of the more recent ones, but we also go back to the basics. If you don't know what RAID is or what RAID means, if you're not sure what an initiator or a target is, you just want to get started. We have those kinds of things as well. We have a series called Everything you Wanted to Know About Storage, what we're too proud to ask. So, everything from the absolute basics to the very new complex topics, we do an awful lot of education that is just freely available for people. All they have to do is look, and so we're going to continue to do that. It's a major pillar of our mission.

Speaker 2:

Okay, well, I've taken up a lot of your time and I really appreciate it. Give us some fascinating insights, so thank you very much indeed for being with us. Thank you.

Speaker 3:

Thank you for the invite.

Speaker 1:

Thank you for listening. For additional information on the material presented in this podcast, be sure and check out our educational library at sniaorg.

Advancements in Computational Storage Devices
NVME and DNA in Storage Industry
Holographic and Cloud Storage
Supply Chain Challenges and Technical Innovations
Free Education and Invitation to Learn