Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

One way to achieve similar performance is redis or memcached running on the same node. It really depends on the workload too. If it is lookups by key without much post-processing, that architecture will probably work well. If it's a lot of scanning, or a lot of post-processing, in-process caching might be the way to go, maybe with some kind of request affinity so that the cache isn't duplicated across each process.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: