Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial draft on how Sui works, what are its limitations, and more #711

Merged
merged 2 commits into from
Mar 10, 2022
Merged

Initial draft on how Sui works, what are its limitations, and more #711

merged 2 commits into from
Mar 10, 2022

Conversation

Clay-Mysten
Copy link
Contributor

Thanks so much for the excellent start and talk, Francois. Let me try to build upon what you have here. Thanks!

Copy link
Contributor

@asonnino asonnino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really good, I have the following two comments (but feel free to ignore if they are outside the scope of the document).

  • We may not want to give the impression that (i) sui can only handle single-writer objects, or that (ii) sui handle shared-objects like a cowboy (ie, locking only the individual resources while we send everything through consensus).
  • Do you want to talk about our sharding story here?

doc/src/sui_compared.md Outdated Show resolved Hide resolved
doc/src/sui_compared.md Outdated Show resolved Hide resolved
@Clay-Mysten
Copy link
Contributor Author

Francois, please take a look at and respond to Alberto's comments with your desired changes. Thanks!

@huitseeker
Copy link
Contributor

huitseeker commented Mar 9, 2022

Thanks a bunch @asonnino ! Pinging @gdanezis since I'm sorta stealing his TODO.

@Clay-Mysten Clay-Mysten merged commit 785c104 into MystenLabs:main Mar 10, 2022

Sui further expands this approach to more involved transactions that may explicilty depend on multiple elements under their sender's control, using an [object model][Objects] and leveraging [Move][Move]'s strong ownership model. By requiring that dependencies be explicit, Sui applies a "multi-lane" approach to transaction validation, making sure those independent transaction flows can progress without impediment from the others.

This doesn't mean that Sui is a platform never orders transactions with respect to each other, or that it we allows owners to only affect their owned microcosm of objects. Sui will also process transactions that have an effect on some shared state, in a rigorous, consensus-ordered manner. They're just not the default use case.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or that it we allows owners => or that if we allows owners ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants