Invalidating a cache
That seems appropriate, and appending a version timestamp will invalidate it, but obviously we don't have that here.So what is the intended mechanism for invalidating a cache of theme css?I am considering using the Amazon SNS for the making the topic.Now for the servers to receive the invalidation messages, I am confused between the following: Could you please highlight the pros and cons of both of these approaches or any other approach that might benefit me.I have a node type "Article" that contains a repeating Paragraphs field.One of the paragraph types let's the user embed a view using a entity reference field.These events are perfectly suited for cache invalidation.
Could you suggest me a way to by-pass the NGINX server or find out the port on the fly and then hit the servers. I mean, why would you have your own caching mechanism which would rely on Amazon anyway (if you use SNS), while you can get the benefits of centralized caching directly from Amazon with no additional effort?
----------UPDATE--------- If I use NGINX to redirect any request to one of the 6 servers.