News for hackers. Stuff that matters.
Re:Cloud Filestore, high-performance file storage for GCP users by oavdeev on Tuesday June 26, 2018 @12:51PM (#17402182)
So now they have two cloud storage products, called Cloud Firestore and Cloud Filestore? Their branding team is on top of their game, as always.
Re:Cloud Filestore, high-performance file storage for GCP users by luryus on Tuesday June 26, 2018 @01:01PM (#17402257)
Between Cloud Storage, Cloud Datastore, Cloud Firestore and now Cloud Filestore the naming of these services is frustratingly confusing. Oh and of course there are also BigQuery and BigTable, which do not really give any clearer picture of the actual service. I've used GCP extensively for more than a year now and I still get confused about the different storage services way too often.
Re:Cloud Filestore, high-performance file storage for GCP users by mehblahwhatevs on Tuesday June 26, 2018 @01:44PM (#17402617)
I came in here to say the same thing.

"Google Cloud Storage" could be a product but also the encompassing category of all the things you mentioned?

Also on the Firebase pricing page (https://firebase.google.com/pricing) they have a "Realtime Database", is that related to datastore or cloud storage?

They also have another item there just labeled "Storage". Is that one of the above?

And at the bottom you get "Google Cloud Platform" on the "Blaze Plan". Is that the products you mentioned that all start with "Cloud"?

Re:Cloud Filestore, high-performance file storage for GCP users by manigandham on Tuesday June 26, 2018 @01:11PM (#17402335)
AWS uses random unique names and Azure uses more standard component names, while GCP seems to be in the middle.

No approach is "the best". They're all very different services and if you're going to use them then you would've read the overview anyway.

Re:Cloud Filestore, high-performance file storage for GCP users by awad on Tuesday June 26, 2018 @03:29PM (#17403372)
Having a product overview is still not an excuse for terrible naming.
Re:Cloud Filestore, high-performance file storage for GCP users by deesix on Tuesday June 26, 2018 @01:28PM (#17402494)
Disclosure: I work on GCP

Thanks for the feedback. As the person that named both products, I can say we spent a ton of time debating this but we felt that the fact one is an enterprise file share and the other a document database service focused on mobile and web would mean very little conflict for customers. We will keep an eye on any customer confusion it might cause.

Re:Cloud Filestore, high-performance file storage for GCP users by jedberg on Tuesday June 26, 2018 @02:00PM (#17402743)
Please make sure you read this comment: https://news.ycombinator.com/item?id=17402427

It explains why this is linguistically bad. Basically, a billion people on this planet don't distinguish between the l and r sounds, so for 1/6 of the planet, these names are identical.

Re:Cloud Filestore, high-performance file storage for GCP users by Gigablah on Tuesday June 26, 2018 @09:18PM (#17405149)
Native Chinese speaker here. That post is comically wrong. For one thing, you don't pronounce either "file" or "fire" like "filer" or "firer" -- isn't English amazing ;) -- so there's no L/R sound in the first place for us to supposedly confuse.
Re:Cloud Filestore, high-performance file storage for GCP users by IanCal on Tuesday June 26, 2018 @01:57PM (#17402702)
I mean all of the following in the best possible way:

Perhaps also worth looking at the screenshot in the blogpost.

You have in there:

---

Datastore

Storage

Filestore

---

So, datastore is not storage, nor is filestore. What is it storage storing if not data or files? Why are files not data? I have no idea what should go where.

> We know folks need to create, read and write large files with low latency. We also know that film studios and production shops are always looking to render movies and create CGI images faster and more efficiently. So alongside our LA region launch,

So I couldn't create, read or write before without low latency? I thought this was already a feature of your other products

> we’re pleased to enable these creative projects by bringing file storage capabilities to GCP for the first time with Cloud Filestore.

For the first time? I couldn't store files before?

I'm not trying to be an arse, but I really don't get from this what the key difference is from everything else you offer.

Re:Cloud Filestore, high-performance file storage for GCP users by derefr on Tuesday June 26, 2018 @05:17PM (#17404079)
> What is it storage storing if not data or files?

Objects. Cloud Storage is the S3 competitor.

> Why are files not data?

“Data” as in rows in a database. Like Dynamo.

Everything on a computer is data. The thing you’ve got to understand is that the terms we use, “objects”, “files”, “data” — these don’t refer to types of data, but rather to access paradigms for data. The semantics of their storage, indexing, mutability, etc.

An object is a blob of data named by a key, that you can retrieve entirely, or overwrite entirely, and where usually you automatically get a version history of old versions that have been overwritten that you can retrieve, with a cutoff for automatic GC.

“Data” is a structured tuple that a database knows how to index into, and sort by the columns of. You insert rows, update columns of rows by a key, or delete rows by a key.

“Files” are seekable streams where you can index anywhere into a file by position and then read(2) or write(2) data at that position, and where other clients can see those updates as soon as you sync(2), without needing to close(2) the file first.

All could be used to implement the other (S3 is implemented in terms of Dynamo rows holding chunks of object data, for example.) But each access semantics has use-cases for which it is an impedance match or mismatch.

Re:Cloud Filestore, high-performance file storage for GCP users by IanCal on Wednesday June 27, 2018 @03:02AM (#17406271)
Thanks for the explanation, the file/object/data difference makes sense.

> An object is a blob of data named by a key, that you can retrieve entirely, or overwrite entirely, and where usually you automatically get a version history of old versions that have been overwritten that you can retrieve, with a cutoff for automatic GC.

And yet they refer to the objects inside as "Files" and support seeking

https://cloud.google.com/appengine/docs/standard/python/goog...

https://stackoverflow.com/questions/14248333/google-cloud-st...

I know this is just bikeshedding about names and terms but it feels confused.

I think some of the confusion in the list is because of the mix of generic and product naming.

Data can be stored in datastore. But also in "spanner" or "bigtable", which are not parts of "datastore", or in "SQL" which is a language. Object can be stored in the object store called "storage" which is also within an entire category itself called "storage". So there's "Storage" which is a group of all these kinds of stores, and "Storage" which is a very specific type of store.

Re:Cloud Filestore, high-performance file storage for GCP users by ttul on Tuesday June 26, 2018 @01:32PM (#17402531)
This will be extremely confusing for Japanese and Korean speakers.
Re:Cloud Filestore, high-performance file storage for GCP users by cellularmitosis on Tuesday June 26, 2018 @02:18PM (#17402872)
I think its worth adding some additional phonetic context around this remark (I made a similar remark and my coworkers thought I was making a racist joke).

The reason native Japanese speakers struggle with "R" and "L" sounds is because they just have one phoneme to work with, which sounds (to a native English speaker) like a combination of "R", "L", and "D". If you aren't exposed to phonemes at a young age, it is difficult to expand your set later in life.

An analogous difficulty might exist for English speakers if a Chinese company came up with two product names which used the exact same sequence of syllables, but had "tonal" differences in pronunciation.

Re:Cloud Filestore, high-performance file storage for GCP users by yongjik on Tuesday June 26, 2018 @02:06PM (#17402781)
Actually, not that much for Korean speakers, because "file" becomes "pa-il" and "fire" becomes "pa-i-eo". (Damn English triphthongs...)

Hopefully they won't launch Cloud Pyrestore any time soon...

Re:Cloud Filestore, high-performance file storage for GCP users by lioeters on Tuesday June 26, 2018 @05:09PM (#17404009)
Similarly for Japanese, "file" is pronounced/written as "fairu" and "fire" as "faiyaa". If the service docs are translated, then they would look like (and sound as) difference names.
Re:Cloud Filestore, high-performance file storage for GCP users by nerpderp83 on Tuesday June 26, 2018 @05:42PM (#17404220)
By the heat of the fire, and play their songs from LyreStore.

Floating plastic would go in the GyreStore.

If you had a bunch muck it would go in MireStore.

Re:Cloud Filestore, high-performance file storage for GCP users by borplk on Tuesday June 26, 2018 @01:40PM (#17402594)
This will be extremely confusing for anyone.
Re:Cloud Filestore, high-performance file storage for GCP users by deesix on Tuesday June 26, 2018 @02:02PM (#17402758)
Disclosure: I work on GCP

Thanks for highlighting. We were aware of this and working with the local sales teams to make it as easy as possible.

Re:Cloud Filestore, high-performance file storage for GCP users by vasco on Tuesday June 26, 2018 @02:37PM (#17403005)
Even if the products are for different types of customers all of them will still need to click the right one.
Re:Cloud Filestore, high-performance file storage for GCP users by oavdeev on Tuesday June 26, 2018 @01:40PM (#17402591)
I mean.. I get it, there isn't a lot to work with, it is a thing that _stores files_ after all, and it most closely resembles a normal filesystem.

But it does make GCP's storage product naming even more confusing overall (after "Cloud Storage" vs "Cloud Datastore" mentioned above).

Re:Cloud Filestore, high-performance file storage for GCP users by pinewurst on Tuesday June 26, 2018 @01:32PM (#17402529)
What about when the names are spoken, especially by non-native English speakers? They're close homonyms.
Re:Cloud Filestore, high-performance file storage for GCP users by iagovar on Tuesday June 26, 2018 @01:43PM (#17402614)
I'm non native English speaker and I didn't notice the difference.

Please, use useful names that do tell what is it about.

Re:Cloud Filestore, high-performance file storage for GCP users by ak217 on Tuesday June 26, 2018 @03:11PM (#17403251)
Not only is it confusingly similar to other storage products, but the abbreviations collide among all of them. GCF means how many different things now? (I always considered it to mean Google Cloud Functions - kind of an important product.) Don't underestimate the importance of these things. I can't even talk to my colleagues about your products without us all misunderstanding each other.
Re:Cloud Filestore, high-performance file storage for GCP users by foobiekr on Tuesday June 26, 2018 @01:54PM (#17402677)
What was so special about the name that it was even worth the debate? Why not avoid the problem?
Re:Cloud Filestore, high-performance file storage for GCP users by some_account on Tuesday June 26, 2018 @03:29PM (#17403368)
You made the wrong choice.
Re:Cloud Filestore, high-performance file storage for GCP users by niftich on Tuesday June 26, 2018 @01:43PM (#17402612)
Update the chooser flowchart [1] when it's out of beta or when appropriate. This page also has brief descriptions and comparison tables.

[1] https://cloud.google.com/storage-options/

Re:Cloud Filestore, high-performance file storage for GCP users by mandeepj on Tuesday June 26, 2018 @02:13PM (#17402832)
> I can say we spent a ton of time debating this but we felt that the fact one is an enterprise file share and the other a document database service focused on mobile and web would mean very little conflict for customers.

How about naming one as Cloud FileStore and other as Cloud DbStore?

Re:Cloud Filestore, high-performance file storage for GCP users by kuwze on Tuesday June 26, 2018 @04:26PM (#17403719)
Maybe you could give them pokemon/ikea-like nicknames? Stupid idea, but it might really help people searching for stuff.
Re:Cloud Filestore, high-performance file storage for GCP users by bigtones on Tuesday June 26, 2018 @08:38PM (#17405010)
Oh oh, it's already causing a lot of confusion. Just check the 70+ comments in this thread alone hating on the naming and professing their confusion and it's been out less than 12 hours... and that is from a self selecting very tech savvy audience. I think you've got a problem.
Re:Cloud Filestore, high-performance file storage for GCP users by borplk on Tuesday June 26, 2018 @01:39PM (#17402583)
Spent a ton of time and still decided to stick to names that differ by a single "r vs l" letter.

Wow. Don't mean to be rude but go for a walk outside and speak to 3 people outside the bubble.

Re:Cloud Filestore, high-performance file storage for GCP users by deesix on Tuesday June 26, 2018 @02:01PM (#17402749)
Disclosure: I work on GCP

Thanks for the feedback. We spoke to number of existing GCP customers for feedback, but it's fair to say we can always talk to more non-customers.

Re:Cloud Filestore, high-performance file storage for GCP users by stingraycharles on Tuesday June 26, 2018 @01:58PM (#17402715)
To be fair, I think “Filestore” in itself is a pretty descriptive name, and the real problem is the name “Firestore”. I can imagine the internal discussion when a bit like that as well, and here we have the result.
Re:Cloud Filestore, high-performance file storage for GCP users by dymk on Tuesday June 26, 2018 @01:49PM (#17402652)
You don't see the irony in that statement, as you toss in your low-effort criticism just to stoke the HN feeding frenzy?
Re:Cloud Filestore, high-performance file storage for GCP users by borplk on Tuesday June 26, 2018 @02:00PM (#17402745)
> low-effort criticism

It's a clear blunt suggestion to get out of their bubble.

No one outside Google would hear that explanation and say "Yeah totally makes sense one of them is an enterprise file share and the other a document database service focused on mobile and web, crystal clear and very little confusion.".

What more do you want out of my comment for it to not be low effort? Write a 3 page essay about it carefully making a case based on peer reviewed scientific evidence?

Re:Cloud Filestore, high-performance file storage for GCP users by dymk on Tuesday June 26, 2018 @03:45PM (#17403475)
You misunderstand, the comment provided no value at all; it’s not that I wanted peer review studies.
Re:Cloud Filestore, high-performance file storage for GCP users by faitswulff on Tuesday June 26, 2018 @01:57PM (#17402706)
Between Cloud Storage, Cloud Firestore, and Cloud Filestore, I can't make heads or tails of the situation without diving into the docs.

I was confused when they introduced Cloud Firestore to compete with their Realtime Database (https://firebase.google.com/docs/database/rtdb-vs-firestore). Now it seems like they're doing it again with Storage vs Filestore, not to mention the horrendous choice of names.

Re:Cloud Filestore, high-performance file storage for GCP users by lathiat on Tuesday June 26, 2018 @08:58PM (#17405081)
Cloud Filestore specifically gives you a multi-host NFS interface (for traditional filesystem applications) like Amazon EFS - for applications you cant easily modify to use other APIs it appears like a normal filesystem.

Cloud Storage is an API-level object store (e.g. S3) that requires specific application support.

Re:Cloud Filestore, high-performance file storage for GCP users by mholt on Tuesday June 26, 2018 @02:03PM (#17402767)
I had to read your comment 3 times before I noticed the difference.
Re:Cloud Filestore, high-performance file storage for GCP users by lazharichir on Tuesday June 26, 2018 @12:53PM (#17402189)
Firestore is a NoSQL database, Filestore is a file storage system.

If you can discern between "now" and "not" then you can deal with "Firestore" and "Filestore"...

Re:Cloud Filestore, high-performance file storage for GCP users by klodolph on Tuesday June 26, 2018 @01:20PM (#17402427)
Most people can tell the difference between /naʊ/ and /nɑt/. I mean, just look at them... one ends with a consonant, one doesn't, and the vowels are reasonably different.

The difference here is between /faɪl/ and /ˈfaɪəɹ/, which is much more subtle. It comes down to the difference between /l/ and /əɹ/. The [ə] is an uncommon vowel in languages, unstressed, and mostly subsumed by nearby sounds. And worse, more than a billion people on the planet grew up speaking a language which doesn't distinguish the [l] and [ɹ] sounds (they're both approximants with only slight differences in articulation). So when you say "file" or "fire" these people can't distinguish which one you're saying, and when they say it they use something like the tap [ɾ] or retroflex [ɻ] instead, both of which sound ambiguous to native English speakers. Or some non-native speakers will use [l] exclusively, for both /l/ and /ɹ/.

Re:Cloud Filestore, high-performance file storage for GCP users by jpatokal on Tuesday June 26, 2018 @07:27PM (#17404734)
FWIW, while Japanese doesn't distinguish L and R, "fire" is transliterated as ファイア faia while "file" is ファイル fairu. So the difference is reasonably clear.
Re:Cloud Filestore, high-performance file storage for GCP users by klodolph on Wednesday June 27, 2018 @11:10AM (#17408741)
The difference is only clear after transliteration. The problem is that transliteration is difficult to begin with.
Re:Cloud Filestore, high-performance file storage for GCP users by lazharichir on Tuesday June 26, 2018 @01:33PM (#17402537)
That's very scientific but most people will read it, not write it. And most people will use one, and not even acknowledge the existance of the other.

Sure, they are one-letter away from the other, it's a fact. But to turn this into a problem, well.. no...

Re:Cloud Filestore, high-performance file storage for GCP users by jfrankamp on Tuesday June 26, 2018 @01:49PM (#17402657)
The parent gave a phonetic explanation that has nothing to do with writing but rather hearing and speaking about it. For a billion people they aren't one letter away from each other, they're ~ the same. That's the point.
Re:Cloud Filestore, high-performance file storage for GCP users by klodolph on Tuesday June 26, 2018 @02:23PM (#17402899)
This is a problem if you work with an international team, especially if you talk over video links which are usually less than ideal.
Re:Cloud Filestore, high-performance file storage for GCP users by ademup on Tuesday June 26, 2018 @12:57PM (#17402224)
I am a bit embarrassed, but I had to read your comment twice to see that you mentioned two different products in your first sentence. So for me at least, GP comment is accurate.
Re:Cloud Filestore, high-performance file storage for GCP users by chrisjc on Tuesday June 26, 2018 @01:33PM (#17402538)
I still had to read your comment to notice the difference.
Re:Cloud Filestore, high-performance file storage for GCP users by phamilton on Tuesday June 26, 2018 @01:14PM (#17402371)
Except "w" and "t" aren't similar in pronunciation. While "r" varies a lot in pronunciation across languages and regional dialects, there are many languages where the two ("r" and "l") require the same tongue position and a few languages where the two are (overly simplified) equivalent.
Re:Cloud Filestore, high-performance file storage for GCP users by pvg on Tuesday June 26, 2018 @01:20PM (#17402418)
'now' and 'not' are almost always trivially identifiable from context, even when misspelled. Firestore and Filestore are not.