jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Ryan (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (OAK-7702) [Direct Binary Access] Add CDN support, use S3 Transfer Acceleration only for uploads
Date Thu, 01 Aug 2019 15:58:00 GMT

    [ https://issues.apache.org/jira/browse/OAK-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826472#comment-16826472
] 

Matt Ryan edited comment on OAK-7702 at 8/1/19 3:57 PM:
--------------------------------------------------------

FWIW, S3 transfer acceleration offers similar benefits to CloudFront (AWS's CDN) but with
a different technology.  Transfer acceleration allows you to resolve your request at a local
node and use AWS's higher speed network to fulfill the request from the origin.  There is
no caching involved with transfer acceleration, so subsequent requests still are resolved
at a local node but fulfilled from origin every time.  CloudFront would follow a similar
pattern for the first request, but the response would be cached at the local node so would
be resolved and fulfilled at the local node in subsequent requests.

[~alexander.klimetschek] it would be helpful to have some more context around your comment
pertaining to S3 transfer acceleration where you asserted that "this feature only makes sense
for uploads".  Is that because uploads by definition are non-cacheable so CloudFront offers
no additional advantage over transfer acceleration when it comes to uploads?

If so I'd argue it may still be worthwhile to add support for uploading to S3 via CloudFront
URIs, because this would mean a customer was not required to turn on transfer acceleration
in addition to CloudFront to gain the upload speed improvement.


was (Author: mattvryan):
FWIF, S3 transfer acceleration offers similar benefits to CloudFront (AWS's CDN) but with
a different technology.  Transfer acceleration allows you to resolve your request at a local
node and use AWS's higher speed network to fulfill the request from the origin.  There is
no caching involved with transfer acceleration, so subsequent requests still are resolved
at a local node but fulfilled from origin every time.  CloudFront would follow a similar
pattern for the first request, but the response would be cached at the local node so would
be resolved and fulfilled at the local node in subsequent requests.

[~alexander.klimetschek] it would be helpful to have some more context around your comment
pertaining to S3 transfer acceleration where you asserted that "this feature only makes sense
for uploads".  Is that because uploads by definition are non-cacheable so CloudFront offers
no additional advantage over transfer acceleration when it comes to uploads?

If so I'd argue it may still be worthwhile to add support for uploading to S3 via CloudFront
URIs, because this would mean a customer was not required to turn on transfer acceleration
in addition to CloudFront to gain the upload speed improvement.

> [Direct Binary Access] Add CDN support, use S3 Transfer Acceleration only for uploads
> -------------------------------------------------------------------------------------
>
>                 Key: OAK-7702
>                 URL: https://issues.apache.org/jira/browse/OAK-7702
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: blob-cloud, blob-cloud-azure
>            Reporter: Alexander Klimetschek
>            Assignee: Matt Ryan
>            Priority: Major
>
> Azure Blob Store and S3 support CDNs in front of private containers/buckets, which also
work with presigned URLs ([S3 docs|https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-signed-urls.html],
[cloudfront presigning java|https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/CFPrivateDistJavaDevelopment.html],
[Azure docs|https://docs.microsoft.com/en-us/azure/cdn/cdn-sas-storage-support]). The binary
access feature should support these for download URLs via a configuration on the DataStore.
> Currently, the S3 datastore has a config for [transfer acceleration|https://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html]
that if enabled, will make both upload & download URLs use the acceleration option. However,
this feature only makes sense for uploads, especially if CDN is an option for downloads.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Mime
View raw message