4 ms·

Sounds neat! What's the performance tradeoff, if any? How far along development is it? Beta? Production ready?

• david927 11y ago
  Thank you so much! I don't have direct competitive benchmarks but it reads and writes at around 620k/qps. It's in alpha right now at about 80% of completion.
  • ibdknox 11y ago
    You have symmetric read and write rates? That's pretty odd. Also if you are writing at that rate, presumably those writes aren't persisted? EDIT: That's also a rate of 1.6us per query. I've never heard of a JSON/REST stack that could take in and return results in that period of time. Are you doing something special to accomplish that?
    • david927 11y ago
      I couldn't remember the write speed but it's about 80% of the read speed. The writes are persisted. The qps rates are for individual look-ups and do not include any HTTP latency, of course.