Writing a very fast cache service with millions of entries in Go

Post by im_down_w_otp » Thu, Mar 31, 2016, 5:48 PM UTC

chris_va wrote: post #89

im_down_w_otp wrote: post #82

Earlier quoted context omitted.

Well, for starters Google Spanner has almost nothing to do with CRDTs. For another it would be really weird for Spanner to expose something CRDT shaped since Spanner is a strongly-consistent distributed database which depends heavily on global order and read/write locks driven by meticulously coordinated multi-site global wall-clock time and consensus groups. In some ways it's almost the opposite of what I want... wi…

Read/write locks... No, it's slightly more lazy in that that. It does timestamp coordination, but retrospectively.

You mean except for the lock table that's maintained by every paxos leader?

Post by andersen1488 » Fri, Apr 01, 2016, 1:58 PM UTC

endymi0n wrote: post #38

I still don’t get why people try writing their own data store, especially in a language that's simply not very well suited to that task (and we're an almost 100% Golang shop here). Seems to be a rite of passage. The requirements are literally Public service announcement: Don't write your own data store. Repeat after me: Don't write your own data store, except if you want to experimentally find out how to build data s…

> Don't write your own data store

I wish more people had this attitude. The amount of times I have seen people re-implementing something that PhD's have been perfecting since the 70's... it's cringe worthy.

Re: Writing a very fast cache service with millions of entries in Go

Re: Writing a very fast cache service with millions of entries in Go