This idea adds a fast SSD cache to a slow access bulk archive.

Obviously that cache can massively accelerate repeated access to the same data, and reduce tape wear and mechanical wear and energy usage.

But I think the critical issue is where you want the cache to be. Because end point devices already have local cache.

So this product only seems to have a big advantage on applications where you expect many unique users to access the same archive data for the first time, and within a short period of time before it expires from the tape drive’s SSD cache.

This is why I think it’s a small niche. Maybe too small to be worthwhile.

Edit: it also has the disadvantage that the first few devices to try to access the data would have a huge delay for a minute or more while the data is located on the tape. It’s also vulnerable to DDOS by attackers requesting random cold data, to fill the SSD.