Erm...
Might just be the academic pedant in me nit picking at terms, but content addressable storage is generally different from object storage in the storage world I live in, to the point that I almost never hear the terms used interchangeably.
Certain implementations share flavors of one another, but the key is in the name: content. A content addressable storage system is one where the content is hashed (or a portion of it hashed) to for the purposes of producing an address that serves the dual purposes of implicit deduplication and naming of the data. Object storage, on the other hand, tends towards using the *name* of the object as a way of locating it, by hashing it and dumping it on a consistent hashing ring with object servers owning parts of the namespace.
Biting the hand that feeds IT
