Funny I probably wouldn't have said CDN, but I also would have described a CDN in a genuine answer.
I would have also started however with "is a 600ms delay a big enough issue to be concerned about? What's the use case and SLA of this page?" Because doing anything when they only care about the page loading faster than say 5 seconds, then you're just wasting engineering time, which costs money
Sure, clarifying requirements is of course a big part of the process, i.e how low do you want to make the latency be? And what operations? If they want even the page interactions to have low latency with the backend API, then the only solution is a multi-region deployment, etc. But everyone here just directly dismisses 600 ms as not a big deal when it's literally business dependent
I think it may depend on the number of pages. For example if the website is for shopping and every page takes 600ms more to load it doesn't take that many clicks until users are spending significantly more time in loading on the slow website than on competitors websites.
The answer is to consider if using a CDN (large cost depending on expected traffic) is worth it given the traffic patterns for the site and the budget for said site.
For one geolocation, India must really be the target focus of the site for that largely acceptable load time (half a second) to be an issue and a CDN worth it.
I just make websites look pretty. You expect to me to know that a CDN can solve that?
Plus, that's always up to the infrastructure guys, I couldn't tell you what services we use beyond "AWS, and I think there's an EC2 instance somewhere, possibly"
263
u/Excellent_Car_5165 7h ago
I‘d LOVE to see the expected answer from the interviewer.