Re:Rails in Realtime - How LayerVault updates every page in ...
by gingerlime on Wednesday September 05, 2012 @03:48PM
(#4481099)
Nice post with lots of cool stuff. Any particular reason you're using delayed_job for async jobs + memcache for caching and not resque/redis? Not saying anything bad about the former, just wonder if there are pros/cons you considered when choosing between the two?
[ Parent
| on HN ]
Re:Rails in Realtime - How LayerVault updates every page in ...
by kellysutton on Wednesday September 05, 2012 @03:57PM
(#4481153)
When first building LayerVault around this time last year, the simplicity of delayed_job appealed to me. Not having to set up and maintain a Redis application was a bonus. The simple '.delay' syntax sealed the deal for me.
That being said, the day where we need to separate our queueing system will come. But delayed_job/MySQL has brought us much further than I'd thought possible.
Re:Rails in Realtime - How LayerVault updates every page in ...
by davidw on Thursday September 06, 2012 @04:32AM
(#4483332)
I think this is a fantastic illustration of how it's more important to get something 'pretty good' out in front of customers, even if you could have used the latest/coolest/hippest things. You're illustrating how you can go back and improve it later, when you're clearer on what needs doing.