0

I have a website, but every time I upload a new update or feature I'm afraid it won't show up to the user.

It has happened a few times, we uploaded something new, but for some users, it didn't appear. The old information was left and it only appeared after a while.

As I know that no users will clear their browser cache to prevent this, I would like to know if there is anything I can do on the development side to prevent this, and every time I upload something new, neither user will experience any problems or will not receive the news.

I currently use AWS services like ec2, es3, bucket. cloud front and route 53

Luck dev
  • 435
  • 2
  • 5
  • 13
  • This is an **extremely, extremely vague question** - I'm voting to close this question as there is not one bit of technical info. – Ermiya Eskandary Dec 06 '21 at 19:33
  • That's right, as it's something that can be applied to any website, leaving the code here would be unnecessary, considering that I currently don't do anything to deal with it. So take it easy, vote to bring more knowledge to the community I asked this because I see few people talking about – Luck dev Dec 07 '21 at 21:57
  • It genuinely wasn’t a dig @ you and I answer a lot of questions sometimes that I shouldn’t - its just that for general questions, Reddit/Quora etc. exist. Glad you got your problem sorted :) – Ermiya Eskandary Dec 08 '21 at 06:52

1 Answers1

1

What to do

Actions to perform summarized with screenshots really elegantly here: https://stackoverflow.com/a/60049652/14077491

Why to do it

When someone makes a request to your website, AWS automatically caches the result in edge locations to speed up the response time for subsequent requests. The default is 24 hours, but this can be modified.

You can bypass this by either (1) setting the cache expiration to a very short time span, or (2) using cache invalidation. The first is not recommended since then your users will have to wait longer for a response more often, which isn't good. You can perform cache invalidation in a couple of ways, depending on whichever is better for your project. You can read the AWS docs about cache invalidation to choose for your use case.

I have previously added an extra cache invalidation task to my CD pipeline, which automates the process and ensures it is never forgotten. Unless you are posting many, many updates per month, it is also free.

Jacob K
  • 1,096
  • 4
  • 10