tencent cloud

Tencent Cloud Distributed Cache (Redis OSS-Compatible)

Release Notes and Announcements
Release Notes
Announcements
User Tutorial
Product Introduction
Overview
Product Strengths
Use Cases
Storage Engine
Product Series
Product Versions
Specifications and Performance
Read/Write Separation
Multi-AZ Deployment
Regions and AZs
Terms
Service Regions and Service Providers
Purchase Guide
Billing Overview
Pricing Center
Instance Purchasing
Renewal (Yearly/Monthly Subscription)
Refund (Yearly/Monthly Subscription)
Overdue Payments
Switching from Pay-as-You-Go to Yearly/Monthly Subscription
Getting Started
Quickly Creating an Instance
Connecting to Redis Instance
Operation Guide
Operation Overview
Connecting to a Database Instance
Managing Instances
Upgrade Instance
Management Node (Redis/ValKey Edition)
Multi-AZ Deployment Management
Backup and Restoration
Managing Accounts
Parameter Configuration
Slow Query
Access Management
Network and Security
Monitoring and Alarms
Event Management (Redis/ValKey Edition)
Data Migration
Global Replication for Redis Edition
Performance Optimization
Sentinel Mode
Development Guidelines
Naming Rules
Basic Usage Guidelines
Design Principles of Key and Value
Command Usage Guidelines
Design Principles of Client Programs
Connection Pool Configuration
Command Reference
Command Reference Overview
Redis Edition and Valkey Edition Command Compatibility
Version Command Usage Differences
Differences Between the Proxy Architecture and Direct Connection Mode
More Command Operations (Redis/Valkey Edition)
Memcached Edition Command Compatibility
Practical Tutorial
Building TencentDB for Redis® Client Monitoring Based on Spring Boot
Redis Client Connection Configuration Policy and Practice
Global SCAN Guide for Cluster Architecture
Eliminating Instances Securely
Hot Key and Big Key
AZ Migration Scheme
Troubleshooting
Connection Exception
Exception Analysis and Solution of Redisson Client Timeout Reconnection
Performance Troubleshooting and Fine-Tuning
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Parameter Management APIs
Other APIs
Backup and Restoration APIs
Region APIs
Monitoring and Management APIs
Log APIs
Data Types
Error Codes
FAQs
General
Connection and Login
Purchase
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us

Memcached Edition Command Compatibility

PDF
Focus Mode
Font Size
Last updated: 2026-03-17 18:11:00
Memcached Edition instances are compatible with the Memcached protocol and support the following commands: set, add, replace, append, prepend, cas, get, bget, gets, get_ext, gets_ext, delete, incr, decr.
Command
Compatible Version
Meaning
set
Memcached protocol 1.6
Set a key-value pair. If the key does not exist, it will create the key; if the key already exists, it will overwrite the old value.
add
Add a key-value pair to the cache, but only when the key does not exist. If the key already exists, however, the command does nothing.
replace
Replace a key-value pair in the cache, but only when the key already exists. If the key does not exist, however, the command does nothing.
append
Append data to the end of the existing value of a key. If the key does not exist, however, the command does nothing.
prepend
Prepend data to the beginning of the existing value of a key. If the key does not exist, however, the command does nothing.
cas
Compare and swap. This command first checks whether the current value of the key matches the provided value; if it does, the value is updated to the new one.
get
Retrieve the value of one or more keys from the cache. If no keys are found, an error will be returned.
bget
Batch Get. This is a binary protocol command used to retrieve the values of multiple keys from the cache.
gets
Similar to get, it obtains the value of a key in the cache and returns a version number.
get_ext
Extended binary protocol command that allows the client to specify more options to control the data retrieval process.
gets_ext
Extended command with versioning that allows the client to retrieve the value of a key while also obtaining a version number for subsequent atomic operations.
delete
Delete a key-value pair from the cache. If the key does not exist, however, the command does nothing.
incr
Increment the value of a key by a specified integer. If the key does not exist, an initial value can be specified. If the value of the key is not an integer, the operation will fail.
decr
Decrement the value of the key by the specified integer.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback