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

I like to run a single redis server process on each instance that's serving the webapp, and also have a shared redis cluster for shared cached state (like user sessions). That way there's a fast local cache for people to use for caching API calls and other things where duplication is preferable to latency.


If it's purely ephemeral and not replicated between instances what are you getting from redis that couldn't be done with SQLite or even a good old hashmap in a separate thread?


Redis is probably slightly faster than sqlite, and developers are used to using redis primitives and APIs.


You get standardized data structures and consistent operations on them for free.




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

Search: