[
https://issues.apache.org/jira/browse/OAK-8524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927145#comment-16927145
]
Matt Ryan commented on OAK-8524:
--------------------------------
I've done a fair bit of testing on different CDNs running tests from multiple
locations worldwide, and one thing I've discovered is that no one approach
seems to be universally better for every situation. So I'm retracting the
statement in the description where I said " It is expected that both domains
would be have the same value if both are configured." Having upload and
download configured separately allows more flexibility - we shouldn't make any
assumptions about them being the same.
> [Direct Binary Access] Add CDN Support to AzureDataStore
> --------------------------------------------------------
>
> Key: OAK-8524
> URL: https://issues.apache.org/jira/browse/OAK-8524
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Reporter: Matt Ryan
> Assignee: Matt Ryan
> Priority: Major
>
> Add support for using an Azure CDN to AzureDataStore. This will allow a user
> to specify an Azure CDN domain via configuration that will be used by in the
> generation of direct upload and direct download URIs.
> It is recommended that two configuration parameters be defined - one for the
> CDN upload domain, and one for the CDN download domain. The reason for
> defining both separately is to allow an installation to specify CDN use for
> each direction independently. For example, if a user determines through
> testing that using CDN for downloads is faster for their users but not using
> a CDN for uploads is better, they can configure only downloads and leave
> uploads to be done using the non-CDN domain. It is expected that both
> domains would be have the same value if both are configured.
> Also, this task limits the scope of CDN support to the generation of signed
> upload and download URIs, and not to the standard interaction of the data
> store with Azure blob storage.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
