Quick Start
API keys are how your Redis compatible client can connect to Thiicket; they also represent seperate distinct namespaces with their own eviction policies and similar
This will open a message box asking you to configure your new API key
For this tutorial, set memory limit to 10485760 and the eviction policy to "Random". Once entered, select "Create" and a new API key will be presented
Open a Terminal / bash environment and set API_KEY to the value from above. Next let's connect to Thiicket using your new API key
When connecting to Thiicket, you have two options: explicitly select a region or let us route you to the nearest geographic region. For this tutorial we'll use the auto-routing feature
$ redis-cli -h connect.thiicket.com -a $API_KEY
Next, let's try some basic Redis commands
connect.thiicket.com:6379> SET myfirstkey "Hello world!"
OK
connect.thiicket.com:6379> GET myfirstkey
"Hello world!"
connect.thiicket.com:6379>
Create a new API key as by the above process, and set it in an environment variable called API_KEY_2
$ redis-cli -h connect.thiicket.com -a $API_KEY_2
connect.thiicket.com:6379> GET myfirstkey
(nil)
connect.thiicket.com:6379> SET myfirstkey "I'm in a different namespace!"
OK
connect.thiicket.com:6379> GET myfirstkey
"I'm in a different namespace!"
$ redis-cli -h connect.thiicket.com -a $API_KEY
connect.thiicket.com:6379> GET myfirstkey
"Hello world!"
As the above example shows, each API key is completely distinct from the other and each have their own namespace. Keys in different namespace cannot be accessed and updating a key in one does not affect the other
Namespaces are isolated at the regional level, two clients connecting to different regions will not have access to the same data
Last modified 3yr ago