ApsaraDB for Memcache (formerly known as ApsaraDB for Memcache) is a seamlessly scalable distributed memory database service with high performance and reliability. Based on the Apsara distributed system and high‑performance storage, ApsaraDB for Memcache provides a complete set of solutions for master/slave hot backup, disaster recovery, business monitoring, data migration, and other scenarios.
ApsaraDB for Memcache supports the out‑of‑the‑box deployment mode, and relieves the database load for dynamic web applications by using the cache service, thus accelerating the overall response of the website.
Similar to the local Memcache databases, ApsaraDB for Memcache is compatible with the Memcached protocol. You can use it directly in your operating environment. The difference is that the hardware and data of ApsaraDB for Memcache are deployed in the cloud, which provides complete infrastructure, network security, and system maintenance services. All these services are billed on a Pay-As-You-Go basis.
Memcache Writer writes data into Memcache channels based on the Memcached protocol.
Currently, Memcache Writer supports only one write mode. Data types written in different modes are converted differently.
text: Memcache Writer serializes source data to the String type, and uses your fieldDelimiter as the delimiter.
binary: Currently not supported.
Description: Data source name. It must be identical to the data source name added. Adding data source is supported in script mode.
- Default value: None
Description: Memcache Writer writes data in the following modes.
- set: Store the data.
- add: Store the data only when this key does not exist (not supported currently).
- replace: Store the data only when this key exists (not supported currently).
- append: Store data after the existing key, and ignore exptime (not supported currently).
- prepend: Store data before the existing key, and ignore exptime (not supported currently).
Default value: None
Description: Currently, Memcache Writer supports writing data in only one format.
TEXT: Serialize the source data to the text format with the first field being the key written into Memcache, and all subsequent fields to the String type. Use fieldDelimiter that you specified as the delimiter to concatenate the text data into a complete string and write it into Memcache.
For example, the source data is:
| ID | NAME | COUNT |
| --------- |:-------|:-----|
| 23 | "CDP"| 100 |
If fieldDelimiter is specified as \^, the data format written into Memcache is.
| KEY (ApsaraDB for Memcache) | VALUE(ApsaraDB for Memcache) |
| --------- |:-------|
| 23 | CDP\^100 |
- Default value: None
Description: The cache invalidation time for the Memcache value. Currently, Memcache supports two types of the invalidation time.
- Unix time (number of seconds since January 1, 1970) indicates that data is invalid at a certain time point in the future.
The relative time (in seconds) starting from the current time point, which indicates the time length from the current time before data is invalid.
If the invalidation time is larger than 60*60*24*30 (30 days), the server identifies the invalidation time as the Unix time.
Default value: 0,0 (valid permanently)
Description: The quantity of records submitted in one operation. Setting this parameter can greatly reduce the interactions between CDP and Memcache over the network, and increase the overall throughput. However, an excessively large value may cause the running process of CDP to become out of memory. (Writing in batches is not supported for the current Memcache version.)
Default value: 1024
Currently, development in wizard mode is not supported.
Use the data generated from memory and imported into Memcache.
"fieldDelimiter": "if the writeFormat is text",