void_star

This is really cool. Does anyone have pointers to relevant papers that inspired/influenced their type system?

Except no mention of vector clocks, so it's unclear how one would detect or repair a conflict. Maybe that is an implementation detail that is intended to be ironed out later...

It's a little unfortunate that consistency is only mentioned as a footnote. If this is being used internally at Netflix, how are they dealing with consistency issues in the face of failed or conflicting writes?

I'm reminded of a blogpost from 2012: http://medriscoll.com/post/9117396231/the-guild-of-silicon-v...

This should be titled "how I learned to stop worrying about memory fragmentation and love jemalloc."

On a slightly more serious note, jemalloc is a pretty incredible piece of systems software. If you're experiencing issues with memory fragmentation or lock contention in malloc(3) it's definitely worth looking at.

This might be slightly off topic but for harder to find parts you should check out Weird Stuff Warehouse in Sunnyvale (it's close to Yahoo). The people are pretty friendly and it's generally just a fun place to go poke around.

You might want to look into secure indices. It's still very new but seems to solve your problem.

How is this a startup? Auto-complete is NOT hard: it's a trie.