Interactive queries in Kafka - Time & Space Complexity

Time Complexity: Interactive queries

O(1)

Understanding Time Complexity

When using interactive queries in Kafka, we want to know how the time to get data changes as the data grows.

We ask: How long does it take to find information when the data size increases?

Scenario Under Consideration

Analyze the time complexity of the following Kafka interactive query code snippet.

// Assume store is a Kafka Streams state store
ReadOnlyKeyValueStore<String, Integer> store = streams.store(
  StoreQueryParameters.fromNameAndType("counts-store", QueryableStoreTypes.keyValueStore())
);

// Query for a specific key
Integer count = store.get("word");

This code queries a local state store for a single key's value.

Identify Repeating Operations

Look for repeated actions that affect time.

• Primary operation: Retrieving a value by key from the local state store.
• How many times: Once per query call.

How Execution Grows With Input

The time to get a key depends on how the store is implemented, usually a key-value store like RocksDB or an in-memory map.

Input Size (n)	Approx. Operations
10	About 1 operation
100	About 1 operation
1000	About 1 operation

Pattern observation: The time stays roughly the same no matter how many keys are stored.

Final Time Complexity

Time Complexity: O(1)

This means getting a value by key takes about the same time, even if the store has many entries.

Common Mistake

[X] Wrong: "Querying a key takes longer as the store grows because it has to look through all entries."

[OK] Correct: The store uses efficient lookup structures, so it finds keys quickly without scanning everything.

Interview Connect

Understanding how interactive queries scale helps you explain how real-time data access stays fast even with lots of data.

Self-Check

"What if the store was a simple list instead of a key-value store? How would the time complexity change?"

Practice

1.

What is the main purpose of interactive queries in Kafka Streams?

easy

A. To create new Kafka topics dynamically

B. To write data back to Kafka topics

C. To read live state data directly from the Kafka Streams application

D. To monitor Kafka broker health status

Solution

1. Step 1: Understand interactive queries concept

   Interactive queries allow reading live state from Kafka Streams state stores.

2. Step 2: Identify the main use case

   The main use is to get real-time data from the app without extra databases.

3. Final Answer:

   To read live state data directly from the Kafka Streams application -> Option C

4. Quick Check:

   Interactive queries = read live state [OK]

Hint: Interactive queries read live state, not write or monitor [OK]

Common Mistakes:

• Confusing interactive queries with writing data
• Thinking it creates topics
• Assuming it monitors brokers

2.

Which of the following is the correct way to get a state store named myStore of type ReadOnlyKeyValueStore in Kafka Streams?

easy

A. store = streams.store("myStore", ReadOnlyKeyValueStore.class);

B. store = streams.getStore("myStore", ReadOnlyKeyValueStore);

C. store = streams.getStore("myStore", ReadOnlyKeyValueStore.class);

D. store = streams.store("myStore", ReadOnlyKeyValueStore);

Solution

1. Step 1: Recall Kafka Streams store retrieval syntax

   The correct method is streams.store(storeName, storeType.class) in Java.

2. Step 2: Match the correct syntax

   store = streams.store("myStore", ReadOnlyKeyValueStore.class); uses streams.store with class type, which is correct method name and syntax.

3. Final Answer:

   store = streams.store("myStore", ReadOnlyKeyValueStore.class); -> Option A

4. Quick Check:

   Use streams.store with class type [OK]

Hint: Use streams.store("name", StoreClass.class) syntax [OK]

Common Mistakes:

• Using streams.getStore instead of streams.store
• Omitting .class for type
• Passing type without .class

3.

Given the following code snippet in a Kafka Streams app, what will be the output if the key "user123" exists with value "active" in the state store?

var store = streams.store("userStatusStore", ReadOnlyKeyValueStore.class);
var status = store.get("user123");
System.out.println(status);

medium

A. null

B. "active"

C. Throws NullPointerException

D. Compilation error

Solution

1. Step 1: Understand store.get(key) behavior

   The get method returns the value for the key if it exists, else null.

2. Step 2: Check given key and value

   Since "user123" exists with value "active", store.get("user123") returns "active".

3. Final Answer:

   "active" -> Option B

4. Quick Check:

   store.get(existingKey) = value [OK]

Hint: store.get(key) returns value or null if missing [OK]

Common Mistakes:

• Assuming null is returned even if key exists
• Expecting exceptions on missing keys
• Confusing syntax causing compile errors

4.

Identify the error in this Kafka Streams interactive query code snippet:

var store = streams.store("ordersStore", ReadOnlyKeyValueStore.class);
var order = store.get(12345);
System.out.println(order);

medium

A. Passing integer key instead of string key

B. Missing try-catch block for exceptions

C. Using streams.store instead of streams.getStore

D. Incorrect store type ReadOnlyKeyValueStore

Solution

1. Step 1: Check method to get state store

   The method streams.store is correct.

2. Step 2: Validate key type and store type

   Key type mismatch: passing integer 12345 instead of string key (common for ordersStore).

3. Final Answer:

   Passing integer key instead of string key -> Option A

4. Quick Check:

   Key type must match store definition [OK]

Hint: Use correct key type in store.get(key) [OK]

Common Mistakes:

• Passing int literal without quotes for string keys
• Assuming key type must be string always
• Ignoring exception handling (not mandatory here)

5.

You want to build a real-time dashboard that shows the current count of active users using Kafka Streams interactive queries. Which approach best fits this requirement?

hard

A. Write user statuses to a separate database and query it periodically

B. Store counts in a local variable updated by Kafka Streams processors

C. Use Kafka consumer to read all user status events and aggregate externally

D. Use a ReadOnlyKeyValueStore to store user statuses and query counts live

Solution

1. Step 1: Identify real-time state storage method

   Kafka Streams state stores hold live data accessible via interactive queries.

2. Step 2: Choose best approach for live dashboard

   Using ReadOnlyKeyValueStore allows querying current counts directly without extra DB.

3. Final Answer:

   Use a ReadOnlyKeyValueStore to store user statuses and query counts live -> Option D

4. Quick Check:

   Interactive queries + state store = real-time dashboard [OK]

Hint: Use state store with interactive queries for live data [OK]

Common Mistakes:

• Relying on external DB instead of state store
• Polling Kafka consumer instead of querying store
• Using local variables which are not shared state