Distributed counters pattern in Firebase - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Architecture

intermediate

Why use distributed counters in Firebase?

In Firebase, what is the main reason to use distributed counters instead of a single document counter?

A To prevent any writes from failing by locking the counter document.

B To avoid contention and improve write scalability by splitting increments across multiple documents.

C To reduce the total number of reads by storing all counts in one document.

D To ensure the counter value is always exactly consistent in real-time without delay.

💡 Hint

Think about what happens when many users try to update the same counter at once.

Distributed counters split increments across multiple documents to reduce write contention and improve scalability. A single document can become a bottleneck when many writes happen simultaneously.

❓ service_behavior

intermediate

Behavior of incrementing a distributed counter shard

Given a distributed counter with 5 shards, what happens when you increment one shard document in Firebase?

A The increment fails if the shard document does not exist.

B All shard documents increase their count by one simultaneously.

C The total count document is updated directly without changing shards.

D Only the shard document's count increases by one; the total count is the sum of all shards.

💡 Hint

Consider how distributed counters store counts across shards.

Each shard document holds part of the total count. Incrementing one shard increases only that shard's count. The total count is calculated by summing all shards.

❓ security

advanced

Securing distributed counter shards in Firebase

Which Firebase security rule best prevents unauthorized users from arbitrarily modifying distributed counter shard values?

A Allow writes only if the increment value is exactly 1 and the user is authenticated.

B Allow any write to shard documents without restrictions.

C Allow writes only if the user is an admin, ignoring increment values.

D Deny all writes to shard documents.

💡 Hint

Think about limiting increments to small controlled changes by trusted users.

Security rules should allow increments only of 1 by authenticated users to prevent tampering. Allowing unrestricted writes or denying all writes would either be insecure or prevent updates.

❓ Configuration

advanced

Configuring shard count for a distributed counter

You want to configure a distributed counter in Firebase to handle up to 1000 increments per second without contention. Which shard count is most appropriate?

A 100 shards to reduce contention while controlling cost.

B 10 shards to balance between performance and cost.

C 1 shard because it simplifies the design.

D 1000 shards to allow one increment per shard per second.

💡 Hint

More shards reduce contention but increase cost and complexity.

100 shards provide a good balance to handle 1000 increments per second by spreading writes, reducing contention, and controlling costs compared to 1000 shards.

🧠 Conceptual

expert

Calculating total count from distributed counter shards

You have a distributed counter with 4 shards having counts: 12, 15, 10, and 13. What is the total count returned when you read the counter?

A 40

B 12

C 50

D 15

💡 Hint

Sum all shard counts to get the total.

The total count is the sum of all shard counts: 12 + 15 + 10 + 13 = 50.