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.

Publication

Aug 22, 2025

Article

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

Orderbooks

Auction houses

Public registries

Per-user data

Frequently updated counters

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

Commentaires

Aug 23 2025, 00:52

Why is it generally a bad idea to store per-user data in a shared object on Sui?

Sui is a Layer 1 protocol blockchain designed as the first internet-scale programmable blockchain platform.

848Publications2233Réponses

Gagne des points de réputation et obtiens des récompenses pour avoir aidé la communauté Sui à se développer.

Campagne de RécompensesAoût

Publications de primes