I would like to quote below lines from: http://antirez.com/news/94 "It is multi threaded: This is true, and in my goals there is to make Redis I/O threaded (like in memcached, where the data access itself is not threaded, basically). However Redis, especially using pipelining, can serve an impressive amount of requests per second per thread (half a million is a common figure with very intensive pipelining. Without pipelining it is around 100,000 ops/sec). In the vanilla caching scenario where each Redis instance is the same, works as a master, disk ops are disabled, and sharding is up to the client like in the “memcached sharding model”, to spin multiple Redis processes per system is not terrible. Once you do this what you get is a shared-nothing multi threaded setup so what counts is the amount of operations you can serve per single thread. Last time I checked Redis was at least as fast as memcached per each thread. Implementations change over time so the edge today may be of the one or the other, but I bet they provide near performances since they both tend to maximize the resources they can use. Memcached multi threading is still an advantage since it makes things simpler to use and administer, but I think it is not a crucial part. "

You can look out for celery beat if you want to do this using Django only, else you can go with crontab only.

Here's your answer: Memcached should be used only for caching small and static data, such as HTML code fragments. Reason is Memcached will consume comparatively less memory resources for metadata. Strings, which are the only data type that are supported by Memcached, are ideal for storing data that's only being read because strings require no further processing. Redis in all other cases. Reason is Redis' ability to fine-tune cache contents and durability -- and greater efficiency overall. More info here: http://nitinbhojwani-tech-talk.blogspot.in/2016/02/redis-or-memcached.html

Node.js and PHP are both good. And you can achieve what you want by going on with anyone. But, it's about ease too. So, Let's discuss them on few points: Synchronous or Asynchronous - This must be the most dominating factor for deciding. If you want to be blocked until previous operation is over, that means you are looking out for synchronous else vice-versa. Email-sending, in most of cases is kept asynchronous. So, Node.js will be the better if you want to send bulk-mails asynchronously. Database - PHP will be better with SQL database and Node.js will be better with NoSQL or storing JSON object. Of course, it's not like hard coded, You can use otherwise too. Performace - I think for your use case Node.js will be better, as it is very well in non-blocking type of applications. You can go through below link as well. http://www.hostingadvice.com/blog/comparing-node-js-vs-php-performance/ Ease of writing - PHP has easier syntax. Node.js, being JavaScript, as we know, is all about curly-braces and parentheses and then keep counting them. But, if there's front-end also involved in your application then Node.js might help you, by preventing the syntax/context switches between front-end and back-end code Now, in terms of framework, Symfony2 is the one I'll go with if I choose PHP - LAMP or LNMP stack ExpressJs, if I choose Node.js, which is the most commonly used framework for Node.js - MEAN stack