Problem this solves: Developers overuse shared objects, causing consensus slowdowns.

What you’ll learn:

When shared objects are unavoidable

How to design them for minimal contention

Sharding patterns

1. Good use cases

Orderbooks

Auction houses

Public registries

2. Bad use cases

Per-user data

Frequently updated counters

3. Sharding example

Instead of one GlobalLeaderboard, create LeaderboardSeason1, LeaderboardSeason2, etc., each as separate shared objects.