Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Overcoming objections: Objects in storage the object of the exercise

Still a lack of support from app vendors?

Storagebod My friend Enrico Signoretti is a massive fan of object storage, whereas for a long time I’ve had the reputation of being somewhat sceptical.

I've felt for a long time that the whole thing has been more than a little overhyped, with the hype beginning with EMC’s Atmos launch, and continuing from there.

The problem with object storage has been the lack of support from application vendors, especially in the space in which I work.

And development teams, especially those working in organisations with large numbers of heritage applications, have been very slow to embrace it. Most just want to work with standard filesystems.

And so we saw the birth of the cloud-gateway, devices that sat in front of the object-stores and presented the object-stores in a more familiar manner. Yet often the way that these were licensed simply added cost and negated the low cost of object store; they also added complexity into an environment.

The object storage vendors were slower to acknowledge the issue and really wanted you to use the API to access the storage. Also, some of the larger (mainstream) vendors really didn’t want their object storage to cannibalise their NAS revenues, and were even slower to acknowledge the issue.

So it seemed that object storage was going to be confined to the world of cloud-scale and cloud-native applications.

But this now seems to be rapidly changing: robust NFS implementations from the object storage vendors are becoming significantly more common; SMB implementations still seem to be rather patchy, but once they become more robust, I see object storage becoming the standard for file-serving applications.

Will we see API-driven "file access" become the universal method for interacting with file storage? Not for some time, but having the choice and realising that it is a not an all-or-nothing scenario will begin to ease friction in this space.

 

Similar topics

Similar topics

Similar topics

TIP US OFF

Send us news


Other stories you might like