Caching
Managed Memcached on your own cluster
The simplest cache there is: a flat in-memory key-value store with no persistence, which is what Django, Rails, Laravel and PHP sessions expect.
Created inside a project, beside the apps that use it. Each project gets its own instance, storage and credentials.
01What it does
Memcached, run for you
Memcached on Anyport's own chart.
No data types, no persistence, no configuration to speak of: a flat key-value store in memory, which is exactly what the framework cache backends were written against. When it fills, the least recently used items are dropped.
One option, the memory size. Bound apps get the host and port, and a SERVERS value in the form the client libraries take.
02Options
What you choose
What the console asks when you create it, in the catalog's own numbers. Anything marked chosen once cannot change without creating a new instance.
- Sizes
- small 192MB, medium 896MB, large 3.8GB of memory
- Storage
- None; it is a cache
- Pause
- Yes
03Binding
What your app receives
Bind it to an app and these arrive as environment variables. The values are generated once into a secret and reach the app from there, rather than as something you copy.
- MEMCACHED_HOST
- MEMCACHED_PORT
- MEMCACHED_SERVERS
04Adding it
Add Memcached to a project
The same four steps as every service in the catalog.
- 01Open a project and go to Services.
- 02Pick it from the catalog and choose its options. Only the size is required; everything else has a default.
- 03Create it. Anyport installs it into the project's namespace, generates its credentials into a secret there, and tracks its health.
- 04Bind it to an app. The connection details arrive as environment variables, and rotating the credential never means editing an app.