cases: Fast and Secure Data Caching Hub#2587
Conversation
redir to hypothetical (for now) how-to
989bc56 to
8652ca8
Compare
update intro per #2587 (comment)
2035cf8 to
8125f91
Compare
(first version)
This comment has been minimized.
This comment has been minimized.
|
Are we all agreed on the following?
Also IMHO this is not about SEO (whether it shows up in my search results). It is purely about being misleading (would I bother clicking on it assuming it was top of my search results). |
64cb514 to
6b74636
Compare
This comment has been minimized.
This comment has been minimized.
I don't agree on this as a necessity. I think "Caching" implies speed. |
| @@ -0,0 +1,78 @@ | |||
| # Secure Data and Model Caching Hub | |||
There was a problem hiding this comment.
let's not make it about models I think
this layer is important primarily to optimize datasets usage
There was a problem hiding this comment.
minor: Hub - do we need this new term? I'm fine to keep it. just doesn't feel like it's needed
There was a problem hiding this comment.
by using Secure exclusively we are overemphasizing it too much now ... it become specifically about "security" now
There was a problem hiding this comment.
Caching Hub can be replaced with Cache I think?
There was a problem hiding this comment.
let's not make it about models
OK, removing "and Models".
Hub - do we need this new term?
Caching Hub can be replaced with Cache
Could be "Layer", or nothing. Layer could refer to the infrastructural aspect of this patter but it's not clear until you actually read the contents. What I like abut Hub is that a) some people may get that it's infrastructure-related (term taken from that recent SO question) and b) it implies multiple parties (people or projects in this case) can share a central cache.
by using Secure exclusively we are overemphasizing it too much now
Since "and Models" will be gone now, we can go back to "Fast and Secure" but fast has some misleading connotations (e.g. improving network throughput)... 🤔
| creating duplication (increasing cost). Valuable time is wasted waiting for | ||
| downloads in each environment. | ||
|
|
||
|  _Users wait for repeated transfers and produce |
There was a problem hiding this comment.
Image feedback:
- border (you mentioned that are removing them - that's good)
- first image should trigger some pain , right not it's neutral - we don't see slow, we don't see the problem - can we emphasize that's slow
- style: smooth arrows heads/tails
- one barrel is enough? otherwise it's not clear if we have two different storages?
There was a problem hiding this comment.
Communicated with the designer. Will report back when we have updates ⏳
|
After @shcheklein 's review, for the title: "Fast and Secure Data Cache"? |
Fast could be misleading but I'm OK with that. I would still prefer "Caching Hub" though, as explained in #2587 (comment). |
|
No strong opinion on this one - I see pros and cons for both, I think it's fine to go with Hub. |
|
UPDATE: FYI we're still finalizing the images but they're pretty close already. See https://dvc-org-cases-mgn-dsets-fbikyq.herokuapp.com/doc/use-cases/fast-data-caching-hub: |
There needs to be a party parrot/blob in Github. 😉 |
|
So this was approved and the images have been worked on so I merged it! Please see the final result in https://dvc.org/doc/use-cases/fast-data-caching-hub and let me know if you have additional feedback. Thanks |



Closes #654 (comment)
Closes #820 (last item)
TODOs: