10 Comments
User's avatar
Uriel Bitton's avatar

Very interesting article and quite fascinating as well!

I wonder how it compares to AWS DynamoDB, being also a key-value datastore?

What kind of needs would make you choose one over the other?

Great post!

Expand full comment
Varun Sankar's avatar

Thank you for including JunoDB in the bytebytego newsletter. Your support means a lot to us!

Expand full comment
Zach's avatar

Their API goes down all the time

Expand full comment
Anoop MS's avatar

Nice one.Thank you

Expand full comment
Disruptive Concepts's avatar

When are they rewriting it in rust?

Expand full comment
Jamal Maison's avatar

Nice article and it makes a lot of sense honestly, thank you.

Expand full comment
javinpaul's avatar

Its impressive to bring a database up in a blink of an eye, that's some piece of work in architecting and coding it.

Expand full comment
Duke's avatar

Can you explain more into how JunoDB solves the problem of being CPU-bound rather than memory-bound?

To be more precise, can we have more details than "As a result, PayPal decided to rewrite the earlier version of JunoDB in Go to make it multi-core friendly and support high concurrency."?

Expand full comment
Leonardo Ramos Costa's avatar

Its quite fascinating to see how engineers are always evolving their solutions to complex problems

Expand full comment