1

I have 6 web servers which are giving me problems due to cache inconsistency. I am thinking of building a cache invalidation service such that there is a topic on which all the servers can publish a message to invalidate an object. 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:

  1. Should I be using the SQS queues for the servers to receive messages.
  2. Should I be using HTTP endpoints and then build an api on that route that invalidates the cache. Could you please highlight the pros and cons of both of these approaches or any other approach that might benefit me.
tanvi
  • 927
  • 5
  • 17
  • 32

1 Answers1

3

For your use case, the http endpoints is the better solution. You push a message to SNS, and each of the subscribed endpoints will get called at a new api endpoint you host, that clears the cache.

SQS wouldn't be the best use-case here - in order to use it, you would need to have 6 separate queues (or one per server), and you would need to have an application on each that is always running in the background to check for new messages and 'pull' the message - the http endpoint is a 'push' operation, and that is what you want.

E.J. Brennan
  • 45,870
  • 7
  • 88
  • 116
  • 1
    Thanks a lot. There's something that I forgot to mention. I use NGINX to redirect any request to one of the 6 servers. If I am using the HTTP endpoint, the topic will end up hitting only one of the servers. I also am not sure which port my application would be running on. 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. – tanvi Jun 17 '16 at 08:08