| Redis 6 Adds Multithreading I/O |
| Written by Kay Ewbank |
| Thursday, 07 May 2020 |
|
Redis 6 is now generally available with threading for I/O. Until now the in-memory database didn't support multithreading I/O because it would complicate the Redis sharding model, but it's now available as an option and can improve Redis I/O performance to twice that of Redis 5. Redis is an open source, BSD licensed, advanced key-value store where the keys can contain strings, hashes, lists, sets and sorted sets. It’s increasing in popularity for web development as a session state store because of its simplicity and rich data structure support.
The new version adds support for Access control lists (ACL), meaning that users can be shown only those operations suitable for their role, preventing them from carrying out dangerous operations. Each user can have a defined set of capabilities that dictate which commands they can run and on what keys. Redis clients in Java, Node.js, Python and .NET already support ACLs, and the developers plan to add support to more languages and libraries now that Redis 6 is generally available. Another security improvement is the ability to encrypt traffic over SSL. Up until this version, encryption in Redis was deferred outside the process, so you had to use other applications to provide encryption. The threading support for I/O means that the Redis process can delegate the time spent reading and writing to I/O sockets over to other threads, therefore devoting more cycles to manipulating, storing, and retrieving data to boost overall performance. Client side caching support has also been added, enabling you to store a subset of data in your own process. The developers say this implementation is smart enough to manage multiple updates to the same data and keep your data as in-sync as possible.
More InformationRelated ArticlesRedis Adds TimeSeries And AI Support Microsoft Expands Redis Support
To be informed about new articles on I Programmer, sign up for our weekly newsletter, subscribe to the RSS feed and follow us on Twitter, Facebook or Linkedin. 
Comments
or email your comment to: comments@i-programmer.info |
