text
stringlengths
0
1.82k
[2683.48 --> 2684.02] familiar with
[2684.02 --> 2685.08] RocksDB and
[2685.08 --> 2685.50] some of those
[2685.50 --> 2685.92] things, that's
[2685.92 --> 2686.42] fun.
[2686.88 --> 2687.36] I'm getting to
[2687.36 --> 2687.76] learn how
[2687.76 --> 2688.62] log-structured
[2688.62 --> 2689.34] merge trees
[2689.34 --> 2689.78] work.
[2690.14 --> 2690.92] Cassandra uses
[2690.92 --> 2691.82] the same
[2691.82 --> 2692.60] approach there.
[2692.60 --> 2695.04] Another project
[2695.04 --> 2695.72] that I've been
[2695.72 --> 2696.28] following for a
[2696.28 --> 2696.92] long time but
[2696.92 --> 2697.90] really only
[2697.90 --> 2698.58] recently has
[2698.58 --> 2699.28] started to
[2699.28 --> 2701.22] mature is
[2701.22 --> 2701.98] Shield from
[2701.98 --> 2702.58] Stark and
[2702.58 --> 2703.14] Wayne on
[2703.14 --> 2703.38] GitHub.
[2704.12 --> 2705.20] You guys may
[2705.20 --> 2706.50] remember Dr.
[2706.60 --> 2707.02] Nick from
[2707.02 --> 2707.38] the Ruby
[2707.38 --> 2707.82] world.
[2708.82 --> 2709.36] He seems to
[2709.36 --> 2710.74] have endorsed
[2710.74 --> 2711.40] Go or
[2711.40 --> 2712.26] embraced Go.
[2713.24 --> 2714.58] This tool
[2714.58 --> 2715.48] Shield is
[2715.48 --> 2718.48] almost a
[2718.48 --> 2719.76] universal utility
[2719.76 --> 2720.30] knife for
[2720.30 --> 2720.98] backing things
[2720.98 --> 2721.22] up.
[2721.42 --> 2721.90] You can write
[2721.90 --> 2722.52] plugins to
[2722.52 --> 2723.54] back up
[2723.54 --> 2724.62] Redis.
[2724.78 --> 2725.00] You can
[2725.00 --> 2726.66] back up a
[2726.66 --> 2726.96] database.
[2727.28 --> 2727.44] You can
[2727.44 --> 2728.10] back up a
[2728.10 --> 2728.40] disk.
[2728.54 --> 2728.80] You can
[2728.80 --> 2729.30] back up
[2729.30 --> 2730.20] anything if
[2730.20 --> 2730.74] you write a
[2730.74 --> 2731.26] plugin for
[2731.26 --> 2731.52] it.
[2732.00 --> 2733.30] Shield, when
[2733.30 --> 2733.88] it first came
[2733.88 --> 2735.02] out, I read
[2735.02 --> 2735.62] the code because
[2735.62 --> 2736.00] there was no
[2736.00 --> 2736.64] description in
[2736.64 --> 2737.78] GitHub and
[2737.78 --> 2738.54] just tried to
[2738.54 --> 2739.00] guess what it
[2739.00 --> 2739.48] was going to
[2739.48 --> 2740.00] do eventually.
[2740.44 --> 2741.04] I couldn't
[2741.04 --> 2741.50] figure it out
[2741.50 --> 2742.08] for quite a
[2742.08 --> 2742.46] few months.
[2743.10 --> 2743.84] Now it's
[2743.84 --> 2744.48] matured quite a
[2744.48 --> 2745.02] bit and it
[2745.02 --> 2745.72] looks to be a
[2745.72 --> 2746.12] really nice
[2746.12 --> 2746.54] tool for
[2746.54 --> 2747.24] backing up all
[2747.24 --> 2747.74] the things.
[2748.78 --> 2749.62] I briefly
[2749.62 --> 2750.04] looked at
[2750.04 --> 2750.18] that.
[2750.26 --> 2750.50] I need to
[2750.50 --> 2750.92] find a use
[2750.92 --> 2751.58] case for it.
[2751.90 --> 2753.70] I like the
[2753.70 --> 2754.22] idea that you
[2754.22 --> 2755.34] can wire up
[2755.34 --> 2756.84] where it's
[2756.84 --> 2757.26] pulling the
[2757.26 --> 2758.04] data from and
[2758.04 --> 2758.38] where it's
[2758.38 --> 2758.76] pushing the
[2758.76 --> 2759.22] data to.
[2760.16 --> 2760.90] I need more
[2760.90 --> 2761.30] time.
[2761.98 --> 2762.72] Almost like the
[2762.72 --> 2763.36] concept of
[2763.36 --> 2763.96] Hekka we were