{"id":21024,"date":"2016-07-12T09:59:50","date_gmt":"2016-07-12T08:59:50","guid":{"rendered":"https:\/\/www.inovex.de\/\/?p=1834"},"modified":"2026-03-17T07:59:26","modified_gmt":"2026-03-17T06:59:26","slug":"redis-more-than-caching","status":"publish","type":"post","link":"https:\/\/www.inovex.de\/de\/blog\/redis-more-than-caching\/","title":{"rendered":"Redis: More than caching"},"content":{"rendered":"

When talking about caching and shared caching most of us would think about memcached<\/a>. Memcached is lightweight, easy to configure and has a very good performance. But what happens when the cached data is a bit more important? Let’s have a look at Redis!<\/p>\n

Loosing cached sessions because of an server-outage is not so bad, but could cause some annoyed customers when the need to re-login. When data becomes more and more important, most people think of persistence, backup, restore, high availability. This is the point where Redis comes into play, offering\u00a0lots of features<\/a> to use both: a fast key-value in-memory DB on the one hand and data persistence, high availability, replication on the other hand.<\/p>\n

In this article we will introduce you to the world of Redis describing the key features. More detailed articles with code snippets will follow.<\/p>\n

\n

<\/p>\n<\/div>