Redis with Java (Jedis, Lettuce) - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new Jedis client connection.

Redis

Jedis jedis = new Jedis([1]);

Drag options to blanks, or click blank then click option'

A"localhost"

B"127.0.0.1"

C"redis-server"

D"192.168.1.1"

Attempts:

3 left

💡 Hint

Common Mistakes

Using an incorrect IP address or hostname that does not point to the Redis server.

The Jedis client connects to Redis using the server address. "127.0.0.1" is the standard localhost IP.

2fill in blank

medium

Complete the code to set a key "user" with value "Alice" in Redis using Jedis.

Redis

jedis.[1]("user", "Alice");

Drag options to blanks, or click blank then click option'

Aset

Bget

Cdel

Dexists

Attempts:

3 left

💡 Hint

Common Mistakes

Using get which retrieves data instead of setting it.

The set method stores a value for a given key in Redis.

3fill in blank

hard

Fix the error in the Lettuce code to connect to Redis synchronously.

Redis

RedisClient client = RedisClient.create("redis://localhost:6379");
StatefulRedisConnection<String, String> connection = client.[1]();

Drag options to blanks, or click blank then click option'

Aconnect

BstartConnection

CopenConnection

DconnectAsync

Attempts:

3 left

💡 Hint

Common Mistakes

Using connectAsync() which returns a future, not a direct connection.

The connect() method opens a synchronous connection to Redis in Lettuce.

4fill in blank

hard

Fill both blanks to set and then get a key "count" using Jedis.

Redis

jedis.[1]("count", "10");
String value = jedis.[2]("count");

Drag options to blanks, or click blank then click option'

Aset

Bget

Cdel

Dexists

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to get a value before setting it.

Using del or exists instead of get.

First, set stores the value, then get retrieves it.

5fill in blank

hard

Fill all three blanks to create a Lettuce client, connect, and set a key "name" to "Bob".

Redis

RedisClient client = RedisClient.[1]("redis://localhost:6379");
StatefulRedisConnection<String, String> connection = client.[2]();
RedisCommands<String, String> commands = connection.[3]();
commands.set("name", "Bob");

Drag options to blanks, or click blank then click option'

Acreate

Bconnect

Csync

Dopen

Attempts:

3 left

💡 Hint

Common Mistakes

Using open instead of sync for commands.

Confusing connectAsync with connect.

Use create to make the client, connect to open connection, and sync to get synchronous commands.

Practice

1. What is the primary purpose of Jedis and Lettuce in Java applications?

easy

A. To connect and interact with Redis databases

B. To create graphical user interfaces

C. To manage Java threads

D. To compile Java code

Solution

1. Step 1: Understand Jedis and Lettuce roles

   Jedis and Lettuce are Java libraries designed to connect to Redis servers.

2. Step 2: Identify their main function

   They allow Java programs to store and retrieve data from Redis easily.

3. Final Answer:

   To connect and interact with Redis databases -> Option A

4. Quick Check:

   Jedis and Lettuce connect Java apps to Redis [OK]

Hint: Remember: Jedis and Lettuce are Redis clients for Java [OK]

Common Mistakes:

• Confusing Jedis/Lettuce with UI or threading libraries
• Thinking they compile Java code
• Assuming they manage Java memory

2. Which of the following is the correct way to create a Jedis connection in Java?

easy

A. Jedis jedis = new JedisClient("localhost");

B. Jedis jedis = Jedis.connect("localhost");

C. Jedis jedis = Jedis.create("localhost", 6379);

D. Jedis jedis = new Jedis("localhost", 6379);

Solution

1. Step 1: Recall Jedis connection syntax

   Jedis connections are created using the constructor with host and port: new Jedis("host", port).

2. Step 2: Verify options

   Only Jedis jedis = new Jedis("localhost", 6379); uses the correct constructor syntax: new Jedis("localhost", 6379); others use invalid methods or classes.

3. Final Answer:

   Jedis jedis = new Jedis("localhost", 6379); -> Option D

4. Quick Check:

   Use new Jedis(host, port) to connect [OK]

Hint: Use new Jedis("host", port) to create connection [OK]

Common Mistakes:

• Using non-existent methods like connect() or create()
• Confusing class names like JedisClient
• Omitting port number

3. Given the following Jedis code snippet, what will be the output?

Jedis jedis = new Jedis("localhost", 6379);
jedis.set("key1", "value1");
String val = jedis.get("key1");
System.out.println(val);
jedis.close();

medium

A. value1

B. null

C. key1

D. Throws an exception

Solution

1. Step 1: Analyze the set operation

   The code sets the key "key1" with value "value1" in Redis using jedis.set().

2. Step 2: Analyze the get operation and output

   Then it retrieves the value for "key1" with jedis.get(), which returns "value1". This is printed to the console.

3. Final Answer:

   value1 -> Option A

4. Quick Check:

   Set then get returns stored value [OK]

Hint: Set key then get key returns stored value [OK]

Common Mistakes:

• Expecting null if not connected properly
• Confusing key and value in output
• Forgetting to close connection causes resource leaks

4. Identify the error in this Lettuce code snippet:

RedisClient client = RedisClient.create("redis://localhost:6379");
StatefulRedisConnection connection = client.connect();
RedisCommands commands = connection.sync();
commands.set("name", "Alice");
System.out.println(commands.get("name"));
// Missing connection.close() and client.shutdown()

medium

A. Incorrect Redis URI format

B. Missing closing connection and shutting down client

C. Using sync() instead of async() causes error

D. Commands object should be created before connection

Solution

1. Step 1: Review resource management in Lettuce

   Connections and clients must be closed to avoid resource leaks.

2. Step 2: Identify missing cleanup calls

   The code lacks connection.close() and client.shutdown(), which are needed to release resources properly.

3. Final Answer:

   Missing closing connection and shutting down client -> Option B

4. Quick Check:

   Always close connection and shutdown client [OK]

Hint: Always close connection and shutdown client after use [OK]

Common Mistakes:

• Ignoring resource cleanup causing leaks
• Thinking sync() causes errors
• Misunderstanding URI format

5. You want to store multiple user scores in Redis using Jedis efficiently. Which approach is best to minimize network calls?

hard

A. Open and close connection for each set command

B. Call jedis.set() for each user score separately

C. Use pipelining to batch multiple set commands

D. Use multiple Jedis instances concurrently

Solution

1. Step 1: Understand network call overhead

   Calling jedis.set() repeatedly sends many network requests, slowing performance.

2. Step 2: Use pipelining to batch commands

   Pipelining batches commands to send them together, reducing network round-trips and improving speed.

3. Final Answer:

   Use pipelining to batch multiple set commands -> Option C

4. Quick Check:

   Pipelining batches commands to reduce network calls [OK]

Hint: Batch commands with pipelining to speed Redis writes [OK]

Common Mistakes:

• Opening/closing connection repeatedly wastes resources
• Using multiple Jedis instances unnecessarily
• Ignoring pipelining benefits