I currently have an application that is using the default view caching that is included with Laravel blade templating. As expected, when the blade files are compiled, the cached view is stored in storage/framework/views (this is the default Laravel value).
When working with my Techops team, they mentioned that these compiled views needed to be put onto an S3 server vs. stored on the local instance. I've found a possible way to overwrite this here, How do I disable Laravel view cache?. Which I have started to implement into my application.
My question is, what is the benefit of pushing these to an S3 server vs. local directory, if any? Will this method cause any latency in load times? Any other issues you may see arising with this method?
via snft02
