Stop releasing bugs with fully automated end-to-end test coverage (Sponsored) Bugs sneak out when less than 80% of user flows are tested before shipping. But how do you get that kind of coverage? You either spend years scaling in-house QA — or you get there in just 4 months with QA Wolf
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."?
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!
Thank you for including JunoDB in the bytebytego newsletter. Your support means a lot to us!
Their API goes down all the time
Nice one.Thank you
When are they rewriting it in rust?
Nice article and it makes a lot of sense honestly, thank you.
Its impressive to bring a database up in a blink of an eye, that's some piece of work in architecting and coding it.
https://www.techlandbd.com/ups
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."?
Its quite fascinating to see how engineers are always evolving their solutions to complex problems