CloudFront cache invalidation for React app
up vote
0
down vote
favorite
I have a React/redux app which is deployed on CloudFront + s3. There is no static hosting enabled on the bucket. I understand that invalidating cache on a new deployment clears cache in all the edge locations and the new changes will be served up. But what happens to the active prod users when the cache is invalidated? Are they able to continue on the app without any errors? Does it get worse for the active users if the redux store structure changed in the new version?
reactjs amazon-cloudfront aws-cloudfront
add a comment |
up vote
0
down vote
favorite
I have a React/redux app which is deployed on CloudFront + s3. There is no static hosting enabled on the bucket. I understand that invalidating cache on a new deployment clears cache in all the edge locations and the new changes will be served up. But what happens to the active prod users when the cache is invalidated? Are they able to continue on the app without any errors? Does it get worse for the active users if the redux store structure changed in the new version?
reactjs amazon-cloudfront aws-cloudfront
There wont be any impact on active users after old cache gets invalidated. Remember, Bundled js file will be downloaded once from server from there until you refresh your browser your react/redux app will use your old app (app before cache got invalidated). Also there would some issues if there are changes in your backend services
– Nagesh Dhope
Nov 19 at 12:11
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a React/redux app which is deployed on CloudFront + s3. There is no static hosting enabled on the bucket. I understand that invalidating cache on a new deployment clears cache in all the edge locations and the new changes will be served up. But what happens to the active prod users when the cache is invalidated? Are they able to continue on the app without any errors? Does it get worse for the active users if the redux store structure changed in the new version?
reactjs amazon-cloudfront aws-cloudfront
I have a React/redux app which is deployed on CloudFront + s3. There is no static hosting enabled on the bucket. I understand that invalidating cache on a new deployment clears cache in all the edge locations and the new changes will be served up. But what happens to the active prod users when the cache is invalidated? Are they able to continue on the app without any errors? Does it get worse for the active users if the redux store structure changed in the new version?
reactjs amazon-cloudfront aws-cloudfront
reactjs amazon-cloudfront aws-cloudfront
asked Nov 19 at 11:51
Celin Jane
306
306
There wont be any impact on active users after old cache gets invalidated. Remember, Bundled js file will be downloaded once from server from there until you refresh your browser your react/redux app will use your old app (app before cache got invalidated). Also there would some issues if there are changes in your backend services
– Nagesh Dhope
Nov 19 at 12:11
add a comment |
There wont be any impact on active users after old cache gets invalidated. Remember, Bundled js file will be downloaded once from server from there until you refresh your browser your react/redux app will use your old app (app before cache got invalidated). Also there would some issues if there are changes in your backend services
– Nagesh Dhope
Nov 19 at 12:11
There wont be any impact on active users after old cache gets invalidated. Remember, Bundled js file will be downloaded once from server from there until you refresh your browser your react/redux app will use your old app (app before cache got invalidated). Also there would some issues if there are changes in your backend services
– Nagesh Dhope
Nov 19 at 12:11
There wont be any impact on active users after old cache gets invalidated. Remember, Bundled js file will be downloaded once from server from there until you refresh your browser your react/redux app will use your old app (app before cache got invalidated). Also there would some issues if there are changes in your backend services
– Nagesh Dhope
Nov 19 at 12:11
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Clearing the cloudfront cache will bring up the fresh content from your origin. However, that would not affect the existing production users. They would continue to be served from the cached content as long as their session continues.
That being said, they would be served the fresh content when their session restarts.
There would be no errors whatsoever.
Hope this helps.
I have chunks instead of a single bundled is. In a React app Wouldn’t the chunks be incompatible between routes for old VS new chunks especially if the redux store structure changed betweeen deployment versions?
– Celin Jane
Nov 20 at 15:26
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Clearing the cloudfront cache will bring up the fresh content from your origin. However, that would not affect the existing production users. They would continue to be served from the cached content as long as their session continues.
That being said, they would be served the fresh content when their session restarts.
There would be no errors whatsoever.
Hope this helps.
I have chunks instead of a single bundled is. In a React app Wouldn’t the chunks be incompatible between routes for old VS new chunks especially if the redux store structure changed betweeen deployment versions?
– Celin Jane
Nov 20 at 15:26
add a comment |
up vote
0
down vote
Clearing the cloudfront cache will bring up the fresh content from your origin. However, that would not affect the existing production users. They would continue to be served from the cached content as long as their session continues.
That being said, they would be served the fresh content when their session restarts.
There would be no errors whatsoever.
Hope this helps.
I have chunks instead of a single bundled is. In a React app Wouldn’t the chunks be incompatible between routes for old VS new chunks especially if the redux store structure changed betweeen deployment versions?
– Celin Jane
Nov 20 at 15:26
add a comment |
up vote
0
down vote
up vote
0
down vote
Clearing the cloudfront cache will bring up the fresh content from your origin. However, that would not affect the existing production users. They would continue to be served from the cached content as long as their session continues.
That being said, they would be served the fresh content when their session restarts.
There would be no errors whatsoever.
Hope this helps.
Clearing the cloudfront cache will bring up the fresh content from your origin. However, that would not affect the existing production users. They would continue to be served from the cached content as long as their session continues.
That being said, they would be served the fresh content when their session restarts.
There would be no errors whatsoever.
Hope this helps.
answered Nov 20 at 8:18
Priyanka Makhija
935
935
I have chunks instead of a single bundled is. In a React app Wouldn’t the chunks be incompatible between routes for old VS new chunks especially if the redux store structure changed betweeen deployment versions?
– Celin Jane
Nov 20 at 15:26
add a comment |
I have chunks instead of a single bundled is. In a React app Wouldn’t the chunks be incompatible between routes for old VS new chunks especially if the redux store structure changed betweeen deployment versions?
– Celin Jane
Nov 20 at 15:26
I have chunks instead of a single bundled is. In a React app Wouldn’t the chunks be incompatible between routes for old VS new chunks especially if the redux store structure changed betweeen deployment versions?
– Celin Jane
Nov 20 at 15:26
I have chunks instead of a single bundled is. In a React app Wouldn’t the chunks be incompatible between routes for old VS new chunks especially if the redux store structure changed betweeen deployment versions?
– Celin Jane
Nov 20 at 15:26
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374069%2fcloudfront-cache-invalidation-for-react-app%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
There wont be any impact on active users after old cache gets invalidated. Remember, Bundled js file will be downloaded once from server from there until you refresh your browser your react/redux app will use your old app (app before cache got invalidated). Also there would some issues if there are changes in your backend services
– Nagesh Dhope
Nov 19 at 12:11