SharedHashMap vs Redis
Overview This is a comparison between OpenHFT's SharedHashMap and a popular key-value store Redis. Any vendor will tell you how great their product is, so I will start by outlining why you wouldn't use SharedHashMap, before I tell you why it is a "must have" for performant applications. Why you would use Redis? Redis is a more mature database, relatively widely used and it includes; Support for multiple languages. Access over TCP to remote clients. A command line management tool. It out performs many other key-value stores. Why you would use OpenHFT's SharedHashMap? You need to maximise performance in Java. It outperforms Redis, and many other popular key-values stores by more than an order of magnitude in Java. Why does SharedHashMap out perform Redis? It is designed for performance from the start, by being as lightweight as possible. It acts as an embedded data store, even across multiple processes. You don't pay the price of TCP mess...