This is one of a series of brief posts discussing the presenters at Tech Field Day 10, occurring 3rd – 5th February 2016 in Austin, Texas, at which I am an attending delegate. See links at the end of this post to other presenting vendors. Details of the event can be found on the Tech Field Day 10 page at techfieldday.com.
Caringo Inc is one of a number of software-based object storage companies and at over 10 years old, it’s difficult to know whether the company can be classed as a “start-up”. Most core object store technology revolves around the same messaging; we can store lots of stuff (billions of objects); we have a really good indexing and access algorithms; we can scale out to thousands of nodes; we have great data protection (none of that RAID stuff). When Swarm (the main Caringo product) was announced in mid-2014, (release 7) it also supported block, file and object protocols – another feature touted by all the vendors in the market.
So, how do these vendors differentiate themselves? Is it the quality of their object support compared to S3 (see my recent post on S3 being a de-facto standard)? Is it the ability to access the data in the object stores in different ways (Caringo supports Hadoop too, for example)? It seems to me that we’re at a point where other than the cost/compliance/legal issues involved, writing data to Amazon’s S3 (or equivalent public cloud vendor) would be the easiest route to take. So why store the data in your own onsite object store (other than the reasons just mentioned)?
These will be my focuses for the presentation – trying to understand how the various object store platforms can be differentiated from each other and why on-premises should be chosen over simply moving to the cloud. Object storage is trying to become the swiss army knife of storage with every protocol available; should we be viewing these solutions as the future, or is block and file support simply muddying the waters? This will be an interesting presentation for sure!
Comments are always welcome; please read our Comments Policy first. If you have any related links of interest, please feel free to add them as a comment for consideration.
Disclaimer: I was personally invited to attend Tech Field Day 10, with the event team covering my travel and accommodation costs. However I was not compensated for my time. I am not required to blog on any content; blog posts are not edited or reviewed by the presenters or Tech Field Day team before publication.
Copyright (c) 2009-2016 – Chris M Evans, first published on https://blog.architecting.it, do not reproduce without permission.