[
https://issues.apache.org/jira/browse/OAK-8280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826477#comment-16826477
]
Matt Ryan commented on OAK-8280:
--------------------------------
The exception case is when the client requesting a URI is running on a VM for a
cloud provider in the same region as where the blob storage is. This is true
at least for Azure - if running on an Azure VM in the same region as the blob
storage, the best performance for downloading a signed URI is to use a non-CDN
URI in that particular case.
In discussion with others on the Oak team, while we recognize that the testing
results showed better performance, it is one edge case and may not be
applicable in real-world scenarios. Most use cases are either web clients
requesting the URIs (which could be anywhere but are almost certainly not
running in a cloud VM), or external services which could also be running
anywhere. An application built on top of the Oak repository would have no
purpose in requesting the signed URI, because it is running in the same VM
anyway and this doesn't improve the I/O usage of that application. So it would
be hard for a client to know for sure that the specific binary it needs to
request is in the same region and also be the case that the client has a reason
to request a signed URI for that binary.
Until we come up with a reasonable use case this is probably on hold.
> [Direct Binary Access] Allow client to veto use of CDN URI
> ----------------------------------------------------------
>
> Key: OAK-8280
> URL: https://issues.apache.org/jira/browse/OAK-8280
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: blob-cloud, blob-cloud-azure
> Reporter: Matt Ryan
> Priority: Major
>
> As we learned in OAK-7702, using signed CDN URIs usually offers improved
> throughput, but not always. Implementing this issue would mean that we
> extend the API to allow a client to indicate that they do not want the CDN
> URI, even if a CDN is configured, because the client somehow knows that the
> non-CDN URI will be better.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
