Talk:Object storage

"Object storage was first proposed at Carnegie Mellon University's Parallel Data Lab "

Talk:Object storage

November 2013

"Object storage was first proposed at Carnegie Mellon University's Parallel Data Lab "

Baloney. Object stores were a universal part of the earliest object oriented environments. It was one of the reasons it was so difficult to use early versions of things like Smalltalk for general programming, because the system lived within its object store, and that was normally a gigantic monolithic snapshot file within the underlying OS's file system. Later there were generalized versions, like Apple's Bento (no, not Bento (database)) and similar concepts.

The description here is not of object storage, but object file systems, which are similar but different. The article either needs to clearly state that, perhaps with a renaming, or alternately expand the description/history to illustrate the development of these concepts. I'm open to suggestions as to which of these seems more appropriate.

Maury Markowitz (talk) 13:02, 12 May 2015 (UTC)Reply

There are way too many duplicate vendor company links in here. So much so it seems promotional... A. Ward (talk) 05:41, 26 May 2016 (UTC)Reply

"Captive" object storage?

What does "Captive" object storage mean, and are there any references to the term? Isn't Facebook's Haystack rather just a proprietary object store? --Raidex.sym (talk) 13:49, 19 September 2018 (UTC)Reply

Response: Maybe merge this with "cloud" storage. "Captive object storage" certainly isn't a standard or defined term, AFAIK. — Preceding unsigned comment added by 2001:569:7CF3:FA00:A83D:9EB4:2852:98B0 (talk) 02:35, 17 February 2020 (UTC)Reply

A Commons file used on this page or its Wikidata item has been nominated for deletion

The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for deletion:

Participate in the deletion discussion at the nomination page. —Community Tech bot (talk) 22:47, 20 February 2020 (UTC)Reply

Object-based storage devices timeline

"Object storage at the protocol and device layer was proposed 20 years ago[ambiguous] and approved for the SCSI command set nearly 10 years ago[ambiguous]"

This line was added on 03. Nov 2013, so while "nearly 10 years ago" most likely refers to the source's mention of July 2004 ratification, it is unclear what proposal is meant by "proposed 20 years ago", as 20 years before 2013 would put it before the 1995 research by Garth Gibson, does anyone have an idea where this comes from?

2A06:93C2:9F:1:25B:C457:A364:BD83 (talk) 09:27, 24 November 2022 (UTC)Reply

"Differences between..." significantly wrong

The "Differences between key-value and object stores" section makes generalizations that are incorrect. Fit example, many key value stores are eventually consistent. 213.55.243.19 (talk) 05:24, 27 January 2023 (UTC)Reply

Why does Binary Large OBject redirect here?

It seems to me that Binary Large Object deserves its own entry, since this is a datatype in SQL databases, and should be described separately from object storage. At least there should be a separate section for that, but I believe restoring the original separate page would be better. RayGates (talk) 18:56, 27 November 2024 (UTC)Reply

Dated reference without attribution

This statement is significantly dated, has no attribution, and cites a report that no longer exists:

"In 2019, IDC rated Dell EMC, Hitachi Data Systems, IBM, NetApp, and Scality as leaders."

It should not appear on this page. — Preceding unsigned comment added by Jftoor (talkcontribs) 21:28, 13 June 2025 (UTC)Reply

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.