matchagreentea

4 ms·

1. 1.▲
   The hard things about sync(expertofobsolescence.substack.com)

   3 points by matchagreentea 2y ago|0 comments
2. 2.▲
   What I Learned About DynamoDB DAX(collectednotes.com)

   1 points by matchagreentea 6y ago|0 comments
3. 3.▲
   Sharing Socket for Fun and Profit(collectednotes.com)

   1 points by matchagreentea 6y ago|0 comments
4. 4.▲
   by matchagreentea 7y ago

   The blog post didn't fully specify, but the source code suggests that the locks are tracked per-partition rather than managed centrally.
5. 5.▲
   by matchagreentea 7y ago

   Part 2: https://wecode.wepay.com/posts/streaming-cassandra-at-wepay-...
6. 6.▲
   by matchagreentea 7y ago

   great question actually. There is a nuance in cassandra regarding to read-repair. If you issue a QUORUM read and the read itself failed (say, because 2/3 nodes are down), but succeeded on 1 node; and later on you read again when all th
7. 7.▲
   by matchagreentea 7y ago

   http://cassandra.apache.org/doc/latest/operating/cdc.html The high-level idea is hard-linking the commit log segment file in cdc directory as it is being written + have a separate index file to keep track of
8. 8.▲
   by matchagreentea 7y ago

   OP here. Thanks for the feedback! I totally agree with you that using a streaming approach seems like an overkill. Actually making the pipeline truly real-time is part of our future work for Cassandra CDC (This is mentioned in Part 2 of thi
9. 9.▲
   Streaming Cassandra at WePay(wecode.wepay.com)

   113 points by matchagreentea 7y ago|43 comments