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

Comparison with Google Trillian #185

Open
domwoe opened this issue Apr 29, 2020 · 1 comment
Open

Comparison with Google Trillian #185

domwoe opened this issue Apr 29, 2020 · 1 comment

Comments

@domwoe
Copy link

domwoe commented Apr 29, 2020

Hi,
this is an interesting project!
Is there a comparison to Trillian anywhere?

@gdiazlo
Copy link
Contributor

gdiazlo commented May 14, 2020

I'm sorry for the delay to answer this. We're glad you find QED interesting.

We don't have a detailed comparison. We have talked with the Trillian guys before implementing QED. The goals are different, and so are the approaches.

QED focuses on a high write performance on a single big tree, while remaining at comparable query performance. The storage engine is an important part of QED. It works standalone while Trillian relays on a third party database.

Also, QED uses a history tree (see the referred papers for deep details about this) which allows us to emit proofs of the order on which the events where inserted.

We haven't published our testing yet, but we will, showing performance indicators such writes/second, memory and storage usage, etc.

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

No branches or pull requests

2 participants