- Optimized for speed - Single threaded event loop
- Data structures are implement for maximum performance, constant time and space
- Binary safe - human readable text to encoded binaries
- Size - 0 bytes to 0.5 GB
- Key based access - using GET and SET semantics
- Multi key operations
- Atomicity of operations
- Data expiration - TTL (Time to Live) support. These keys are called volatile keys (Advantages: effective invalidation approach and keeping cache size under control)
- Configurable eviction policies (all or only volatile keys) - Supports random or usage based eviction policies
- Intelligent caching - can managed via commands on server or LUA scripts
- Distributed network server - uses TCP protocol
- Request pipeline - i.e. batch process to boost average request per pipeline
- Master - Slave architecture
- Highly available - Replication mechanism through slave. Watchdog and management processes failover when needed
- Persisting data to durable storage - supports optimal and tunable data persistent mechanisms. Also can create snapshots of cache at any moment in time and restore to instant before outage
- Horizontal scaling support for RAM, Computation or Network resources via Sharing
- Local cache replicas - can be run on application servers and can be used for local caching. Replication can be used for local replicas for central shared cache.
- RLEC - Redis Lab Enterprise Cluster acts as container that can run multiple redis databases in a highly available and scalable manner.
- Zero touch service deployment - cloud (AWS, GCP, Azure, IBM) based deployment
- https://redislabs.com/redis-enterprise/technology/redis-enterprise-cluster-architecture/
- https://redislabs.com/redis-enterprise/technology/redis-enterprise-cluster-architecture/
Thursday, April 18, 2019
Redis capabilities - I'm impressed
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment