WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:10.770 align:start position:0% [Applause] 00:00:10.770 --> 00:00:10.780 align:start position:0% 00:00:10.780 --> 00:00:14.500 align:start position:0% all<00:00:11.780> right<00:00:11.930> we're<00:00:12.710> gonna<00:00:13.059> hi<00:00:14.059> everybody 00:00:14.500 --> 00:00:14.510 align:start position:0% all right we're gonna hi everybody 00:00:14.510 --> 00:00:18.790 align:start position:0% all right we're gonna hi everybody eg<00:00:15.320> and<00:00:15.710> this<00:00:16.309> is<00:00:16.460> Jeep<00:00:16.760> and<00:00:16.970> we<00:00:17.570> are<00:00:18.050> members<00:00:18.650> I 00:00:18.790 --> 00:00:18.800 align:start position:0% eg and this is Jeep and we are members I 00:00:18.800 --> 00:00:20.440 align:start position:0% eg and this is Jeep and we are members I think<00:00:19.340> since<00:00:19.520> we're<00:00:19.640> not<00:00:19.939> here<00:00:20.119> here<00:00:20.360> at 00:00:20.440 --> 00:00:20.450 align:start position:0% think since we're not here here at 00:00:20.450 --> 00:00:28.630 align:start position:0% think since we're not here here at project<00:00:25.869> today<00:00:26.869> we're<00:00:27.050> here<00:00:27.170> talking<00:00:27.500> to<00:00:27.830> talk 00:00:28.630 --> 00:00:28.640 align:start position:0% project today we're here talking to talk 00:00:28.640 --> 00:00:30.000 align:start position:0% project today we're here talking to talk to<00:00:28.760> you<00:00:28.820> about<00:00:28.880> our<00:00:29.270> open<00:00:29.570> architecture 00:00:30.000 --> 00:00:30.010 align:start position:0% to you about our open architecture 00:00:30.010 --> 00:00:33.369 align:start position:0% to you about our open architecture initiative<00:00:31.010> it's<00:00:31.780> really<00:00:32.780> great<00:00:32.989> to<00:00:33.020> be<00:00:33.170> back 00:00:33.369 --> 00:00:33.379 align:start position:0% initiative it's really great to be back 00:00:33.379 --> 00:00:39.850 align:start position:0% initiative it's really great to be back here<00:00:33.680> at<00:00:35.620> yeah<00:00:36.620> all<00:00:36.980> right<00:00:38.530> this<00:00:39.530> place<00:00:39.710> is 00:00:39.850 --> 00:00:39.860 align:start position:0% here at yeah all right this place is 00:00:39.860 --> 00:00:41.380 align:start position:0% here at yeah all right this place is always<00:00:40.010> in<00:00:40.250> all<00:00:40.430> this<00:00:40.550> special<00:00:40.940> place<00:00:41.150> in<00:00:41.300> our 00:00:41.380 --> 00:00:41.390 align:start position:0% always in all this special place in our 00:00:41.390 --> 00:00:43.479 align:start position:0% always in all this special place in our hearts<00:00:41.720> because<00:00:42.080> we<00:00:42.110> watched<00:00:42.589> it<00:00:42.890> Def<00:00:43.070> Con<00:00:43.339> in 00:00:43.479 --> 00:00:43.489 align:start position:0% hearts because we watched it Def Con in 00:00:43.489 --> 00:00:46.840 align:start position:0% hearts because we watched it Def Con in Shanghai<00:00:44.229> just<00:00:45.229> over<00:00:45.559> three<00:00:45.890> years<00:00:45.920> ago<00:00:46.250> and 00:00:46.840 --> 00:00:46.850 align:start position:0% Shanghai just over three years ago and 00:00:46.850 --> 00:00:49.930 align:start position:0% Shanghai just over three years ago and obviously<00:00:47.600> the<00:00:48.080> agreement<00:00:48.559> good<00:00:48.680> system<00:00:49.129> has 00:00:49.930 --> 00:00:49.940 align:start position:0% obviously the agreement good system has 00:00:49.940 --> 00:00:51.430 align:start position:0% obviously the agreement good system has seen<00:00:50.089> a<00:00:50.239> huge<00:00:50.449> amount<00:00:50.690> of<00:00:50.750> growth<00:00:50.870> in<00:00:51.199> that 00:00:51.430 --> 00:00:51.440 align:start position:0% seen a huge amount of growth in that 00:00:51.440 --> 00:00:54.460 align:start position:0% seen a huge amount of growth in that amount<00:00:51.650> of<00:00:51.830> time<00:00:52.059> our<00:00:53.059> team<00:00:53.330> has<00:00:53.570> grown<00:00:53.600> our 00:00:54.460 --> 00:00:54.470 align:start position:0% amount of time our team has grown our 00:00:54.470 --> 00:00:56.860 align:start position:0% amount of time our team has grown our architecture<00:00:55.220> is<00:00:55.309> pretty<00:00:55.580> much<00:00:55.699> unrecognized 00:00:56.860 --> 00:00:56.870 align:start position:0% architecture is pretty much unrecognized 00:00:56.870 --> 00:00:59.529 align:start position:0% architecture is pretty much unrecognized analysis<00:00:57.620> but<00:00:57.890> we<00:00:57.920> have<00:00:58.190> created<00:00:58.399> ship<00:00:58.850> and 00:00:59.529 --> 00:00:59.539 align:start position:0% analysis but we have created ship and 00:00:59.539 --> 00:01:02.080 align:start position:0% analysis but we have created ship and that's<00:01:00.289> really<00:01:00.530> what<00:01:00.829> this<00:01:00.980> talk<00:01:01.040> is<00:01:01.280> about<00:01:01.460> me 00:01:02.080 --> 00:01:02.090 align:start position:0% that's really what this talk is about me 00:01:02.090 --> 00:01:04.479 align:start position:0% that's really what this talk is about me we<00:01:02.629> entered<00:01:03.140> into<00:01:03.379> this<00:01:03.500> space<00:01:03.829> because<00:01:04.280> we 00:01:04.479 --> 00:01:04.489 align:start position:0% we entered into this space because we 00:01:04.489 --> 00:01:07.870 align:start position:0% we entered into this space because we saw<00:01:04.810> that<00:01:05.810> people<00:01:05.960> were<00:01:06.110> having<00:01:06.619> with<00:01:07.009> trying 00:01:07.870 --> 00:01:07.880 align:start position:0% saw that people were having with trying 00:01:07.880 --> 00:01:09.730 align:start position:0% saw that people were having with trying to<00:01:07.940> enter<00:01:08.240> let<00:01:08.450> three<00:01:08.720> explore<00:01:09.140> with<00:01:09.380> what 00:01:09.730 --> 00:01:09.740 align:start position:0% to enter let three explore with what 00:01:09.740 --> 00:01:10.359 align:start position:0% to enter let three explore with what could<00:01:09.860> be<00:01:09.950> deadly 00:01:10.359 --> 00:01:10.369 align:start position:0% could be deadly 00:01:10.369 --> 00:01:12.340 align:start position:0% could be deadly notice<00:01:10.729> my<00:01:10.909> contracts<00:01:11.659> and<00:01:11.840> building<00:01:12.200> things 00:01:12.340 --> 00:01:12.350 align:start position:0% notice my contracts and building things 00:01:12.350 --> 00:01:14.830 align:start position:0% notice my contracts and building things on<00:01:12.619> top<00:01:12.830> of<00:01:12.890> it<00:01:13.070> their<00:01:13.280> name<00:01:13.430> and<00:01:14.149> we<00:01:14.600> thought 00:01:14.830 --> 00:01:14.840 align:start position:0% on top of it their name and we thought 00:01:14.840 --> 00:01:17.499 align:start position:0% on top of it their name and we thought needed<00:01:14.960> up<00:01:15.200> with<00:01:15.350> that<00:01:15.530> and<00:01:16.460> one<00:01:17.330> of<00:01:17.420> the 00:01:17.499 --> 00:01:17.509 align:start position:0% needed up with that and one of the 00:01:17.509 --> 00:01:19.960 align:start position:0% needed up with that and one of the things<00:01:17.750> that<00:01:18.440> we<00:01:18.710> want<00:01:18.920> to<00:01:19.009> be<00:01:19.130> now<00:01:19.310> is<00:01:19.580> share 00:01:19.960 --> 00:01:19.970 align:start position:0% things that we want to be now is share 00:01:19.970 --> 00:01:21.760 align:start position:0% things that we want to be now is share our<00:01:20.240> lessons<00:01:20.690> learned<00:01:20.750> over<00:01:21.140> the<00:01:21.320> last<00:01:21.350> three 00:01:21.760 --> 00:01:21.770 align:start position:0% our lessons learned over the last three 00:01:21.770 --> 00:01:24.340 align:start position:0% our lessons learned over the last three years<00:01:21.800> talk<00:01:22.430> about<00:01:22.729> what<00:01:23.509> work<00:01:23.659> for<00:01:23.899> us<00:01:24.020> within 00:01:24.340 --> 00:01:24.350 align:start position:0% years talk about what work for us within 00:01:24.350 --> 00:01:27.700 align:start position:0% years talk about what work for us within and<00:01:25.119> just<00:01:26.119> continue<00:01:26.690> the<00:01:26.780> sugar<00:01:27.020> experiences 00:01:27.700 --> 00:01:27.710 align:start position:0% and just continue the sugar experiences 00:01:27.710 --> 00:01:29.560 align:start position:0% and just continue the sugar experiences and<00:01:27.890> I<00:01:27.979> started<00:01:28.430> going<00:01:28.729> forward<00:01:29.119> and<00:01:29.450> that's 00:01:29.560 --> 00:01:29.570 align:start position:0% and I started going forward and that's 00:01:29.570 --> 00:01:31.570 align:start position:0% and I started going forward and that's what<00:01:29.990> this<00:01:30.080> exact<00:01:30.530> texture<00:01:30.890> Michigan<00:01:31.460> is 00:01:31.570 --> 00:01:31.580 align:start position:0% what this exact texture Michigan is 00:01:31.580 --> 00:01:35.529 align:start position:0% what this exact texture Michigan is about<00:01:33.100> so<00:01:34.100> talking<00:01:34.850> about<00:01:35.030> see<00:01:35.240> them<00:01:35.420> in 00:01:35.529 --> 00:01:35.539 align:start position:0% about so talking about see them in 00:01:35.539 --> 00:01:39.480 align:start position:0% about so talking about see them in architecture<00:01:36.289> it's<00:01:36.440> my<00:01:36.590> whatever<00:01:37.009> we<00:01:37.250> all<00:01:37.280> got 00:01:39.480 --> 00:01:39.490 align:start position:0% architecture it's my whatever we all got 00:01:39.490 --> 00:01:42.190 align:start position:0% architecture it's my whatever we all got watching<00:01:40.490> we<00:01:40.759> all<00:01:40.880> serve<00:01:41.149> that<00:01:41.479> same<00:01:41.780> place<00:01:42.050> to 00:01:42.190 --> 00:01:42.200 align:start position:0% watching we all serve that same place to 00:01:42.200 --> 00:01:44.919 align:start position:0% watching we all serve that same place to start<00:01:42.409> rendering<00:01:42.619> or<00:01:43.280> claim<00:01:43.550> if<00:01:44.300> next<00:01:44.659> to<00:01:44.840> the 00:01:44.919 --> 00:01:44.929 align:start position:0% start rendering or claim if next to the 00:01:44.929 --> 00:01:47.350 align:start position:0% start rendering or claim if next to the network<00:01:45.289> and<00:01:45.679> you<00:01:46.100> start<00:01:46.399> throwing<00:01:47.179> some 00:01:47.350 --> 00:01:47.360 align:start position:0% network and you start throwing some 00:01:47.360 --> 00:01:50.109 align:start position:0% network and you start throwing some requests<00:01:47.840> for<00:01:47.899> data<00:01:48.200> whether<00:01:49.039> that's<00:01:49.340> give<00:01:50.030> me 00:01:50.109 --> 00:01:50.119 align:start position:0% requests for data whether that's give me 00:01:50.119 --> 00:01:53.850 align:start position:0% requests for data whether that's give me this<00:01:50.240> list<00:01:50.479> of<00:01:50.539> transactions<00:01:51.319> of<00:01:51.619> the<00:01:51.740> back 00:01:53.850 --> 00:01:53.860 align:start position:0% this list of transactions of the back 00:01:53.860 --> 00:01:55.440 align:start position:0% this list of transactions of the back you're<00:01:54.340> interacting<00:01:54.730> with<00:01:54.940> people<00:01:55.150> dead 00:01:55.440 --> 00:01:55.450 align:start position:0% you're interacting with people dead 00:01:55.450 --> 00:01:57.510 align:start position:0% you're interacting with people dead that's<00:01:55.660> terribly<00:01:56.020> installed<00:01:56.770> on<00:01:56.920> your<00:01:57.040> laptop 00:01:57.510 --> 00:01:57.520 align:start position:0% that's terribly installed on your laptop 00:01:57.520 --> 00:02:00.180 align:start position:0% that's terribly installed on your laptop maybe<00:01:58.480> start<00:01:58.930> breaking<00:01:59.350> a<00:01:59.530> co-working<00:02:00.070> space 00:02:00.180 --> 00:02:00.190 align:start position:0% maybe start breaking a co-working space 00:02:00.190 --> 00:02:01.920 align:start position:0% maybe start breaking a co-working space with<00:02:00.640> some<00:02:00.850> people<00:02:01.090> and<00:02:01.450> they<00:02:01.510> started 00:02:01.920 --> 00:02:01.930 align:start position:0% with some people and they started 00:02:01.930 --> 00:02:04.440 align:start position:0% with some people and they started sharing<00:02:02.170> this<00:02:02.410> then<00:02:02.710> because<00:02:03.190> nobody<00:02:04.180> wants 00:02:04.440 --> 00:02:04.450 align:start position:0% sharing this then because nobody wants 00:02:04.450 --> 00:02:06.750 align:start position:0% sharing this then because nobody wants to<00:02:04.510> have<00:02:05.110> all<00:02:05.440> of<00:02:05.470> that<00:02:05.620> space<00:02:05.979> taken<00:02:06.490> up<00:02:06.580> on 00:02:06.750 --> 00:02:06.760 align:start position:0% to have all of that space taken up on 00:02:06.760 --> 00:02:09.540 align:start position:0% to have all of that space taken up on their<00:02:06.910> back<00:02:07.240> correctly<00:02:08.080> like<00:02:08.740> upload<00:02:09.220> or 00:02:09.540 --> 00:02:09.550 align:start position:0% their back correctly like upload or 00:02:09.550 --> 00:02:13.080 align:start position:0% their back correctly like upload or update<00:02:10.270> your<00:02:10.300> head<00:02:10.660> drive<00:02:10.899> so<00:02:11.880> what<00:02:12.880> you<00:02:13.000> end 00:02:13.080 --> 00:02:13.090 align:start position:0% update your head drive so what you end 00:02:13.090 --> 00:02:17.400 align:start position:0% update your head drive so what you end up<00:02:13.209> having<00:02:13.420> is<00:02:13.930> the<00:02:14.560> single<00:02:14.920> machine<00:02:16.410> and 00:02:17.400 --> 00:02:17.410 align:start position:0% up having is the single machine and 00:02:17.410 --> 00:02:19.410 align:start position:0% up having is the single machine and maybe<00:02:17.890> the<00:02:18.340> amount<00:02:18.520> of<00:02:18.640> requests<00:02:19.120> they<00:02:19.270> were 00:02:19.410 --> 00:02:19.420 align:start position:0% maybe the amount of requests they were 00:02:19.420 --> 00:02:22.440 align:start position:0% maybe the amount of requests they were like<00:02:19.900> they<00:02:20.080> are<00:02:20.290> starting<00:02:20.560> to<00:02:20.890> be<00:02:21.300> slower<00:02:22.300> than 00:02:22.440 --> 00:02:22.450 align:start position:0% like they are starting to be slower than 00:02:22.450 --> 00:02:25.800 align:start position:0% like they are starting to be slower than expected<00:02:23.160> and<00:02:24.160> latency<00:02:24.910> starts<00:02:25.330> to<00:02:25.420> increase 00:02:25.800 --> 00:02:25.810 align:start position:0% expected and latency starts to increase 00:02:25.810 --> 00:02:28.170 align:start position:0% expected and latency starts to increase and<00:02:26.320> you<00:02:27.130> end<00:02:27.280> up<00:02:27.370> trying<00:02:27.550> to<00:02:27.820> do<00:02:27.940> traditional 00:02:28.170 --> 00:02:28.180 align:start position:0% and you end up trying to do traditional 00:02:28.180 --> 00:02:30.360 align:start position:0% and you end up trying to do traditional wet<00:02:28.750> scaling<00:02:29.200> tactics<00:02:29.680> which<00:02:29.890> starts<00:02:30.280> with 00:02:30.360 --> 00:02:30.370 align:start position:0% wet scaling tactics which starts with 00:02:30.370 --> 00:02:33.180 align:start position:0% wet scaling tactics which starts with realities<00:02:31.080> that<00:02:32.080> just<00:02:32.350> means<00:02:32.560> throwing<00:02:32.860> more 00:02:33.180 --> 00:02:33.190 align:start position:0% realities that just means throwing more 00:02:33.190 --> 00:02:35.640 align:start position:0% realities that just means throwing more simple<00:02:33.640> resources<00:02:34.180> attic<00:02:34.480> but<00:02:35.050> that<00:02:35.230> it<00:02:35.470> takes 00:02:35.640 --> 00:02:35.650 align:start position:0% simple resources attic but that it takes 00:02:35.650 --> 00:02:38.400 align:start position:0% simple resources attic but that it takes you<00:02:35.920> so<00:02:36.160> far<00:02:36.190> at<00:02:36.820> some<00:02:37.090> point<00:02:37.450> these<00:02:37.750> service 00:02:38.400 --> 00:02:38.410 align:start position:0% you so far at some point these service 00:02:38.410 --> 00:02:41.430 align:start position:0% you so far at some point these service versus<00:02:39.060> skill<00:02:40.060> beyond<00:02:40.450> what<00:02:40.959> might<00:02:41.260> have 00:02:41.430 --> 00:02:41.440 align:start position:0% versus skill beyond what might have 00:02:41.440 --> 00:02:45.150 align:start position:0% versus skill beyond what might have access<00:02:41.830> to<00:02:41.890> a<00:02:42.130> solution<00:02:42.670> and<00:02:43.739> what<00:02:44.739> we've<00:02:44.890> seen 00:02:45.150 --> 00:02:45.160 align:start position:0% access to a solution and what we've seen 00:02:45.160 --> 00:02:47.640 align:start position:0% access to a solution and what we've seen is<00:02:45.220> that<00:02:45.400> developers<00:02:46.209> end<00:02:46.600> up<00:02:46.810> with<00:02:47.110> custom 00:02:47.640 --> 00:02:47.650 align:start position:0% is that developers end up with custom 00:02:47.650 --> 00:02:49.110 align:start position:0% is that developers end up with custom solutions<00:02:48.190> around<00:02:48.430> this<00:02:48.580> whether<00:02:48.850> that's 00:02:49.110 --> 00:02:49.120 align:start position:0% solutions around this whether that's 00:02:49.120 --> 00:02:52.500 align:start position:0% solutions around this whether that's custom<00:02:49.959> captioning<00:02:50.590> custom<00:02:50.950> API<00:02:51.100> is<00:02:51.510> about 00:02:52.500 --> 00:02:52.510 align:start position:0% custom captioning custom API is about 00:02:52.510 --> 00:02:53.670 align:start position:0% custom captioning custom API is about you<00:02:52.660> know<00:02:52.810> sort<00:02:53.080> of<00:02:53.200> like<00:02:53.260> scaffolding 00:02:53.670 --> 00:02:53.680 align:start position:0% you know sort of like scaffolding 00:02:53.680 --> 00:02:56.490 align:start position:0% you know sort of like scaffolding architecture<00:02:54.640> around<00:02:54.790> us<00:02:55.150> and<00:02:55.870> what<00:02:56.320> we've 00:02:56.490 --> 00:02:56.500 align:start position:0% architecture around us and what we've 00:02:56.500 --> 00:02:58.680 align:start position:0% architecture around us and what we've seen<00:02:56.739> but<00:02:57.130> there<00:02:57.519> is<00:02:57.670> a<00:02:57.700> smell<00:02:58.180> like<00:02:58.450> this 00:02:58.680 --> 00:02:58.690 align:start position:0% seen but there is a smell like this 00:02:58.690 --> 00:03:02.490 align:start position:0% seen but there is a smell like this inequality<00:02:59.440> of<00:03:00.190> data<00:03:00.730> between<00:03:01.480> the<00:03:01.690> relevant 00:03:02.490 --> 00:03:02.500 align:start position:0% inequality of data between the relevant 00:03:02.500 --> 00:03:05.150 align:start position:0% inequality of data between the relevant emails<00:03:02.860> depending<00:03:03.430> on<00:03:03.690> whether<00:03:04.690> or<00:03:04.840> not 00:03:05.150 --> 00:03:05.160 align:start position:0% emails depending on whether or not 00:03:05.160 --> 00:03:08.570 align:start position:0% emails depending on whether or not the<00:03:05.580> team<00:03:05.850> has<00:03:06.450> hard<00:03:07.260> expertise<00:03:07.830> like<00:03:08.340> wet 00:03:08.570 --> 00:03:08.580 align:start position:0% the team has hard expertise like wet 00:03:08.580 --> 00:03:11.450 align:start position:0% the team has hard expertise like wet skill<00:03:08.970> or<00:03:09.510> they<00:03:10.080> have<00:03:10.320> the<00:03:11.100> amount<00:03:11.340> of 00:03:11.450 --> 00:03:11.460 align:start position:0% skill or they have the amount of 00:03:11.460 --> 00:03:13.100 align:start position:0% skill or they have the amount of resources<00:03:11.940> and<00:03:12.090> science<00:03:12.480> dive<00:03:12.720> into<00:03:12.870> this 00:03:13.100 --> 00:03:13.110 align:start position:0% resources and science dive into this 00:03:13.110 --> 00:03:16.160 align:start position:0% resources and science dive into this kind<00:03:13.410> of<00:03:13.500> culture<00:03:13.830> and<00:03:14.760> so<00:03:15.090> that's<00:03:15.810> what<00:03:16.050> we're 00:03:16.160 --> 00:03:16.170 align:start position:0% kind of culture and so that's what we're 00:03:16.170 --> 00:03:18.470 align:start position:0% kind of culture and so that's what we're trying<00:03:16.350> to<00:03:16.530> be<00:03:16.680> able<00:03:16.740> is<00:03:17.030> its<00:03:18.030> share<00:03:18.270> my 00:03:18.470 --> 00:03:18.480 align:start position:0% trying to be able is its share my 00:03:18.480 --> 00:03:20.890 align:start position:0% trying to be able is its share my information<00:03:18.660> about<00:03:19.260> what's<00:03:19.470> worked<00:03:19.740> for<00:03:19.800> us 00:03:20.890 --> 00:03:20.900 align:start position:0% information about what's worked for us 00:03:20.900 --> 00:03:23.690 align:start position:0% information about what's worked for us they're<00:03:21.900> different<00:03:22.140> types<00:03:22.680> of<00:03:22.860> user<00:03:23.100> profiles 00:03:23.690 --> 00:03:23.700 align:start position:0% they're different types of user profiles 00:03:23.700 --> 00:03:26.750 align:start position:0% they're different types of user profiles that<00:03:23.940> use<00:03:24.270> the<00:03:24.810> Dearing<00:03:25.170> knows<00:03:25.550> or<00:03:26.550> the 00:03:26.750 --> 00:03:26.760 align:start position:0% that use the Dearing knows or the 00:03:26.760 --> 00:03:28.700 align:start position:0% that use the Dearing knows or the majority<00:03:27.030> of<00:03:27.210> these<00:03:27.480> days<00:03:27.690> all<00:03:28.110> you're<00:03:28.320> doing 00:03:28.700 --> 00:03:28.710 align:start position:0% majority of these days all you're doing 00:03:28.710 --> 00:03:30.710 align:start position:0% majority of these days all you're doing is<00:03:28.860> interacting<00:03:29.490> with<00:03:29.520> this<00:03:29.730> might<00:03:29.940> contract 00:03:30.710 --> 00:03:30.720 align:start position:0% is interacting with this might contract 00:03:30.720 --> 00:03:32.570 align:start position:0% is interacting with this might contract checking<00:03:31.410> myself<00:03:31.560> in<00:03:31.890> balance<00:03:32.280> in<00:03:32.400> summation 00:03:32.570 --> 00:03:32.580 align:start position:0% checking myself in balance in summation 00:03:32.580 --> 00:03:35.180 align:start position:0% checking myself in balance in summation about<00:03:33.030> you<00:03:33.480> these<00:03:33.960> are<00:03:34.350> all<00:03:34.620> these<00:03:34.830> in<00:03:35.130> the 00:03:35.180 --> 00:03:35.190 align:start position:0% about you these are all these in the 00:03:35.190 --> 00:03:37.400 align:start position:0% about you these are all these in the late<00:03:35.370> night<00:03:35.610> or<00:03:35.820> even<00:03:36.030> communities<00:03:36.570> and 00:03:37.400 --> 00:03:37.410 align:start position:0% late night or even communities and 00:03:37.410 --> 00:03:39.800 align:start position:0% late night or even communities and that's<00:03:37.590> pretty<00:03:37.770> sufficient<00:03:38.570> if<00:03:39.570> you're<00:03:39.780> a 00:03:39.800 --> 00:03:39.810 align:start position:0% that's pretty sufficient if you're a 00:03:39.810 --> 00:03:41.660 align:start position:0% that's pretty sufficient if you're a developer<00:03:40.170> the<00:03:40.560> hacker<00:03:40.800> on<00:03:41.070> and<00:03:41.310> we<00:03:41.400> tried<00:03:41.640> to 00:03:41.660 --> 00:03:41.670 align:start position:0% developer the hacker on and we tried to 00:03:41.670 --> 00:03:44.330 align:start position:0% developer the hacker on and we tried to do<00:03:42.030> something<00:03:42.300> that<00:03:42.540> it's<00:03:43.350> it's<00:03:44.220> really 00:03:44.330 --> 00:03:44.340 align:start position:0% do something that it's it's really 00:03:44.340 --> 00:03:45.620 align:start position:0% do something that it's it's really simply<00:03:44.700> these<00:03:44.820> days<00:03:45.060> we<00:03:45.210> probably<00:03:45.390> saw 00:03:45.620 --> 00:03:45.630 align:start position:0% simply these days we probably saw 00:03:45.630 --> 00:03:48.050 align:start position:0% simply these days we probably saw anything<00:03:46.020> away<00:03:46.200> it's<00:03:46.950> only<00:03:47.100> when<00:03:47.580> you<00:03:47.700> started 00:03:48.050 --> 00:03:48.060 align:start position:0% anything away it's only when you started 00:03:48.060 --> 00:03:50.030 align:start position:0% anything away it's only when you started trying<00:03:48.360> to<00:03:48.450> be<00:03:48.600> slightly<00:03:49.380> more<00:03:49.620> complex 00:03:50.030 --> 00:03:50.040 align:start position:0% trying to be slightly more complex 00:03:50.040 --> 00:03:52.310 align:start position:0% trying to be slightly more complex things<00:03:50.370> with<00:03:50.610> that<00:03:50.760> data<00:03:50.820> like<00:03:51.420> looking<00:03:52.200> at 00:03:52.310 --> 00:03:52.320 align:start position:0% things with that data like looking at 00:03:52.320 --> 00:03:54.440 align:start position:0% things with that data like looking at historical<00:03:53.130> information<00:03:53.400> which<00:03:53.820> mean<00:03:54.180> that 00:03:54.440 --> 00:03:54.450 align:start position:0% historical information which mean that 00:03:54.450 --> 00:03:57.320 align:start position:0% historical information which mean that you<00:03:55.200> start<00:03:55.470> needing<00:03:55.710> to<00:03:56.040> run<00:03:56.190> like 00:03:57.320 --> 00:03:57.330 align:start position:0% you start needing to run like 00:03:57.330 --> 00:03:59.720 align:start position:0% you start needing to run like or<00:03:57.480> a<00:03:57.510> whole<00:03:57.720> heart<00:03:57.930> kinda<00:03:58.380> and<00:03:58.590> we<00:03:59.490> get 00:03:59.720 --> 00:03:59.730 align:start position:0% or a whole heart kinda and we get 00:03:59.730 --> 00:04:02.750 align:start position:0% or a whole heart kinda and we get somewhere<00:04:00.120> we<00:04:00.300> turn<00:04:00.480> that<00:04:00.630> into<00:04:01.010> business 00:04:02.750 --> 00:04:02.760 align:start position:0% somewhere we turn that into business 00:04:02.760 --> 00:04:05.300 align:start position:0% somewhere we turn that into business I'm<00:04:03.060> watching<00:04:03.599> analytics<00:04:04.230> and<00:04:04.530> at<00:04:04.860> that<00:04:05.040> point 00:04:05.300 --> 00:04:05.310 align:start position:0% I'm watching analytics and at that point 00:04:05.310 --> 00:04:08.240 align:start position:0% I'm watching analytics and at that point meatless<00:04:05.909> lives<00:04:06.180> always<00:04:06.599> online<00:04:07.250> because 00:04:08.240 --> 00:04:08.250 align:start position:0% meatless lives always online because 00:04:08.250 --> 00:04:10.759 align:start position:0% meatless lives always online because maybe<00:04:08.489> you<00:04:08.730> built<00:04:09.030> an<00:04:09.299> API<00:04:09.930> on<00:04:10.019> top<00:04:10.440> of<00:04:10.620> it<00:04:10.739> that 00:04:10.759 --> 00:04:10.769 align:start position:0% maybe you built an API on top of it that 00:04:10.769 --> 00:04:14.089 align:start position:0% maybe you built an API on top of it that your<00:04:11.069> users<00:04:11.370> are<00:04:11.519> consuming<00:04:12.120> and<00:04:12.720> all<00:04:13.650> three 00:04:14.089 --> 00:04:14.099 align:start position:0% your users are consuming and all three 00:04:14.099 --> 00:04:15.860 align:start position:0% your users are consuming and all three of<00:04:14.129> these<00:04:14.400> types<00:04:14.670> of<00:04:14.849> things<00:04:14.909> our<00:04:15.180> parents<00:04:15.209> are 00:04:15.860 --> 00:04:15.870 align:start position:0% of these types of things our parents are 00:04:15.870 --> 00:04:18.170 align:start position:0% of these types of things our parents are using<00:04:16.049> the<00:04:16.320> same<00:04:16.560> underlying<00:04:17.549> that<00:04:17.880> variable 00:04:18.170 --> 00:04:18.180 align:start position:0% using the same underlying that variable 00:04:18.180 --> 00:04:20.449 align:start position:0% using the same underlying that variable and<00:04:18.479> software<00:04:18.989> the<00:04:19.590> darién<00:04:19.919> clients<00:04:20.340> were 00:04:20.449 --> 00:04:20.459 align:start position:0% and software the darién clients were 00:04:20.459 --> 00:04:22.340 align:start position:0% and software the darién clients were meant<00:04:20.699> to<00:04:20.760> be<00:04:20.910> vigorous<00:04:21.540> everybody<00:04:21.989> this<00:04:22.109> was 00:04:22.340 --> 00:04:22.350 align:start position:0% meant to be vigorous everybody this was 00:04:22.350 --> 00:04:24.409 align:start position:0% meant to be vigorous everybody this was have<00:04:22.560> access<00:04:22.919> to<00:04:23.040> same<00:04:23.310> software<00:04:23.760> and<00:04:24.060> we<00:04:24.180> get 00:04:24.409 --> 00:04:24.419 align:start position:0% have access to same software and we get 00:04:24.419 --> 00:04:26.750 align:start position:0% have access to same software and we get the<00:04:24.540> same<00:04:24.780> opportunity<00:04:25.680> to<00:04:25.710> access<00:04:26.250> this<00:04:26.460> data 00:04:26.750 --> 00:04:26.760 align:start position:0% the same opportunity to access this data 00:04:26.760 --> 00:04:29.330 align:start position:0% the same opportunity to access this data so<00:04:27.389> whether<00:04:27.540> we<00:04:27.720> were<00:04:27.870> in<00:04:27.990> Gaza<00:04:28.320> parity<00:04:28.889> or 00:04:29.330 --> 00:04:29.340 align:start position:0% so whether we were in Gaza parity or 00:04:29.340 --> 00:04:31.899 align:start position:0% so whether we were in Gaza parity or apparently<00:04:30.060> on<00:04:30.240> now 00:04:31.899 --> 00:04:31.909 align:start position:0% apparently on now 00:04:31.909 --> 00:04:34.909 align:start position:0% apparently on now all<00:04:32.909> three<00:04:33.360> of<00:04:33.479> these<00:04:33.659> user<00:04:34.080> profiles<00:04:34.650> here 00:04:34.909 --> 00:04:34.919 align:start position:0% all three of these user profiles here 00:04:34.919 --> 00:04:37.670 align:start position:0% all three of these user profiles here are<00:04:35.759> lending<00:04:36.030> the<00:04:36.210> same<00:04:36.419> software<00:04:36.870> and<00:04:37.530> it's 00:04:37.670 --> 00:04:37.680 align:start position:0% are lending the same software and it's 00:04:37.680 --> 00:04:39.680 align:start position:0% are lending the same software and it's not<00:04:37.860> as<00:04:38.009> fairly<00:04:38.280> tailored<00:04:38.759> to<00:04:39.000> a<00:04:39.030> stereo<00:04:39.539> these 00:04:39.680 --> 00:04:39.690 align:start position:0% not as fairly tailored to a stereo these 00:04:39.690 --> 00:04:44.300 align:start position:0% not as fairly tailored to a stereo these days<00:04:39.930> so<00:04:42.229> when<00:04:43.229> you<00:04:43.349> think<00:04:43.500> about<00:04:43.620> it<00:04:44.009> during<00:04:44.190> a 00:04:44.300 --> 00:04:44.310 align:start position:0% days so when you think about it during a 00:04:44.310 --> 00:04:45.740 align:start position:0% days so when you think about it during a client<00:04:44.669> as<00:04:44.759> a<00:04:44.789> model<00:04:45.150> like<00:04:45.270> a<00:04:45.360> piece<00:04:45.569> of 00:04:45.740 --> 00:04:45.750 align:start position:0% client as a model like a piece of 00:04:45.750 --> 00:04:47.869 align:start position:0% client as a model like a piece of software<00:04:46.110> making<00:04:46.560> up<00:04:46.680> this<00:04:46.889> as<00:04:47.159> like<00:04:47.580> a<00:04:47.610> web 00:04:47.869 --> 00:04:47.879 align:start position:0% software making up this as like a web 00:04:47.879 --> 00:04:49.999 align:start position:0% software making up this as like a web team<00:04:48.090> application<00:04:48.750> like<00:04:49.349> maybe<00:04:49.590> this<00:04:49.710> is<00:04:49.860> like 00:04:49.999 --> 00:04:50.009 align:start position:0% team application like maybe this is like 00:04:50.009 --> 00:04:53.590 align:start position:0% team application like maybe this is like a<00:04:50.099> Jenga 00:04:53.590 --> 00:04:53.600 align:start position:0% 00:04:53.600 --> 00:04:55.900 align:start position:0% the<00:04:54.200> way<00:04:54.350> to<00:04:54.410> particularly<00:04:54.920> soft<00:04:55.280> wet<00:04:55.580> scale 00:04:55.900 --> 00:04:55.910 align:start position:0% the way to particularly soft wet scale 00:04:55.910 --> 00:04:58.200 align:start position:0% the way to particularly soft wet scale was<00:04:56.330> by<00:04:56.540> looking<00:04:56.930> at<00:04:57.020> this<00:04:57.200> thing<00:04:57.410> it<00:04:57.590> has 00:04:58.200 --> 00:04:58.210 align:start position:0% was by looking at this thing it has 00:04:58.210 --> 00:05:00.460 align:start position:0% was by looking at this thing it has subsistence<00:04:59.210> it<00:04:59.660> sort<00:04:59.930> of<00:04:59.960> a<00:05:00.050> subsistence 00:05:00.460 --> 00:05:00.470 align:start position:0% subsistence it sort of a subsistence 00:05:00.470 --> 00:05:03.430 align:start position:0% subsistence it sort of a subsistence under<00:05:01.130> any<00:05:01.430> other<00:05:01.520> planet<00:05:01.970> there<00:05:02.630> is<00:05:02.780> a<00:05:02.990> period 00:05:03.430 --> 00:05:03.440 align:start position:0% under any other planet there is a period 00:05:03.440 --> 00:05:05.110 align:start position:0% under any other planet there is a period of<00:05:03.530> days<00:05:03.740> which<00:05:03.980> is<00:05:04.130> for<00:05:04.310> Jason<00:05:04.490> I<00:05:04.760> can<00:05:04.970> see 00:05:05.110 --> 00:05:05.120 align:start position:0% of days which is for Jason I can see 00:05:05.120 --> 00:05:07.240 align:start position:0% of days which is for Jason I can see website<00:05:05.930> there's<00:05:06.320> the<00:05:06.560> pubic<00:05:07.130> area 00:05:07.240 --> 00:05:07.250 align:start position:0% website there's the pubic area 00:05:07.250 --> 00:05:08.440 align:start position:0% website there's the pubic area connection<00:05:07.700> to<00:05:07.790> the<00:05:07.880> network 00:05:08.440 --> 00:05:08.450 align:start position:0% connection to the network 00:05:08.450 --> 00:05:10.540 align:start position:0% connection to the network there's<00:05:09.050> the<00:05:09.320> EDM<00:05:09.680> it's<00:05:09.980> actually<00:05:10.280> able<00:05:10.400> to 00:05:10.540 --> 00:05:10.550 align:start position:0% there's the EDM it's actually able to 00:05:10.550 --> 00:05:12.700 align:start position:0% there's the EDM it's actually able to process<00:05:10.790> new<00:05:11.000> blog<00:05:11.450> from<00:05:11.660> transactions<00:05:12.410> and 00:05:12.700 --> 00:05:12.710 align:start position:0% process new blog from transactions and 00:05:12.710 --> 00:05:15.610 align:start position:0% process new blog from transactions and then<00:05:12.940> chain<00:05:13.940> data<00:05:14.210> storage<00:05:14.660> that<00:05:15.260> actually 00:05:15.610 --> 00:05:15.620 align:start position:0% then chain data storage that actually 00:05:15.620 --> 00:05:17.800 align:start position:0% then chain data storage that actually stores<00:05:15.919> that<00:05:16.100> information<00:05:16.280> readily<00:05:16.880> and<00:05:17.270> then 00:05:17.800 --> 00:05:17.810 align:start position:0% stores that information readily and then 00:05:17.810 --> 00:05:19.600 align:start position:0% stores that information readily and then the<00:05:17.900> transaction<00:05:18.350> system<00:05:18.980> that<00:05:19.370> actually 00:05:19.600 --> 00:05:19.610 align:start position:0% the transaction system that actually 00:05:19.610 --> 00:05:21.430 align:start position:0% the transaction system that actually received<00:05:20.480> these<00:05:20.630> transactions<00:05:21.290> and 00:05:21.430 --> 00:05:21.440 align:start position:0% received these transactions and 00:05:21.440 --> 00:05:23.370 align:start position:0% received these transactions and accommodates<00:05:21.950> the<00:05:22.070> net<00:05:22.220> across<00:05:22.430> the<00:05:22.550> network 00:05:23.370 --> 00:05:23.380 align:start position:0% accommodates the net across the network 00:05:23.380 --> 00:05:25.270 align:start position:0% accommodates the net across the network talking<00:05:24.380> about<00:05:24.530> something<00:05:24.830> like<00:05:24.950> the<00:05:25.070> chain 00:05:25.270 --> 00:05:25.280 align:start position:0% talking about something like the chain 00:05:25.280 --> 00:05:27.400 align:start position:0% talking about something like the chain data<00:05:25.490> so<00:05:26.120> if<00:05:26.540> you're<00:05:26.720> running<00:05:27.050> this<00:05:27.140> on<00:05:27.350> a 00:05:27.400 --> 00:05:27.410 align:start position:0% data so if you're running this on a 00:05:27.410 --> 00:05:29.590 align:start position:0% data so if you're running this on a single<00:05:27.560> piece<00:05:27.950> part<00:05:28.310> of<00:05:28.370> it<00:05:28.520> how<00:05:29.000> to<00:05:29.060> scale 00:05:29.590 --> 00:05:29.600 align:start position:0% single piece part of it how to scale 00:05:29.600 --> 00:05:32.950 align:start position:0% single piece part of it how to scale access<00:05:30.050> to<00:05:30.169> Gmail<00:05:30.380> past<00:05:31.160> with<00:05:31.720> specific<00:05:32.720> many 00:05:32.950 --> 00:05:32.960 align:start position:0% access to Gmail past with specific many 00:05:32.960 --> 00:05:34.810 align:start position:0% access to Gmail past with specific many paths<00:05:33.290> forget<00:05:33.950> they're<00:05:34.190> really<00:05:34.430> easy<00:05:34.550> and 00:05:34.810 --> 00:05:34.820 align:start position:0% paths forget they're really easy and 00:05:34.820 --> 00:05:39.640 align:start position:0% paths forget they're really easy and luckily<00:05:35.240> for<00:05:35.560> period<00:05:36.560> and<00:05:36.770> easily<00:05:38.169> by<00:05:39.169> taking 00:05:39.640 --> 00:05:39.650 align:start position:0% luckily for period and easily by taking 00:05:39.650 --> 00:05:42.130 align:start position:0% luckily for period and easily by taking this<00:05:40.550> and<00:05:40.820> thinking<00:05:41.210> about<00:05:41.419> that<00:05:41.570> not<00:05:41.780> as<00:05:41.960> this 00:05:42.130 --> 00:05:42.140 align:start position:0% this and thinking about that not as this 00:05:42.140 --> 00:05:44.670 align:start position:0% this and thinking about that not as this model<00:05:42.380> that<00:05:42.620> increases<00:05:43.070> productivity<00:05:43.760> as 00:05:44.670 --> 00:05:44.680 align:start position:0% model that increases productivity as 00:05:44.680 --> 00:05:47.710 align:start position:0% model that increases productivity as subsystems<00:05:45.820> we<00:05:46.820> started<00:05:47.240> to<00:05:47.360> apply<00:05:47.690> a 00:05:47.710 --> 00:05:47.720 align:start position:0% subsystems we started to apply a 00:05:47.720 --> 00:05:50.260 align:start position:0% subsystems we started to apply a dispositional<00:05:48.530> like<00:05:49.280> West<00:05:49.580> into<00:05:50.150> this 00:05:50.260 --> 00:05:50.270 align:start position:0% dispositional like West into this 00:05:50.270 --> 00:05:52.120 align:start position:0% dispositional like West into this because<00:05:50.600> we're<00:05:50.870> not<00:05:51.169> running<00:05:51.410> this<00:05:51.710> and<00:05:52.010> I'm 00:05:52.120 --> 00:05:52.130 align:start position:0% because we're not running this and I'm 00:05:52.130 --> 00:05:54.610 align:start position:0% because we're not running this and I'm just<00:05:52.160> a<00:05:52.460> single<00:05:52.880> backup<00:05:53.419> do<00:05:53.810> any<00:05:53.990> miss<00:05:54.200> McCloud 00:05:54.610 --> 00:05:54.620 align:start position:0% just a single backup do any miss McCloud 00:05:54.620 --> 00:05:58.719 align:start position:0% just a single backup do any miss McCloud and<00:05:55.250> so<00:05:56.500> you<00:05:57.500> start<00:05:57.800> with<00:05:57.830> right<00:05:58.220> at<00:05:58.340> least<00:05:58.460> in 00:05:58.719 --> 00:05:58.729 align:start position:0% and so you start with right at least in 00:05:58.729 --> 00:06:01.659 align:start position:0% and so you start with right at least in and<00:05:59.180> put<00:05:59.360> this<00:05:59.450> on<00:05:59.630> a<00:05:59.690> survey<00:06:00.110> it's<00:06:00.740> a 00:06:01.659 --> 00:06:01.669 align:start position:0% and put this on a survey it's a 00:06:01.669 --> 00:06:05.110 align:start position:0% and put this on a survey it's a in<00:06:01.969> court<00:06:02.599> as<00:06:02.719> 60<00:06:03.169> gigs<00:06:03.379> of<00:06:03.499> memory<00:06:03.530> and<00:06:04.430> these 00:06:05.110 --> 00:06:05.120 align:start position:0% in court as 60 gigs of memory and these 00:06:05.120 --> 00:06:07.330 align:start position:0% in court as 60 gigs of memory and these are<00:06:05.599> usually<00:06:06.080> pretty<00:06:06.469> proficient<00:06:06.800> minutes 00:06:07.330 --> 00:06:07.340 align:start position:0% are usually pretty proficient minutes 00:06:07.340 --> 00:06:09.309 align:start position:0% are usually pretty proficient minutes you<00:06:07.520> can<00:06:07.669> get<00:06:07.819> to<00:06:08.030> the<00:06:08.120> over<00:06:08.300> 8,000<00:06:08.960> requests 00:06:09.309 --> 00:06:09.319 align:start position:0% you can get to the over 8,000 requests 00:06:09.319 --> 00:06:11.350 align:start position:0% you can get to the over 8,000 requests per<00:06:09.530> second<00:06:09.889> with<00:06:10.009> less<00:06:10.159> red<00:06:10.400> light<00:06:10.550> one 00:06:11.350 --> 00:06:11.360 align:start position:0% per second with less red light one 00:06:11.360 --> 00:06:13.149 align:start position:0% per second with less red light one server<00:06:11.689> if<00:06:11.960> you<00:06:12.110> said<00:06:12.349> 11<00:06:12.740> computer 00:06:13.149 --> 00:06:13.159 align:start position:0% server if you said 11 computer 00:06:13.159 --> 00:06:16.540 align:start position:0% server if you said 11 computer incorrectly<00:06:13.610> and<00:06:14.360> you<00:06:14.689> can<00:06:15.199> get<00:06:15.349> to<00:06:15.529> all<00:06:15.680> when 00:06:16.540 --> 00:06:16.550 align:start position:0% incorrectly and you can get to all when 00:06:16.550 --> 00:06:18.309 align:start position:0% incorrectly and you can get to all when they<00:06:16.639> struggled<00:06:17.060> for<00:06:17.509> certain<00:06:17.930> things<00:06:18.139> they 00:06:18.309 --> 00:06:18.319 align:start position:0% they struggled for certain things they 00:06:18.319 --> 00:06:20.200 align:start position:0% they struggled for certain things they can<00:06:18.469> just<00:06:18.710> send<00:06:18.889> us<00:06:19.009> here<00:06:19.490> at<00:06:19.610> the<00:06:19.729> own<00:06:19.879> memory 00:06:20.200 --> 00:06:20.210 align:start position:0% can just send us here at the own memory 00:06:20.210 --> 00:06:22.749 align:start position:0% can just send us here at the own memory but<00:06:20.810> then<00:06:20.960> beyond<00:06:21.349> that<00:06:21.379> that's<00:06:22.249> where<00:06:22.550> people 00:06:22.749 --> 00:06:22.759 align:start position:0% but then beyond that that's where people 00:06:22.759 --> 00:06:27.010 align:start position:0% but then beyond that that's where people start<00:06:23.150> running<00:06:23.900> into<00:06:24.169> issues<00:06:24.759> and<00:06:25.759> so<00:06:26.060> we<00:06:26.840> have 00:06:27.010 --> 00:06:27.020 align:start position:0% start running into issues and so we have 00:06:27.020 --> 00:06:30.309 align:start position:0% start running into issues and so we have what<00:06:27.469> we<00:06:27.560> call<00:06:27.740> a<00:06:27.800> cloud<00:06:28.159> architecture<00:06:28.999> so<00:06:29.599> we 00:06:30.309 --> 00:06:30.319 align:start position:0% what we call a cloud architecture so we 00:06:30.319 --> 00:06:32.379 align:start position:0% what we call a cloud architecture so we conceptualize<00:06:31.099> this<00:06:31.340> as<00:06:31.639> taking<00:06:32.300> those 00:06:32.379 --> 00:06:32.389 align:start position:0% conceptualize this as taking those 00:06:32.389 --> 00:06:34.659 align:start position:0% conceptualize this as taking those subsystems<00:06:32.900> and<00:06:33.229> being<00:06:34.009> able<00:06:34.099> to<00:06:34.250> optimize 00:06:34.659 --> 00:06:34.669 align:start position:0% subsystems and being able to optimize 00:06:34.669 --> 00:06:37.809 align:start position:0% subsystems and being able to optimize and<00:06:35.120> independent<00:06:35.719> so<00:06:36.590> you<00:06:37.250> never<00:06:37.340> just<00:06:37.639> say 00:06:37.809 --> 00:06:37.819 align:start position:0% and independent so you never just say 00:06:37.819 --> 00:06:39.309 align:start position:0% and independent so you never just say this<00:06:38.000> would<00:06:38.150> normally<00:06:38.539> be<00:06:38.719> on<00:06:38.930> a<00:06:38.990> single 00:06:39.309 --> 00:06:39.319 align:start position:0% this would normally be on a single 00:06:39.319 --> 00:06:41.200 align:start position:0% this would normally be on a single instance<00:06:39.710> you<00:06:40.069> say<00:06:40.279> this<00:06:40.460> is<00:06:40.610> the<00:06:40.639> chain<00:06:40.969> data 00:06:41.200 --> 00:06:41.210 align:start position:0% instance you say this is the chain data 00:06:41.210 --> 00:06:43.809 align:start position:0% instance you say this is the chain data and<00:06:41.599> if<00:06:42.319> I<00:06:42.439> want<00:06:42.680> to<00:06:42.740> be<00:06:42.860> able<00:06:42.949> to<00:06:43.250> query<00:06:43.610> this 00:06:43.809 --> 00:06:43.819 align:start position:0% and if I want to be able to query this 00:06:43.819 --> 00:06:45.399 align:start position:0% and if I want to be able to query this data<00:06:44.029> more<00:06:44.270> efficiently<00:06:44.479> invert<00:06:44.990> ruthlessly 00:06:45.399 --> 00:06:45.409 align:start position:0% data more efficiently invert ruthlessly 00:06:45.409 --> 00:06:47.350 align:start position:0% data more efficiently invert ruthlessly in<00:06:45.620> the<00:06:45.680> morning<00:06:45.949> I<00:06:46.580> can<00:06:46.849> build<00:06:47.029> additional 00:06:47.350 --> 00:06:47.360 align:start position:0% in the morning I can build additional 00:06:47.360 --> 00:06:50.769 align:start position:0% in the morning I can build additional indexes<00:06:48.139> there<00:06:48.500> may<00:06:49.099> be<00:06:49.129> activism<00:06:49.729> self<00:06:50.210> and 00:06:50.769 --> 00:06:50.779 align:start position:0% indexes there may be activism self and 00:06:50.779 --> 00:06:52.959 align:start position:0% indexes there may be activism self and all<00:06:50.930> of<00:06:51.050> the<00:06:51.139> vehicles<00:06:51.919> Postgres<00:06:52.400> migrated 00:06:52.959 --> 00:06:52.969 align:start position:0% all of the vehicles Postgres migrated 00:06:52.969 --> 00:06:55.240 align:start position:0% all of the vehicles Postgres migrated into<00:06:53.120> died<00:06:53.870> when<00:06:54.080> TB<00:06:54.439> or<00:06:54.650> something<00:06:55.039> like<00:06:55.189> that 00:06:55.240 --> 00:06:55.250 align:start position:0% into died when TB or something like that 00:06:55.250 --> 00:06:59.470 align:start position:0% into died when TB or something like that that<00:06:55.699> has<00:06:55.969> like<00:06:56.330> well<00:06:56.569> scale 00:06:59.470 --> 00:06:59.480 align:start position:0% 00:06:59.480 --> 00:07:03.190 align:start position:0% the<00:06:59.840> table<00:07:00.200> is<00:07:00.260> unique<00:07:01.240> and<00:07:02.240> inventive<00:07:02.780> as 00:07:03.190 --> 00:07:03.200 align:start position:0% the table is unique and inventive as 00:07:03.200 --> 00:07:06.810 align:start position:0% the table is unique and inventive as with<00:07:03.410> any<00:07:03.620> other<00:07:03.740> set<00:07:04.580> system<00:07:05.020> turn<00:07:06.020> it<00:07:06.140> into<00:07:06.290> a 00:07:06.810 --> 00:07:06.820 align:start position:0% with any other set system turn it into a 00:07:06.820 --> 00:07:09.820 align:start position:0% with any other set system turn it into a specialized<00:07:07.820> nitrous<00:07:08.270> service<00:07:08.830> or 00:07:09.820 --> 00:07:09.830 align:start position:0% specialized nitrous service or 00:07:09.830 --> 00:07:15.010 align:start position:0% specialized nitrous service or application<00:07:12.940> all<00:07:13.940> these<00:07:14.210> things<00:07:14.480> start<00:07:14.840> with 00:07:15.010 --> 00:07:15.020 align:start position:0% application all these things start with 00:07:15.020 --> 00:07:17.140 align:start position:0% application all these things start with having<00:07:15.320> that<00:07:15.470> reliable<00:07:16.010> note<00:07:16.190> connection<00:07:16.760> and 00:07:17.140 --> 00:07:17.150 align:start position:0% having that reliable note connection and 00:07:17.150 --> 00:07:19.990 align:start position:0% having that reliable note connection and that's<00:07:17.990> how<00:07:18.770> you<00:07:18.950> can<00:07:19.160> quickly<00:07:19.310> provision<00:07:19.910> in 00:07:19.990 --> 00:07:20.000 align:start position:0% that's how you can quickly provision in 00:07:20.000 --> 00:07:22.500 align:start position:0% that's how you can quickly provision in it<00:07:20.230> trust<00:07:21.230> me 00:07:22.500 --> 00:07:22.510 align:start position:0% it trust me 00:07:22.510 --> 00:07:27.150 align:start position:0% it trust me is<00:07:23.040> much<00:07:24.040> slower<00:07:24.370> than<00:07:25.290> Eastley<00:07:26.290> our<00:07:26.410> 2016<00:07:27.040> you 00:07:27.150 --> 00:07:27.160 align:start position:0% is much slower than Eastley our 2016 you 00:07:27.160 --> 00:07:29.490 align:start position:0% is much slower than Eastley our 2016 you that<00:07:27.340> need<00:07:27.520> extra<00:07:27.730> oil<00:07:28.390> we<00:07:28.810> didn't<00:07:29.050> work<00:07:29.200> sync 00:07:29.490 --> 00:07:29.500 align:start position:0% that need extra oil we didn't work sync 00:07:29.500 --> 00:07:33.980 align:start position:0% that need extra oil we didn't work sync apparently<00:07:30.310> no<00:07:30.460> minutes<00:07:31.090> and<00:07:31.330> yeah 00:07:33.980 --> 00:07:33.990 align:start position:0% apparently no minutes and yeah 00:07:33.990 --> 00:07:37.279 align:start position:0% apparently no minutes and yeah but<00:07:34.770> over<00:07:35.069> time<00:07:35.099> that's<00:07:35.639> been<00:07:35.729> at<00:07:36.419> in<00:07:36.810> terms<00:07:36.960> of 00:07:37.279 --> 00:07:37.289 align:start position:0% but over time that's been at in terms of 00:07:37.289 --> 00:07:39.649 align:start position:0% but over time that's been at in terms of donation<00:07:37.770> as<00:07:37.949> Kingdom<00:07:38.759> change<00:07:39.240> the<00:07:39.479> others 00:07:39.649 --> 00:07:39.659 align:start position:0% donation as Kingdom change the others 00:07:39.659 --> 00:07:42.710 align:start position:0% donation as Kingdom change the others grow<00:07:39.990> and<00:07:40.970> so<00:07:41.970> the<00:07:42.090> first<00:07:42.330> thing<00:07:42.479> that<00:07:42.599> we 00:07:42.710 --> 00:07:42.720 align:start position:0% grow and so the first thing that we 00:07:42.720 --> 00:07:45.469 align:start position:0% grow and so the first thing that we tried<00:07:42.990> was<00:07:43.199> doing<00:07:43.530> simple<00:07:44.129> you<00:07:44.460> just<00:07:44.490> a 00:07:45.469 --> 00:07:45.479 align:start position:0% tried was doing simple you just a 00:07:45.479 --> 00:07:48.140 align:start position:0% tried was doing simple you just a familiar<00:07:46.020> with<00:07:46.460> Amazon<00:07:47.460> Web<00:07:47.490> Services 00:07:48.140 --> 00:07:48.150 align:start position:0% familiar with Amazon Web Services 00:07:48.150 --> 00:07:50.839 align:start position:0% familiar with Amazon Web Services there's<00:07:48.990> this<00:07:49.110> concept<00:07:49.620> of<00:07:49.860> elastic<00:07:50.430> block 00:07:50.839 --> 00:07:50.849 align:start position:0% there's this concept of elastic block 00:07:50.849 --> 00:07:54.800 align:start position:0% there's this concept of elastic block search<00:07:51.180> which<00:07:51.720> is<00:07:52.310> the<00:07:53.310> ability<00:07:53.460> to<00:07:53.810> snapshot 00:07:54.800 --> 00:07:54.810 align:start position:0% search which is the ability to snapshot 00:07:54.810 --> 00:07:57.920 align:start position:0% search which is the ability to snapshot periodic<00:07:55.560> backups<00:07:55.710> and<00:07:56.610> quickly<00:07:57.120> spin<00:07:57.539> up<00:07:57.720> the 00:07:57.920 --> 00:07:57.930 align:start position:0% periodic backups and quickly spin up the 00:07:57.930 --> 00:08:00.559 align:start position:0% periodic backups and quickly spin up the disk<00:07:58.590> types<00:07:58.860> that<00:07:59.039> can<00:07:59.190> be<00:07:59.370> associated<00:08:00.210> with 00:08:00.559 --> 00:08:00.569 align:start position:0% disk types that can be associated with 00:08:00.569 --> 00:08:02.089 align:start position:0% disk types that can be associated with any<00:08:00.840> service 00:08:02.089 --> 00:08:02.099 align:start position:0% any service 00:08:02.099 --> 00:08:04.760 align:start position:0% any service so<00:08:02.460> it<00:08:02.580> said<00:08:02.819> take<00:08:03.240> and<00:08:03.569> say<00:08:03.720> well<00:08:04.229> that<00:08:04.259> was<00:08:04.620> to 00:08:04.760 --> 00:08:04.770 align:start position:0% so it said take and say well that was to 00:08:04.770 --> 00:08:06.770 align:start position:0% so it said take and say well that was to say<00:08:04.949> yeah<00:08:05.250> this<00:08:05.759> is<00:08:05.879> going<00:08:06.000> to<00:08:06.150> be<00:08:06.330> an<00:08:06.599> online 00:08:06.770 --> 00:08:06.780 align:start position:0% say yeah this is going to be an online 00:08:06.780 --> 00:08:11.149 align:start position:0% say yeah this is going to be an online and<00:08:07.379> like<00:08:07.919> and<00:08:08.729> so<00:08:09.650> additionally<00:08:10.650> these<00:08:10.830> three 00:08:11.149 --> 00:08:11.159 align:start position:0% and like and so additionally these three 00:08:11.159 --> 00:08:13.850 align:start position:0% and like and so additionally these three got<00:08:11.340> snapshots<00:08:12.060> idea<00:08:12.780> Westphalia<00:08:13.319> repairing 00:08:13.850 --> 00:08:13.860 align:start position:0% got snapshots idea Westphalia repairing 00:08:13.860 --> 00:08:17.360 align:start position:0% got snapshots idea Westphalia repairing there<00:08:14.250> were<00:08:14.370> huge<00:08:14.969> certain<00:08:15.710> upgrades<00:08:16.710> that 00:08:17.360 --> 00:08:17.370 align:start position:0% there were huge certain upgrades that 00:08:17.370 --> 00:08:21.110 align:start position:0% there were huge certain upgrades that they<00:08:18.120> actually<00:08:18.719> did<00:08:19.169> and<00:08:19.560> we<00:08:20.370> had<00:08:20.639> to<00:08:20.759> find<00:08:21.060> a 00:08:21.110 --> 00:08:21.120 align:start position:0% they actually did and we had to find a 00:08:21.120 --> 00:08:22.969 align:start position:0% they actually did and we had to find a way<00:08:21.150> to<00:08:21.300> quickly<00:08:21.569> recover<00:08:21.930> otherwise<00:08:22.680> our 00:08:22.969 --> 00:08:22.979 align:start position:0% way to quickly recover otherwise our 00:08:22.979 --> 00:08:26.869 align:start position:0% way to quickly recover otherwise our service<00:08:23.280> were<00:08:23.430> there<00:08:23.669> yeah<00:08:24.569> so<00:08:25.469> that<00:08:26.310> was<00:08:26.430> one 00:08:26.869 --> 00:08:26.879 align:start position:0% service were there yeah so that was one 00:08:26.879 --> 00:08:29.689 align:start position:0% service were there yeah so that was one of<00:08:26.909> the<00:08:27.060> things<00:08:27.270> we<00:08:27.449> started<00:08:27.509> with<00:08:28.699> lady 00:08:29.689 --> 00:08:29.699 align:start position:0% of the things we started with lady 00:08:29.699 --> 00:08:31.760 align:start position:0% of the things we started with lady there's<00:08:30.060> the<00:08:30.180> logic<00:08:30.629> depends<00:08:31.050> to<00:08:31.229> some<00:08:31.259> times 00:08:31.760 --> 00:08:31.770 align:start position:0% there's the logic depends to some times 00:08:31.770 --> 00:08:36.230 align:start position:0% there's the logic depends to some times where<00:08:32.219> it's<00:08:32.700> gone<00:08:33.269> from<00:08:34.339> hours<00:08:35.339> with<00:08:35.789> left<00:08:36.060> one 00:08:36.230 --> 00:08:36.240 align:start position:0% where it's gone from hours with left one 00:08:36.240 --> 00:08:40.889 align:start position:0% where it's gone from hours with left one night<00:08:36.560> to<00:08:37.560> four<00:08:38.010> hours 00:08:40.889 --> 00:08:40.899 align:start position:0% 00:08:40.899 --> 00:08:43.630 align:start position:0% this<00:08:41.899> is<00:08:42.020> test<00:08:42.289> data<00:08:42.560> from<00:08:42.860> the<00:08:42.979> gap<00:08:43.159> to<00:08:43.399> their 00:08:43.630 --> 00:08:43.640 align:start position:0% this is test data from the gap to their 00:08:43.640 --> 00:08:44.410 align:start position:0% this is test data from the gap to their great<00:08:44.029> work 00:08:44.410 --> 00:08:44.420 align:start position:0% great work 00:08:44.420 --> 00:08:47.320 align:start position:0% great work and<00:08:45.020> I'm<00:08:45.950> were<00:08:46.160> able<00:08:46.430> to<00:08:46.459> get<00:08:46.700> these<00:08:46.940> kinds<00:08:47.270> of 00:08:47.320 --> 00:08:47.330 align:start position:0% and I'm were able to get these kinds of 00:08:47.330 --> 00:08:51.000 align:start position:0% and I'm were able to get these kinds of improvements<00:08:47.690> at<00:08:48.470> me<00:08:48.649> by<00:08:49.209> optimizing<00:08:50.209> our 00:08:51.000 --> 00:08:51.010 align:start position:0% improvements at me by optimizing our 00:08:51.010 --> 00:08:54.910 align:start position:0% improvements at me by optimizing our utilization<00:08:53.290> idealization<00:08:54.290> is<00:08:54.680> really 00:08:54.910 --> 00:08:54.920 align:start position:0% utilization idealization is really 00:08:54.920 --> 00:08:57.579 align:start position:0% utilization idealization is really important<00:08:55.370> because<00:08:56.110> when<00:08:57.110> we<00:08:57.170> read<00:08:57.410> these 00:08:57.579 --> 00:08:57.589 align:start position:0% important because when we read these 00:08:57.589 --> 00:08:59.650 align:start position:0% important because when we read these things<00:08:57.860> there<00:08:58.190> is<00:08:58.370> a<00:08:58.580> huge<00:08:58.820> amount<00:08:58.910> of<00:08:59.120> IELTS 00:08:59.650 --> 00:08:59.660 align:start position:0% things there is a huge amount of IELTS 00:08:59.660 --> 00:09:02.290 align:start position:0% things there is a huge amount of IELTS because<00:08:59.810> watching<00:09:00.440> data<00:09:00.950> in<00:09:01.670> terms<00:09:01.910> of<00:09:02.149> being 00:09:02.290 --> 00:09:02.300 align:start position:0% because watching data in terms of being 00:09:02.300 --> 00:09:04.060 align:start position:0% because watching data in terms of being stored<00:09:02.690> in<00:09:02.750> too<00:09:02.990> many<00:09:03.140> stores<00:09:03.620> in<00:09:03.830> the<00:09:03.920> way 00:09:04.060 --> 00:09:04.070 align:start position:0% stored in too many stores in the way 00:09:04.070 --> 00:09:06.660 align:start position:0% stored in too many stores in the way that<00:09:04.220> data<00:09:04.490> is<00:09:04.730> verified<00:09:04.970> is<00:09:05.660> very<00:09:05.959> even<00:09:06.410> right 00:09:06.660 --> 00:09:06.670 align:start position:0% that data is verified is very even right 00:09:06.670 --> 00:09:09.310 align:start position:0% that data is verified is very even right so<00:09:07.670> we<00:09:07.910> are<00:09:07.940> to<00:09:08.209> use<00:09:08.360> this<00:09:08.570> type<00:09:08.870> like<00:09:09.080> your 00:09:09.310 --> 00:09:09.320 align:start position:0% so we are to use this type like your 00:09:09.320 --> 00:09:11.889 align:start position:0% so we are to use this type like your life<00:09:09.589> through<00:09:09.830> Forex<00:09:10.250> version<00:09:10.399> which<00:09:11.060> is<00:09:11.270> it 00:09:11.889 --> 00:09:11.899 align:start position:0% life through Forex version which is it 00:09:11.899 --> 00:09:15.579 align:start position:0% life through Forex version which is it just<00:09:12.470> another<00:09:13.000> 25,000<00:09:14.000> random<00:09:14.899> read<00:09:15.080> lots 00:09:15.579 --> 00:09:15.589 align:start position:0% just another 25,000 random read lots 00:09:15.589 --> 00:09:18.970 align:start position:0% just another 25,000 random read lots available<00:09:16.750> if<00:09:17.750> we<00:09:17.990> weren't<00:09:18.260> isn't<00:09:18.589> as<00:09:18.709> we 00:09:18.970 --> 00:09:18.980 align:start position:0% available if we weren't isn't as we 00:09:18.980 --> 00:09:21.550 align:start position:0% available if we weren't isn't as we reclaim<00:09:19.370> oh<00:09:19.610> yes<00:09:19.910> we're<00:09:20.690> going<00:09:20.870> to<00:09:20.990> be<00:09:21.170> limited 00:09:21.550 --> 00:09:21.560 align:start position:0% reclaim oh yes we're going to be limited 00:09:21.560 --> 00:09:23.860 align:start position:0% reclaim oh yes we're going to be limited to<00:09:21.800> a<00:09:22.250> fraction<00:09:22.640> about<00:09:22.880> that<00:09:23.060> one<00:09:23.270> time<00:09:23.480> that 00:09:23.860 --> 00:09:23.870 align:start position:0% to a fraction about that one time that 00:09:23.870 --> 00:09:28.720 align:start position:0% to a fraction about that one time that is<00:09:24.470> really<00:09:24.950> that<00:09:26.350> this<00:09:27.350> only<00:09:27.770> gets<00:09:28.070> you<00:09:28.339> to 00:09:28.720 --> 00:09:28.730 align:start position:0% is really that this only gets you to 00:09:28.730 --> 00:09:30.970 align:start position:0% is really that this only gets you to that<00:09:28.910> for<00:09:29.240> our<00:09:29.450> part<00:09:29.810> and<00:09:30.200> that's<00:09:30.440> not<00:09:30.649> fast 00:09:30.970 --> 00:09:30.980 align:start position:0% that for our part and that's not fast 00:09:30.980 --> 00:09:33.680 align:start position:0% that for our part and that's not fast enough 00:09:33.680 --> 00:09:33.690 align:start position:0% 00:09:33.690 --> 00:09:36.560 align:start position:0% and<00:09:34.320> so<00:09:35.280> we<00:09:35.520> ended<00:09:35.820> up<00:09:35.880> combining<00:09:36.150> this 00:09:36.560 --> 00:09:36.570 align:start position:0% and so we ended up combining this 00:09:36.570 --> 00:09:38.800 align:start position:0% and so we ended up combining this approach<00:09:36.960> combined<00:09:37.680> with<00:09:37.890> periodic<00:09:38.280> backups 00:09:38.800 --> 00:09:38.810 align:start position:0% approach combined with periodic backups 00:09:38.810 --> 00:09:42.320 align:start position:0% approach combined with periodic backups being<00:09:39.810> able<00:09:39.960> to<00:09:40.110> sync<00:09:40.500> that<00:09:41.030> directly<00:09:42.030> to<00:09:42.270> you 00:09:42.320 --> 00:09:42.330 align:start position:0% being able to sync that directly to you 00:09:42.330 --> 00:09:46.130 align:start position:0% being able to sync that directly to you I<00:09:42.390> mean<00:09:42.540> that<00:09:42.600> when<00:09:43.050> we<00:09:43.290> spin<00:09:43.530> it<00:09:43.590> up<00:09:44.990> thanks<00:09:45.990> to 00:09:46.130 --> 00:09:46.140 align:start position:0% I mean that when we spin it up thanks to 00:09:46.140 --> 00:09:47.690 align:start position:0% I mean that when we spin it up thanks to my<00:09:46.320> cryptid<00:09:46.710> team<00:09:46.890> appreciate<00:09:47.400> their 00:09:47.690 --> 00:09:47.700 align:start position:0% my cryptid team appreciate their 00:09:47.700 --> 00:09:49.100 align:start position:0% my cryptid team appreciate their implementation<00:09:48.390> of<00:09:48.510> this<00:09:48.660> they<00:09:48.930> were<00:09:48.990> the 00:09:49.100 --> 00:09:49.110 align:start position:0% implementation of this they were the 00:09:49.110 --> 00:09:50.330 align:start position:0% implementation of this they were the first<00:09:49.320> ones<00:09:49.530> really<00:09:49.770> try<00:09:49.980> to<00:09:50.010> self 00:09:50.330 --> 00:09:50.340 align:start position:0% first ones really try to self 00:09:50.340 --> 00:09:51.650 align:start position:0% first ones really try to self introduction<00:09:51.060> and<00:09:51.240> they<00:09:51.390> share<00:09:51.630> their 00:09:51.650 --> 00:09:51.660 align:start position:0% introduction and they share their 00:09:51.660 --> 00:09:53.750 align:start position:0% introduction and they share their activation<00:09:52.470> carefully<00:09:53.100> and<00:09:53.250> once<00:09:53.370> I<00:09:53.550> shove<00:09:53.730> it 00:09:53.750 --> 00:09:53.760 align:start position:0% activation carefully and once I shove it 00:09:53.760 --> 00:09:58.310 align:start position:0% activation carefully and once I shove it out<00:09:54.110> but<00:09:55.110> this<00:09:55.410> know<00:09:56.570> where<00:09:57.570> this<00:09:57.870> source<00:09:58.170> of 00:09:58.310 --> 00:09:58.320 align:start position:0% out but this know where this source of 00:09:58.320 --> 00:10:00.740 align:start position:0% out but this know where this source of truth<00:09:58.530> live<00:09:58.830> is<00:09:59.190> what<00:09:59.400> you<00:09:59.520> call<00:09:59.730> it<00:09:59.880> stinks 00:10:00.740 --> 00:10:00.750 align:start position:0% truth live is what you call it stinks 00:10:00.750 --> 00:10:02.450 align:start position:0% truth live is what you call it stinks from<00:10:00.930> scratch<00:10:01.230> I<00:10:01.560> think<00:10:01.920> it's<00:10:02.010> a<00:10:02.070> pretty 00:10:02.450 --> 00:10:02.460 align:start position:0% from scratch I think it's a pretty 00:10:02.460 --> 00:10:04.310 align:start position:0% from scratch I think it's a pretty ratchet<00:10:02.730> power<00:10:03.120> all<00:10:03.360> it<00:10:03.510> takes<00:10:03.750> is<00:10:03.870> very<00:10:04.050> fast 00:10:04.310 --> 00:10:04.320 align:start position:0% ratchet power all it takes is very fast 00:10:04.320 --> 00:10:07.340 align:start position:0% ratchet power all it takes is very fast in<00:10:04.650> the<00:10:05.010> archive<00:10:05.370> medicine<00:10:05.940> then<00:10:06.840> we<00:10:07.140> have 00:10:07.340 --> 00:10:07.350 align:start position:0% in the archive medicine then we have 00:10:07.350 --> 00:10:09.470 align:start position:0% in the archive medicine then we have away<00:10:07.890> the<00:10:08.100> function<00:10:08.460> the<00:10:08.580> fires<00:10:08.850> off<00:10:09.150> every 00:10:09.470 --> 00:10:09.480 align:start position:0% away the function the fires off every 00:10:09.480 --> 00:10:11.420 align:start position:0% away the function the fires off every hour<00:10:09.510> to<00:10:09.990> back<00:10:10.230> up<00:10:10.470> that<00:10:10.680> data<00:10:10.920> to<00:10:11.100> an<00:10:11.280> s3 00:10:11.420 --> 00:10:11.430 align:start position:0% hour to back up that data to an s3 00:10:11.430 --> 00:10:13.880 align:start position:0% hour to back up that data to an s3 bucket<00:10:11.700> we<00:10:12.480> can<00:10:12.900> generalize<00:10:13.320> this<00:10:13.590> to<00:10:13.650> any 00:10:13.880 --> 00:10:13.890 align:start position:0% bucket we can generalize this to any 00:10:13.890 --> 00:10:16.130 align:start position:0% bucket we can generalize this to any cloud<00:10:14.190> that<00:10:14.430> office<00:10:14.730> is<00:10:14.880> somewhere<00:10:15.180> to<00:10:15.330> go<00:10:15.480> and 00:10:16.130 --> 00:10:16.140 align:start position:0% cloud that office is somewhere to go and 00:10:16.140 --> 00:10:19.070 align:start position:0% cloud that office is somewhere to go and then<00:10:16.290> lastly<00:10:16.740> they<00:10:17.070> just<00:10:17.490> pass<00:10:18.300> it<00:10:18.510> up<00:10:18.780> written 00:10:19.070 --> 00:10:19.080 align:start position:0% then lastly they just pass it up written 00:10:19.080 --> 00:10:23.030 align:start position:0% then lastly they just pass it up written it<00:10:20.000> we<00:10:21.000> have<00:10:21.720> a<00:10:21.900> high<00:10:22.140> throughput<00:10:22.440> pipeline 00:10:23.030 --> 00:10:23.040 align:start position:0% it we have a high throughput pipeline 00:10:23.040 --> 00:10:26.210 align:start position:0% it we have a high throughput pipeline between<00:10:23.400> s3<00:10:24.120> ready<00:10:24.390> CT<00:10:24.840> and<00:10:25.140> it's<00:10:25.830> bullying 00:10:26.210 --> 00:10:26.220 align:start position:0% between s3 ready CT and it's bullying 00:10:26.220 --> 00:10:28.040 align:start position:0% between s3 ready CT and it's bullying with<00:10:26.400> the<00:10:26.490> saturate<00:10:26.940> about<00:10:27.150> my<00:10:27.360> office 00:10:28.040 --> 00:10:28.050 align:start position:0% with the saturate about my office 00:10:28.050 --> 00:10:29.660 align:start position:0% with the saturate about my office that's<00:10:28.680> a 00:10:29.660 --> 00:10:29.670 align:start position:0% that's a 00:10:29.670 --> 00:10:34.010 align:start position:0% that's a and<00:10:29.940> yet<00:10:30.180> this<00:10:30.330> day<00:10:30.570> about<00:10:32.060> 50<00:10:33.060> minutes<00:10:33.360> from 00:10:34.010 --> 00:10:34.020 align:start position:0% and yet this day about 50 minutes from 00:10:34.020 --> 00:10:35.480 align:start position:0% and yet this day about 50 minutes from the<00:10:34.350> time<00:10:34.380> that<00:10:34.560> he<00:10:34.710> started<00:10:34.770> to<00:10:35.220> return 00:10:35.480 --> 00:10:35.490 align:start position:0% the time that he started to return 00:10:35.490 --> 00:10:37.240 align:start position:0% the time that he started to return that's<00:10:35.730> ready 00:10:37.240 --> 00:10:37.250 align:start position:0% that's ready 00:10:37.250 --> 00:10:40.220 align:start position:0% that's ready so<00:10:38.250> once<00:10:38.430> you<00:10:38.490> have<00:10:38.610> this<00:10:38.760> reliable<00:10:39.270> then<00:10:39.540> IV 00:10:40.220 --> 00:10:40.230 align:start position:0% so once you have this reliable then IV 00:10:40.230 --> 00:10:42.290 align:start position:0% so once you have this reliable then IV start<00:10:40.650> building<00:10:41.160> additional<00:10:41.580> services<00:10:42.060> on 00:10:42.290 --> 00:10:42.300 align:start position:0% start building additional services on 00:10:42.300 --> 00:10:44.570 align:start position:0% start building additional services on top<00:10:42.510> of<00:10:42.690> its<00:10:42.840> optimizer<00:10:43.350> traffic<00:10:43.950> and<00:10:44.400> that 00:10:44.570 --> 00:10:44.580 align:start position:0% top of its optimizer traffic and that 00:10:44.580 --> 00:10:47.990 align:start position:0% top of its optimizer traffic and that really<00:10:44.910> needs<00:10:45.210> to<00:10:46.250> traffic<00:10:47.250> parents<00:10:47.640> like<00:10:47.790> you 00:10:47.990 --> 00:10:48.000 align:start position:0% really needs to traffic parents like you 00:10:48.000 --> 00:10:49.550 align:start position:0% really needs to traffic parents like you and<00:10:48.180> their<00:10:48.300> application<00:10:48.990> in<00:10:49.080> your<00:10:49.110> business 00:10:49.550 --> 00:10:49.560 align:start position:0% and their application in your business 00:10:49.560 --> 00:11:04.550 align:start position:0% and their application in your business said<00:10:50.460> she's<00:10:50.670> gonna<00:11:02.840> memorize<00:11:03.840> our<00:11:04.140> traffic 00:11:04.550 --> 00:11:04.560 align:start position:0% said she's gonna memorize our traffic 00:11:04.560 --> 00:11:07.240 align:start position:0% said she's gonna memorize our traffic into<00:11:05.250> three<00:11:05.580> different<00:11:05.910> types<00:11:06.120> near<00:11:06.660> head 00:11:07.240 --> 00:11:07.250 align:start position:0% into three different types near head 00:11:07.250 --> 00:11:10.880 align:start position:0% into three different types near head archiving<00:11:08.250> pull<00:11:08.490> your<00:11:09.360> head<00:11:09.600> is<00:11:09.990> any<00:11:10.470> request 00:11:10.880 --> 00:11:10.890 align:start position:0% archiving pull your head is any request 00:11:10.890 --> 00:11:12.500 align:start position:0% archiving pull your head is any request that's<00:11:11.220> within<00:11:11.520> a<00:11:11.760> couple<00:11:11.940> hundred<00:11:12.060> blocks 00:11:12.500 --> 00:11:12.510 align:start position:0% that's within a couple hundred blocks 00:11:12.510 --> 00:11:16.130 align:start position:0% that's within a couple hundred blocks behind<00:11:12.810> pet<00:11:13.260> the<00:11:14.100> archive<00:11:14.670> is<00:11:15.450> requests<00:11:15.900> that 00:11:16.130 --> 00:11:16.140 align:start position:0% behind pet the archive is requests that 00:11:16.140 --> 00:11:19.640 align:start position:0% behind pet the archive is requests that require<00:11:16.470> dia<00:11:17.100> and<00:11:17.490> then<00:11:17.670> full<00:11:17.910> is<00:11:18.240> requested 00:11:19.640 --> 00:11:19.650 align:start position:0% require dia and then full is requested 00:11:19.650 --> 00:11:23.270 align:start position:0% require dia and then full is requested do<00:11:20.370> not<00:11:20.550> require<00:11:20.820> proof<00:11:21.090> data<00:11:21.740> as<00:11:22.740> you<00:11:22.800> can<00:11:23.070> see 00:11:23.270 --> 00:11:23.280 align:start position:0% do not require proof data as you can see 00:11:23.280 --> 00:11:25.400 align:start position:0% do not require proof data as you can see the<00:11:23.610> majority<00:11:23.910> of<00:11:24.210> traffic<00:11:24.450> that<00:11:24.720> we<00:11:24.870> get<00:11:25.050> is 00:11:25.400 --> 00:11:25.410 align:start position:0% the majority of traffic that we get is 00:11:25.410 --> 00:11:28.330 align:start position:0% the majority of traffic that we get is your<00:11:25.860> head<00:11:26.270> it's<00:11:27.270> fairly<00:11:27.510> consistent 00:11:28.330 --> 00:11:28.340 align:start position:0% your head it's fairly consistent 00:11:28.340 --> 00:11:30.890 align:start position:0% your head it's fairly consistent Verna's<00:11:29.340> archive<00:11:30.150> data<00:11:30.390> could<00:11:30.660> fluctuate 00:11:30.890 --> 00:11:30.900 align:start position:0% Verna's archive data could fluctuate 00:11:30.900 --> 00:11:33.860 align:start position:0% Verna's archive data could fluctuate anywhere<00:11:31.680> between<00:11:31.920> six<00:11:32.610> to<00:11:32.790> even<00:11:33.210> less<00:11:33.540> than 00:11:33.860 --> 00:11:33.870 align:start position:0% anywhere between six to even less than 00:11:33.870 --> 00:11:36.530 align:start position:0% anywhere between six to even less than one<00:11:34.380> percent<00:11:34.880> depending<00:11:35.880> on<00:11:36.000> what<00:11:36.150> our<00:11:36.240> users 00:11:36.530 --> 00:11:36.540 align:start position:0% one percent depending on what our users 00:11:36.540 --> 00:11:38.000 align:start position:0% one percent depending on what our users were<00:11:36.660> doing<00:11:36.960> at<00:11:37.140> that<00:11:37.170> given<00:11:37.440> point<00:11:37.590> on<00:11:37.950> the 00:11:38.000 --> 00:11:38.010 align:start position:0% were doing at that given point on the 00:11:38.010 --> 00:11:41.210 align:start position:0% were doing at that given point on the time<00:11:38.780> so<00:11:39.780> the<00:11:39.870> first<00:11:39.990> thing<00:11:40.200> we<00:11:40.320> did<00:11:40.500> was<00:11:40.770> we 00:11:41.210 --> 00:11:41.220 align:start position:0% time so the first thing we did was we 00:11:41.220 --> 00:11:43.940 align:start position:0% time so the first thing we did was we asked<00:11:41.700> our<00:11:41.820> near<00:11:42.030> that<00:11:42.180> DHT<00:11:43.080> and<00:11:43.320> it<00:11:43.770> worked 00:11:43.940 --> 00:11:43.950 align:start position:0% asked our near that DHT and it worked 00:11:43.950 --> 00:11:44.420 align:start position:0% asked our near that DHT and it worked really<00:11:44.160> well 00:11:44.420 --> 00:11:44.430 align:start position:0% really well 00:11:44.430 --> 00:11:46.690 align:start position:0% really well it<00:11:45.360> just<00:11:45.540> came<00:11:45.690> with<00:11:45.930> certain<00:11:46.380> limitations 00:11:46.690 --> 00:11:46.700 align:start position:0% it just came with certain limitations 00:11:46.700 --> 00:11:49.580 align:start position:0% it just came with certain limitations time<00:11:47.700> for<00:11:47.940> exactly<00:11:48.360> we<00:11:48.450> could<00:11:48.600> only<00:11:48.780> get 00:11:49.580 --> 00:11:49.590 align:start position:0% time for exactly we could only get 00:11:49.590 --> 00:11:50.300 align:start position:0% time for exactly we could only get blocked<00:11:49.800> my<00:11:49.950> number 00:11:50.300 --> 00:11:50.310 align:start position:0% blocked my number 00:11:50.310 --> 00:11:52.640 align:start position:0% blocked my number yeah<00:11:50.730> block<00:11:51.030> number<00:11:51.060> it<00:11:52.050> also<00:11:52.200> was<00:11:52.440> a<00:11:52.470> good 00:11:52.640 --> 00:11:52.650 align:start position:0% yeah block number it also was a good 00:11:52.650 --> 00:11:56.030 align:start position:0% yeah block number it also was a good scalable<00:11:53.280> so<00:11:53.550> we<00:11:53.880> made<00:11:54.030> a<00:11:54.120> decision<00:11:54.390> to<00:11:55.040> store 00:11:56.030 --> 00:11:56.040 align:start position:0% scalable so we made a decision to store 00:11:56.040 --> 00:12:00.879 align:start position:0% scalable so we made a decision to store or<00:11:56.340> in<00:11:56.430> your<00:11:56.610> head<00:11:57.230> read<00:11:58.230> a<00:11:58.290> few<00:11:58.560> e<00:11:58.620> and<00:11:59.420> it<00:12:00.420> was 00:12:00.879 --> 00:12:00.889 align:start position:0% or in your head read a few e and it was 00:12:00.889 --> 00:12:02.879 align:start position:0% or in your head read a few e and it was are<00:12:01.009> scalable<00:12:01.339> and<00:12:01.670> also<00:12:01.999> allowed<00:12:02.269> us<00:12:02.299> to 00:12:02.879 --> 00:12:02.889 align:start position:0% are scalable and also allowed us to 00:12:02.889 --> 00:12:08.439 align:start position:0% are scalable and also allowed us to store<00:12:03.889> all<00:12:04.100> of<00:12:04.129> our<00:12:04.399> new<00:12:04.579> pet<00:12:04.819> data<00:12:07.449> in 00:12:08.439 --> 00:12:08.449 align:start position:0% store all of our new pet data in 00:12:08.449 --> 00:12:11.079 align:start position:0% store all of our new pet data in addition<00:12:08.569> to<00:12:09.230> our<00:12:09.649> narrative<00:12:10.189> hatch<00:12:10.429> we<00:12:10.879> have 00:12:11.079 --> 00:12:11.089 align:start position:0% addition to our narrative hatch we have 00:12:11.089 --> 00:12:13.509 align:start position:0% addition to our narrative hatch we have a<00:12:11.389> set<00:12:11.869> and<00:12:12.139> a<00:12:12.170> special<00:12:12.529> library<00:12:12.619> services 00:12:13.509 --> 00:12:13.519 align:start position:0% a set and a special library services 00:12:13.519 --> 00:12:17.349 align:start position:0% a set and a special library services that<00:12:13.850> I<00:12:14.179> heard<00:12:14.449> index<00:12:14.989> or<00:12:15.399> cash<00:12:16.399> like<00:12:16.819> specific 00:12:17.349 --> 00:12:17.359 align:start position:0% that I heard index or cash like specific 00:12:17.359 --> 00:12:19.449 align:start position:0% that I heard index or cash like specific types<00:12:17.660> of<00:12:17.839> data<00:12:18.019> but<00:12:18.889> what<00:12:18.980> I'm<00:12:19.100> going<00:12:19.220> to<00:12:19.279> talk 00:12:19.449 --> 00:12:19.459 align:start position:0% types of data but what I'm going to talk 00:12:19.459 --> 00:12:21.669 align:start position:0% types of data but what I'm going to talk about<00:12:19.519> today<00:12:20.059> is<00:12:20.419> our<00:12:20.569> log<00:12:20.839> indexer<00:12:21.439> which 00:12:21.669 --> 00:12:21.679 align:start position:0% about today is our log indexer which 00:12:21.679 --> 00:12:25.030 align:start position:0% about today is our log indexer which service<00:12:22.369> is<00:12:22.519> our<00:12:22.669> get<00:12:22.850> box<00:12:23.089> request<00:12:23.919> the<00:12:24.919> way 00:12:25.030 --> 00:12:25.040 align:start position:0% service is our get box request the way 00:12:25.040 --> 00:12:28.030 align:start position:0% service is our get box request the way that<00:12:25.279> if<00:12:25.759> your<00:12:25.999> your<00:12:26.119> clients<00:12:26.600> rich<00:12:27.079> we<00:12:27.410> want 00:12:28.030 --> 00:12:28.040 align:start position:0% that if your your clients rich we want 00:12:28.040 --> 00:12:30.299 align:start position:0% that if your your clients rich we want data<00:12:28.309> from<00:12:28.669> will<00:12:28.850> get<00:12:28.999> very<00:12:29.480> time-consuming 00:12:30.299 --> 00:12:30.309 align:start position:0% data from will get very time-consuming 00:12:30.309 --> 00:12:33.280 align:start position:0% data from will get very time-consuming it<00:12:31.309> retrieves<00:12:31.790> every<00:12:32.119> blog<00:12:32.359> compares<00:12:33.049> it<00:12:33.259> with 00:12:33.280 --> 00:12:33.290 align:start position:0% it retrieves every blog compares it with 00:12:33.290 --> 00:12:35.679 align:start position:0% it retrieves every blog compares it with the<00:12:33.470> bloom<00:12:33.889> filter<00:12:34.339> that<00:12:34.939> it<00:12:35.089> retrieves<00:12:35.509> the 00:12:35.679 --> 00:12:35.689 align:start position:0% the bloom filter that it retrieves the 00:12:35.689 --> 00:12:38.259 align:start position:0% the bloom filter that it retrieves the transaction<00:12:36.290> or<00:12:36.859> the<00:12:37.249> match<00:12:37.429> logs<00:12:37.819> and<00:12:38.089> that 00:12:38.259 --> 00:12:38.269 align:start position:0% transaction or the match logs and that 00:12:38.269 --> 00:12:41.409 align:start position:0% transaction or the match logs and that again<00:12:38.629> compares<00:12:39.529> the<00:12:39.980> generating<00:12:40.579> logs<00:12:40.730> with 00:12:41.409 --> 00:12:41.419 align:start position:0% again compares the generating logs with 00:12:41.419 --> 00:12:44.590 align:start position:0% again compares the generating logs with the<00:12:41.540> filter<00:12:41.889> it<00:12:42.889> works<00:12:43.220> really<00:12:43.519> great<00:12:43.730> for<00:12:43.850> a 00:12:44.590 --> 00:12:44.600 align:start position:0% the filter it works really great for a 00:12:44.600 --> 00:12:46.749 align:start position:0% the filter it works really great for a person<00:12:45.470> that's<00:12:45.679> just<00:12:45.769> create<00:12:46.489> their<00:12:46.730> own 00:12:46.749 --> 00:12:46.759 align:start position:0% person that's just create their own 00:12:46.759 --> 00:12:50.979 align:start position:0% person that's just create their own thoughts<00:12:47.749> using<00:12:48.350> their<00:12:48.499> own<00:12:48.529> note<00:12:48.919> but<00:12:49.449> we<00:12:50.449> get 00:12:50.979 --> 00:12:50.989 align:start position:0% thoughts using their own note but we get 00:12:50.989 --> 00:12:52.569 align:start position:0% thoughts using their own note but we get up<00:12:51.199> to<00:12:51.350> the<00:12:51.470> house<00:12:51.619> like<00:12:51.799> for<00:12:51.980> millions<00:12:52.429> get 00:12:52.569 --> 00:12:52.579 align:start position:0% up to the house like for millions get 00:12:52.579 --> 00:12:54.849 align:start position:0% up to the house like for millions get lock<00:12:52.790> request<00:12:53.119> today<00:12:53.629> so<00:12:54.019> what<00:12:54.290> that<00:12:54.379> happens 00:12:54.849 --> 00:12:54.859 align:start position:0% lock request today so what that happens 00:12:54.859 --> 00:12:57.159 align:start position:0% lock request today so what that happens in<00:12:55.129> it<00:12:55.279> over<00:12:55.639> Gardens<00:12:55.999> are<00:12:56.299> any<00:12:56.689> of<00:12:56.749> you<00:12:56.899> nodes 00:12:57.159 --> 00:12:57.169 align:start position:0% in it over Gardens are any of you nodes 00:12:57.169 --> 00:12:59.559 align:start position:0% in it over Gardens are any of you nodes and<00:12:57.379> also<00:12:57.679> increases<00:12:58.429> a<00:12:58.459> response<00:12:58.999> times<00:12:59.299> for 00:12:59.559 --> 00:12:59.569 align:start position:0% and also increases a response times for 00:12:59.569 --> 00:13:03.009 align:start position:0% and also increases a response times for our<00:12:59.720> users<00:13:00.109> so<00:13:00.410> we<00:13:01.339> actually<00:13:02.209> affects<00:13:02.779> all<00:13:02.989> our 00:13:03.009 --> 00:13:03.019 align:start position:0% our users so we actually affects all our 00:13:03.019 --> 00:13:06.549 align:start position:0% our users so we actually affects all our logs<00:13:03.379> live<00:13:03.709> incoming<00:13:04.189> new<00:13:04.309> blocks<00:13:05.470> what<00:13:06.470> are 00:13:06.549 --> 00:13:06.559 align:start position:0% logs live incoming new blocks what are 00:13:06.559 --> 00:13:08.319 align:start position:0% logs live incoming new blocks what are they<00:13:06.649> choosing<00:13:06.889> and<00:13:07.309> run<00:13:07.459> into<00:13:07.790> when<00:13:08.059> you<00:13:08.179> do 00:13:08.319 --> 00:13:08.329 align:start position:0% they choosing and run into when you do 00:13:08.329 --> 00:13:12.159 align:start position:0% they choosing and run into when you do this<00:13:08.480> is<00:13:08.799> to<00:13:09.879> correctly<00:13:10.879> attack<00:13:11.269> for<00:13:11.660> rewards 00:13:12.159 --> 00:13:12.169 align:start position:0% this is to correctly attack for rewards 00:13:12.169 --> 00:13:14.919 align:start position:0% this is to correctly attack for rewards or<00:13:12.459> you<00:13:13.459> might<00:13:13.639> be<00:13:13.790> servicing<00:13:14.299> incorrect<00:13:14.749> data 00:13:14.919 --> 00:13:14.929 align:start position:0% or you might be servicing incorrect data 00:13:14.929 --> 00:13:17.650 align:start position:0% or you might be servicing incorrect data so<00:13:15.769> the<00:13:16.129> log<00:13:16.369> index<00:13:16.759> are<00:13:16.939> actually<00:13:17.269> uses 00:13:17.650 --> 00:13:17.660 align:start position:0% so the log index are actually uses 00:13:17.660 --> 00:13:18.470 align:start position:0% so the log index are actually uses another 00:13:18.470 --> 00:13:18.480 align:start position:0% another 00:13:18.480 --> 00:13:21.769 align:start position:0% another service<00:13:18.810> that<00:13:18.839> we<00:13:19.079> have<00:13:19.339> sorry<00:13:20.600> called 00:13:21.769 --> 00:13:21.779 align:start position:0% service that we have sorry called 00:13:21.779 --> 00:13:26.329 align:start position:0% service that we have sorry called New<00:13:21.930> York<00:13:22.110> driver<00:13:22.440> and<00:13:23.209> rear<00:13:24.209> tracker<00:13:25.339> gets 00:13:26.329 --> 00:13:26.339 align:start position:0% New York driver and rear tracker gets 00:13:26.339 --> 00:13:28.730 align:start position:0% New York driver and rear tracker gets dead<00:13:26.639> in<00:13:26.820> blocks<00:13:27.180> if<00:13:27.480> we<00:13:27.810> have<00:13:27.959> a<00:13:27.990> block<00:13:28.230> five 00:13:28.730 --> 00:13:28.740 align:start position:0% dead in blocks if we have a block five 00:13:28.740 --> 00:13:30.980 align:start position:0% dead in blocks if we have a block five million<00:13:29.160> it<00:13:29.940> outputs<00:13:30.300> that<00:13:30.510> data<00:13:30.750> to<00:13:30.959> a 00:13:30.980 --> 00:13:30.990 align:start position:0% million it outputs that data to a 00:13:30.990 --> 00:13:33.079 align:start position:0% million it outputs that data to a consumer<00:13:31.560> in<00:13:31.740> which<00:13:31.889> case<00:13:32.100> is<00:13:32.339> the<00:13:32.550> logging 00:13:33.079 --> 00:13:33.089 align:start position:0% consumer in which case is the logging 00:13:33.089 --> 00:13:35.840 align:start position:0% consumer in which case is the logging mixer<00:13:33.480> the<00:13:33.959> log<00:13:34.139> of<00:13:34.260> extra<00:13:34.529> time<00:13:34.709> can<00:13:35.040> push<00:13:35.279> FX 00:13:35.840 --> 00:13:35.850 align:start position:0% mixer the log of extra time can push FX 00:13:35.850 --> 00:13:41.870 align:start position:0% mixer the log of extra time can push FX to<00:13:36.690> its<00:13:36.959> EE<00:13:37.110> a<00:13:37.529> we<00:13:37.980> use<00:13:38.160> MongoDB<00:13:40.639> continues<00:13:41.639> on 00:13:41.870 --> 00:13:41.880 align:start position:0% to its EE a we use MongoDB continues on 00:13:41.880 --> 00:13:45.410 align:start position:0% to its EE a we use MongoDB continues on with<00:13:42.089> block<00:13:42.630> per<00:13:42.870> million<00:13:43.199> one<00:13:44.089> log<00:13:45.089> effects 00:13:45.410 --> 00:13:45.420 align:start position:0% with block per million one log effects 00:13:45.420 --> 00:13:47.810 align:start position:0% with block per million one log effects are<00:13:45.570> updates<00:13:45.899> that<00:13:46.199> information<00:13:47.010> and<00:13:47.550> then 00:13:47.810 --> 00:13:47.820 align:start position:0% are updates that information and then 00:13:47.820 --> 00:13:50.449 align:start position:0% are updates that information and then when<00:13:48.029> we<00:13:48.149> get<00:13:48.329> lot<00:13:48.810> five<00:13:49.139> million<00:13:49.589> to<00:13:49.949> rework 00:13:50.449 --> 00:13:50.459 align:start position:0% when we get lot five million to rework 00:13:50.459 --> 00:13:52.850 align:start position:0% when we get lot five million to rework tracker<00:13:50.790> that<00:13:51.240> realizes<00:13:51.630> that<00:13:51.839> the<00:13:52.500> parent 00:13:52.850 --> 00:13:52.860 align:start position:0% tracker that realizes that the parent 00:13:52.860 --> 00:13:56.019 align:start position:0% tracker that realizes that the parent Hashim<00:13:53.399> current<00:13:53.760> block<00:13:54.000> does<00:13:54.839> not<00:13:55.050> match<00:13:55.350> the 00:13:56.019 --> 00:13:56.029 align:start position:0% Hashim current block does not match the 00:13:56.029 --> 00:13:58.310 align:start position:0% Hashim current block does not match the block<00:13:57.029> cache<00:13:57.240> of<00:13:57.420> the<00:13:57.449> previous<00:13:57.899> clock<00:13:58.079> that 00:13:58.310 --> 00:13:58.320 align:start position:0% block cache of the previous clock that 00:13:58.320 --> 00:14:01.100 align:start position:0% block cache of the previous clock that it<00:13:58.410> received<00:13:58.769> so<00:13:59.130> it<00:13:59.399> actually<00:13:59.899> emits<00:14:00.899> a 00:14:01.100 --> 00:14:01.110 align:start position:0% it received so it actually emits a 00:14:01.110 --> 00:14:03.259 align:start position:0% it received so it actually emits a rollback<00:14:01.440> event<00:14:01.920> which<00:14:02.339> the<00:14:02.579> law<00:14:02.730> context<00:14:03.089> or 00:14:03.259 --> 00:14:03.269 align:start position:0% rollback event which the law context or 00:14:03.269 --> 00:14:05.060 align:start position:0% rollback event which the law context or date<00:14:03.389> consumes<00:14:03.870> to<00:14:04.320> delete<00:14:04.740> that<00:14:04.889> information 00:14:05.060 --> 00:14:05.070 align:start position:0% date consumes to delete that information 00:14:05.070 --> 00:14:08.720 align:start position:0% date consumes to delete that information and<00:14:05.880> then<00:14:06.149> when<00:14:06.870> rework<00:14:07.260> tracker<00:14:07.730> retrieves 00:14:08.720 --> 00:14:08.730 align:start position:0% and then when rework tracker retrieves 00:14:08.730 --> 00:14:10.430 align:start position:0% and then when rework tracker retrieves the<00:14:08.910> correct<00:14:09.180> block<00:14:09.449> information<00:14:10.139> it<00:14:10.320> can 00:14:10.430 --> 00:14:10.440 align:start position:0% the correct block information it can 00:14:10.440 --> 00:14:12.910 align:start position:0% the correct block information it can then<00:14:10.680> make<00:14:11.519> sure<00:14:11.550> that<00:14:11.699> it<00:14:11.970> has<00:14:12.089> the<00:14:12.120> correct 00:14:12.910 --> 00:14:12.920 align:start position:0% then make sure that it has the correct 00:14:12.920 --> 00:14:15.740 align:start position:0% then make sure that it has the correct lobster-claw<00:14:13.920> fight<00:14:14.160> in<00:14:14.370> Amman<00:14:14.670> and<00:14:14.940> then<00:14:15.630> it 00:14:15.740 --> 00:14:15.750 align:start position:0% lobster-claw fight in Amman and then it 00:14:15.750 --> 00:14:17.840 align:start position:0% lobster-claw fight in Amman and then it just<00:14:15.899> continues<00:14:16.380> on<00:14:16.589> with<00:14:17.370> the<00:14:17.459> incoming 00:14:17.840 --> 00:14:17.850 align:start position:0% just continues on with the incoming 00:14:17.850 --> 00:14:21.079 align:start position:0% just continues on with the incoming locks<00:14:18.120> it's<00:14:18.600> a<00:14:18.870> very<00:14:19.500> simple<00:14:19.860> but<00:14:20.279> and<00:14:20.610> we<00:14:20.940> use 00:14:21.079 --> 00:14:21.089 align:start position:0% locks it's a very simple but and we use 00:14:21.089 --> 00:14:23.509 align:start position:0% locks it's a very simple but and we use it<00:14:21.120> right<00:14:21.510> now<00:14:21.690> to<00:14:21.750> index<00:14:22.350> logs<00:14:22.620> but<00:14:23.010> it<00:14:23.310> can 00:14:23.509 --> 00:14:23.519 align:start position:0% it right now to index logs but it can 00:14:23.519 --> 00:14:25.910 align:start position:0% it right now to index logs but it can actually<00:14:23.639> be<00:14:23.850> used<00:14:24.149> to<00:14:24.480> index<00:14:25.110> any<00:14:25.440> kind<00:14:25.769> of 00:14:25.910 --> 00:14:25.920 align:start position:0% actually be used to index any kind of 00:14:25.920 --> 00:14:27.680 align:start position:0% actually be used to index any kind of data<00:14:26.190> that's<00:14:26.490> associated<00:14:26.790> with<00:14:27.209> locking 00:14:27.680 --> 00:14:27.690 align:start position:0% data that's associated with locking 00:14:27.690 --> 00:14:33.319 align:start position:0% data that's associated with locking partition<00:14:29.779> so<00:14:30.779> this<00:14:31.019> is<00:14:31.199> a<00:14:31.230> very<00:14:31.649> simple<00:14:32.329> view 00:14:33.319 --> 00:14:33.329 align:start position:0% partition so this is a very simple view 00:14:33.329 --> 00:14:36.500 align:start position:0% partition so this is a very simple view of<00:14:33.540> how<00:14:33.690> we<00:14:33.750> handle<00:14:34.260> our<00:14:34.350> requests<00:14:35.510> the 00:14:36.500 --> 00:14:36.510 align:start position:0% of how we handle our requests the 00:14:36.510 --> 00:14:38.689 align:start position:0% of how we handle our requests the majority<00:14:37.050> of<00:14:37.110> the<00:14:37.319> traffic<00:14:37.500> that<00:14:37.800> we<00:14:37.920> get<00:14:38.130> gets 00:14:38.689 --> 00:14:38.699 align:start position:0% majority of the traffic that we get gets 00:14:38.699 --> 00:14:41.329 align:start position:0% majority of the traffic that we get gets handled<00:14:39.329> fire<00:14:39.569> near<00:14:39.839> near<00:14:40.500> head<00:14:40.769> cache<00:14:41.010> there 00:14:41.329 --> 00:14:41.339 align:start position:0% handled fire near near head cache there 00:14:41.339 --> 00:14:45.660 align:start position:0% handled fire near near head cache there and<00:14:41.639> then<00:14:42.209> we<00:14:42.600> have<00:14:42.810> our<00:14:42.990> set<00:14:43.260> and 00:14:45.660 --> 00:14:45.670 align:start position:0% 00:14:45.670 --> 00:14:49.060 align:start position:0% cassius<00:14:46.670> that<00:14:46.940> handle<00:14:47.900> the<00:14:48.140> more<00:14:48.590> frequently 00:14:49.060 --> 00:14:49.070 align:start position:0% cassius that handle the more frequently 00:14:49.070 --> 00:14:51.820 align:start position:0% cassius that handle the more frequently called<00:14:49.870> requests<00:14:50.870> and<00:14:51.050> then<00:14:51.140> whatever<00:14:51.500> is 00:14:51.820 --> 00:14:51.830 align:start position:0% called requests and then whatever is 00:14:51.830 --> 00:14:55.320 align:start position:0% called requests and then whatever is left<00:14:52.100> is<00:14:52.430> then<00:14:52.670> service<00:14:53.210> fire<00:14:53.450> theorem<00:14:53.990> yes 00:14:55.320 --> 00:14:55.330 align:start position:0% left is then service fire theorem yes 00:14:55.330 --> 00:14:57.970 align:start position:0% left is then service fire theorem yes so<00:14:56.330> those<00:14:56.480> are<00:14:56.690> some<00:14:56.990> of<00:14:57.140> the<00:14:57.170> market<00:14:57.560> services 00:14:57.970 --> 00:14:57.980 align:start position:0% so those are some of the market services 00:14:57.980 --> 00:15:00.730 align:start position:0% so those are some of the market services that<00:14:58.160> we<00:14:58.250> use<00:14:58.460> to<00:14:58.730> help<00:14:58.900> handle<00:14:59.900> the<00:15:00.500> large 00:15:00.730 --> 00:15:00.740 align:start position:0% that we use to help handle the large 00:15:00.740 --> 00:15:02.350 align:start position:0% that we use to help handle the large amount<00:15:01.010> of<00:15:01.100> traffic<00:15:01.430> that<00:15:01.610> we<00:15:01.880> get<00:15:02.060> but<00:15:02.270> we 00:15:02.350 --> 00:15:02.360 align:start position:0% amount of traffic that we get but we 00:15:02.360 --> 00:15:05.200 align:start position:0% amount of traffic that we get but we also<00:15:02.510> have<00:15:02.840> a<00:15:02.870> set<00:15:03.230> of<00:15:03.610> internal<00:15:04.610> tools<00:15:04.940> that 00:15:05.200 --> 00:15:05.210 align:start position:0% also have a set of internal tools that 00:15:05.210 --> 00:15:07.420 align:start position:0% also have a set of internal tools that we<00:15:05.330> use<00:15:05.480> just<00:15:05.810> to<00:15:05.990> help<00:15:06.530> maintain<00:15:07.040> our<00:15:07.070> the 00:15:07.420 --> 00:15:07.430 align:start position:0% we use just to help maintain our the 00:15:07.430 --> 00:15:10.180 align:start position:0% we use just to help maintain our the structure<00:15:07.850> one<00:15:08.810> of<00:15:08.900> the<00:15:08.990> recent<00:15:09.380> market 00:15:10.180 --> 00:15:10.190 align:start position:0% structure one of the recent market 00:15:10.190 --> 00:15:12.430 align:start position:0% structure one of the recent market services<00:15:10.790> that<00:15:11.030> we<00:15:11.240> open<00:15:11.510> sourced<00:15:11.870> is<00:15:12.080> key 00:15:12.430 --> 00:15:12.440 align:start position:0% services that we open sourced is key 00:15:12.440 --> 00:15:18.010 align:start position:0% services that we open sourced is key router<00:15:12.850> it<00:15:13.850> Maps<00:15:14.510> like<00:15:14.870> keys<00:15:15.490> to<00:15:16.490> a<00:15:17.020> consistent 00:15:18.010 --> 00:15:18.020 align:start position:0% router it Maps like keys to a consistent 00:15:18.020 --> 00:15:18.940 align:start position:0% router it Maps like keys to a consistent set<00:15:18.260> of<00:15:18.320> notes 00:15:18.940 --> 00:15:18.950 align:start position:0% set of notes 00:15:18.950 --> 00:15:22.300 align:start position:0% set of notes it<00:15:19.130> helps<00:15:19.760> route<00:15:20.690> specific<00:15:21.410> crisis<00:15:21.890> traffic 00:15:22.300 --> 00:15:22.310 align:start position:0% it helps route specific crisis traffic 00:15:22.310 --> 00:15:26.350 align:start position:0% it helps route specific crisis traffic to<00:15:22.610> a<00:15:22.640> consistent<00:15:23.450> data<00:15:23.780> source<00:15:24.050> a<00:15:25.270> member<00:15:26.270> of 00:15:26.350 --> 00:15:26.360 align:start position:0% to a consistent data source a member of 00:15:26.360 --> 00:15:29.080 align:start position:0% to a consistent data source a member of our<00:15:26.480> team<00:15:26.630> actually<00:15:26.960> Petroff<00:15:27.670> created<00:15:28.670> the 00:15:29.080 --> 00:15:29.090 align:start position:0% our team actually Petroff created the 00:15:29.090 --> 00:15:32.740 align:start position:0% our team actually Petroff created the Phe<00:15:29.600> node<00:15:29.840> which<00:15:30.290> is<00:15:30.550> like<00:15:31.550> a<00:15:31.690> way<00:15:32.690> to 00:15:32.740 --> 00:15:32.750 align:start position:0% Phe node which is like a way to 00:15:32.750 --> 00:15:35.440 align:start position:0% Phe node which is like a way to incentivize<00:15:33.230> the<00:15:34.160> use<00:15:34.310> of<00:15:34.520> like<00:15:34.700> clients<00:15:35.210> but 00:15:35.440 --> 00:15:35.450 align:start position:0% incentivize the use of like clients but 00:15:35.450 --> 00:15:38.260 align:start position:0% incentivize the use of like clients but we<00:15:35.750> actually<00:15:35.930> use<00:15:36.350> it<00:15:36.560> to<00:15:36.830> manage<00:15:37.490> carry<00:15:38.060> our 00:15:38.260 --> 00:15:38.270 align:start position:0% we actually use it to manage carry our 00:15:38.270 --> 00:15:41.440 align:start position:0% we actually use it to manage carry our notes<00:15:39.340> if<00:15:40.340> anybody's<00:15:40.700> interested<00:15:41.120> or<00:15:41.300> check 00:15:41.440 --> 00:15:41.450 align:start position:0% notes if anybody's interested or check 00:15:41.450 --> 00:15:43.960 align:start position:0% notes if anybody's interested or check it<00:15:41.570> out<00:15:41.690> it's<00:15:41.840> pretty<00:15:41.900> cool<00:15:42.220> and<00:15:43.220> also<00:15:43.400> we<00:15:43.760> have 00:15:43.960 --> 00:15:43.970 align:start position:0% it out it's pretty cool and also we have 00:15:43.970 --> 00:15:45.940 align:start position:0% it out it's pretty cool and also we have our<00:15:44.180> new<00:15:44.480> monitor<00:15:44.960> that<00:15:45.170> monitors<00:15:45.680> the<00:15:45.920> health 00:15:45.940 --> 00:15:45.950 align:start position:0% our new monitor that monitors the health 00:15:45.950 --> 00:15:49.480 align:start position:0% our new monitor that monitors the health of<00:15:46.250> our<00:15:46.430> notes<00:15:46.640> it<00:15:47.530> tracks<00:15:48.530> like<00:15:48.770> latest<00:15:49.220> blog 00:15:49.480 --> 00:15:49.490 align:start position:0% of our notes it tracks like latest blog 00:15:49.490 --> 00:15:51.370 align:start position:0% of our notes it tracks like latest blog number<00:15:49.700> and<00:15:50.180> then<00:15:50.300> compares<00:15:50.720> it<00:15:50.900> with<00:15:50.930> an 00:15:51.370 --> 00:15:51.380 align:start position:0% number and then compares it with an 00:15:51.380 --> 00:15:53.320 align:start position:0% number and then compares it with an external<00:15:51.890> source<00:15:52.070> like<00:15:52.430> either<00:15:52.700> scan<00:15:53.030> to<00:15:53.300> make 00:15:53.320 --> 00:15:53.330 align:start position:0% external source like either scan to make 00:15:53.330 --> 00:15:55.000 align:start position:0% external source like either scan to make sure<00:15:53.600> that<00:15:53.750> our<00:15:53.810> notes<00:15:54.200> are<00:15:54.320> in<00:15:54.350> your<00:15:54.500> head 00:15:55.000 --> 00:15:55.010 align:start position:0% sure that our notes are in your head 00:15:55.010 --> 00:15:58.180 align:start position:0% sure that our notes are in your head it<00:15:55.400> also<00:15:55.610> monitors<00:15:56.240> like<00:15:56.630> peer<00:15:57.560> care<00:15:57.830> out<00:15:57.950> on 00:15:58.180 --> 00:15:58.190 align:start position:0% it also monitors like peer care out on 00:15:58.190 --> 00:15:59.800 align:start position:0% it also monitors like peer care out on whether<00:15:58.490> or<00:15:58.610> not<00:15:58.670> it's<00:15:58.940> syncing<00:15:59.330> and<00:15:59.540> that<00:15:59.660> all 00:15:59.800 --> 00:15:59.810 align:start position:0% whether or not it's syncing and that all 00:15:59.810 --> 00:16:02.710 align:start position:0% whether or not it's syncing and that all helps<00:16:00.050> to<00:16:00.380> make<00:16:00.890> sure<00:16:01.040> that<00:16:01.250> the<00:16:01.580> that<00:16:02.210> are<00:16:02.360> if 00:16:02.710 --> 00:16:02.720 align:start position:0% helps to make sure that the that are if 00:16:02.720 --> 00:16:03.920 align:start position:0% helps to make sure that the that are if your<00:16:02.990> notes<00:16:03.170> are<00:16:03.350> healthy 00:16:03.920 --> 00:16:03.930 align:start position:0% your notes are healthy 00:16:03.930 --> 00:16:10.160 align:start position:0% your notes are healthy and<00:16:04.910> then<00:16:08.180> the<00:16:09.180> essence<00:16:09.480> is<00:16:09.600> really<00:16:09.840> just<00:16:10.050> the 00:16:10.160 --> 00:16:10.170 align:start position:0% and then the essence is really just the 00:16:10.170 --> 00:16:12.610 align:start position:0% and then the essence is really just the start<00:16:10.470> of<00:16:10.590> our<00:16:10.740> webinar<00:16:11.160> catcher<00:16:11.520> initiative 00:16:12.610 --> 00:16:12.620 align:start position:0% start of our webinar catcher initiative 00:16:12.620 --> 00:16:14.750 align:start position:0% start of our webinar catcher initiative having<00:16:13.620> this<00:16:13.770> source<00:16:14.040> of<00:16:14.130> truth<00:16:14.400> that<00:16:14.580> the 00:16:14.750 --> 00:16:14.760 align:start position:0% having this source of truth that the 00:16:14.760 --> 00:16:18.170 align:start position:0% having this source of truth that the structure<00:16:15.180> having<00:16:15.800> some<00:16:16.800> like<00:16:17.030> standard<00:16:18.030> way 00:16:18.170 --> 00:16:18.180 align:start position:0% structure having some like standard way 00:16:18.180 --> 00:16:20.660 align:start position:0% structure having some like standard way of<00:16:18.360> indexing<00:16:18.800> is<00:16:19.800> really<00:16:20.070> just<00:16:20.310> the<00:16:20.490> start 00:16:20.660 --> 00:16:20.670 align:start position:0% of indexing is really just the start 00:16:20.670 --> 00:16:22.490 align:start position:0% of indexing is really just the start over<00:16:21.240> the<00:16:21.300> next<00:16:21.510> few<00:16:21.840> months<00:16:21.990> really<00:16:22.260> the 00:16:22.490 --> 00:16:22.500 align:start position:0% over the next few months really the 00:16:22.500 --> 00:16:24.140 align:start position:0% over the next few months really the continuation<00:16:22.950> and<00:16:23.280> more<00:16:23.490> information<00:16:24.030> about 00:16:24.140 --> 00:16:24.150 align:start position:0% continuation and more information about 00:16:24.150 --> 00:16:27.170 align:start position:0% continuation and more information about how<00:16:24.690> we<00:16:24.750> bought<00:16:25.200> my<00:16:25.440> specific<00:16:25.910> recipe<00:16:26.910> of<00:16:27.000> your 00:16:27.170 --> 00:16:27.180 align:start position:0% how we bought my specific recipe of your 00:16:27.180 --> 00:16:30.200 align:start position:0% how we bought my specific recipe of your implants<00:16:27.540> assistance<00:16:28.280> and<00:16:29.280> that<00:16:29.790> one<00:16:30.030> of<00:16:30.060> the 00:16:30.200 --> 00:16:30.210 align:start position:0% implants assistance and that one of the 00:16:30.210 --> 00:16:31.340 align:start position:0% implants assistance and that one of the things<00:16:30.420> that<00:16:30.600> we<00:16:30.690> want<00:16:30.870> to<00:16:30.900> do<00:16:31.020> is<00:16:31.110> continue 00:16:31.340 --> 00:16:31.350 align:start position:0% things that we want to do is continue 00:16:31.350 --> 00:16:35.270 align:start position:0% things that we want to do is continue working<00:16:31.680> partners<00:16:32.550> in<00:16:32.730> the<00:16:32.790> ecosystem<00:16:34.280> t32 00:16:35.270 --> 00:16:35.280 align:start position:0% working partners in the ecosystem t32 00:16:35.280 --> 00:16:36.950 align:start position:0% working partners in the ecosystem t32 and<00:16:35.310> really<00:16:35.820> share<00:16:36.210> knowledge<00:16:36.450> so<00:16:36.780> that<00:16:36.810> we 00:16:36.950 --> 00:16:36.960 align:start position:0% and really share knowledge so that we 00:16:36.960 --> 00:16:38.480 align:start position:0% and really share knowledge so that we can<00:16:37.140> achieve<00:16:37.230> building<00:16:37.770> another<00:16:37.980> two<00:16:38.220> into 00:16:38.480 --> 00:16:38.490 align:start position:0% can achieve building another two into 00:16:38.490 --> 00:16:40.940 align:start position:0% can achieve building another two into that<00:16:38.750> and<00:16:39.750> we<00:16:40.020> always<00:16:40.200> want<00:16:40.500> to<00:16:40.590> do<00:16:40.650> it<00:16:40.770> in<00:16:40.890> a 00:16:40.940 --> 00:16:40.950 align:start position:0% that and we always want to do it in a 00:16:40.950 --> 00:16:43.340 align:start position:0% that and we always want to do it in a way<00:16:41.070> that's<00:16:41.100> over<00:16:41.520> declarative<00:16:42.270> and<00:16:42.450> the<00:16:43.140> last 00:16:43.340 --> 00:16:43.350 align:start position:0% way that's over declarative and the last 00:16:43.350 --> 00:16:45.050 align:start position:0% way that's over declarative and the last view<00:16:43.560> that<00:16:43.890> we<00:16:43.980> wanted<00:16:44.250> to<00:16:44.400> play<00:16:44.550> for<00:16:44.610> the<00:16:44.850> new 00:16:45.050 --> 00:16:45.060 align:start position:0% view that we wanted to play for the new 00:16:45.060 --> 00:16:48.550 align:start position:0% view that we wanted to play for the new yeah<00:16:45.390> that<00:16:45.780> was<00:16:45.900> nice<00:16:46.110> and<00:16:46.140> every<00:16:46.710> server<00:16:47.220> box 00:16:48.550 --> 00:16:48.560 align:start position:0% yeah that was nice and every server box 00:16:48.560 --> 00:16:52.850 align:start position:0% yeah that was nice and every server box provider<00:16:49.560> in<00:16:49.830> specific<00:16:50.810> service<00:16:51.810> and<00:16:52.080> so<00:16:52.470> the 00:16:52.850 --> 00:16:52.860 align:start position:0% provider in specific service and so the 00:16:52.860 --> 00:16:54.170 align:start position:0% provider in specific service and so the next<00:16:53.040> thing<00:16:53.130> kind<00:16:53.400> of<00:16:53.430> for<00:16:53.610> us<00:16:53.730> retracing 00:16:54.170 --> 00:16:54.180 align:start position:0% next thing kind of for us retracing 00:16:54.180 --> 00:16:55.910 align:start position:0% next thing kind of for us retracing today<00:16:54.780> if<00:16:55.050> you've<00:16:55.170> already<00:16:55.350> tried<00:16:55.590> running 00:16:55.910 --> 00:16:55.920 align:start position:0% today if you've already tried running 00:16:55.920 --> 00:16:59.250 align:start position:0% today if you've already tried running the<00:16:56.730> trace<00:16:57.600> an<00:16:57.750> API<00:16:58.170> bill 00:16:59.250 --> 00:16:59.260 align:start position:0% the trace an API bill 00:16:59.260 --> 00:17:02.250 align:start position:0% the trace an API bill that's<00:17:00.360> really<00:17:01.360> going<00:17:01.510> to<00:17:01.630> be<00:17:01.780> building<00:17:02.020> on 00:17:02.250 --> 00:17:02.260 align:start position:0% that's really going to be building on 00:17:02.260 --> 00:17:04.350 align:start position:0% that's really going to be building on time<00:17:02.530> as<00:17:02.770> well<00:17:03.070> really<00:17:03.340> building<00:17:03.820> on<00:17:03.970> top<00:17:04.180> of 00:17:04.350 --> 00:17:04.360 align:start position:0% time as well really building on top of 00:17:04.360 --> 00:17:08.630 align:start position:0% time as well really building on top of this<00:17:04.480> and<00:17:04.720> will<00:17:05.530> be<00:17:05.560> available<00:17:06.130> in<00:17:06.610> the<00:17:06.699> next 00:17:08.630 --> 00:17:08.640 align:start position:0% this and will be available in the next 00:17:08.640 --> 00:17:11.040 align:start position:0% this and will be available in the next outside<00:17:09.640> of<00:17:09.790> this<00:17:09.880> this<00:17:10.420> architecture<00:17:11.020> is 00:17:11.040 --> 00:17:11.050 align:start position:0% outside of this this architecture is 00:17:11.050 --> 00:17:12.630 align:start position:0% outside of this this architecture is generalized<00:17:11.589> it's<00:17:11.829> not<00:17:12.040> specific<00:17:12.520> to<00:17:12.550> that 00:17:12.630 --> 00:17:12.640 align:start position:0% generalized it's not specific to that 00:17:12.640 --> 00:17:15.449 align:start position:0% generalized it's not specific to that area<00:17:12.910> it's<00:17:13.420> definitely<00:17:14.199> easy<00:17:14.589> to<00:17:14.829> support<00:17:15.280> the 00:17:15.449 --> 00:17:15.459 align:start position:0% area it's definitely easy to support the 00:17:15.459 --> 00:17:18.569 align:start position:0% area it's definitely easy to support the vmas<00:17:15.880> treasonous<00:17:16.810> we<00:17:17.740> have<00:17:17.890> the<00:17:18.070> north<00:17:18.339> which 00:17:18.569 --> 00:17:18.579 align:start position:0% vmas treasonous we have the north which 00:17:18.579 --> 00:17:20.510 align:start position:0% vmas treasonous we have the north which means<00:17:18.880> in<00:17:19.000> the<00:17:19.089> near<00:17:19.270> future 00:17:20.510 --> 00:17:20.520 align:start position:0% means in the near future 00:17:20.520 --> 00:17:23.250 align:start position:0% means in the near future so<00:17:21.520> the<00:17:22.030> you<00:17:22.180> have<00:17:22.270> any<00:17:22.510> questions<00:17:23.079> we're 00:17:23.250 --> 00:17:23.260 align:start position:0% so the you have any questions we're 00:17:23.260 --> 00:17:24.960 align:start position:0% so the you have any questions we're going<00:17:23.380> to<00:17:23.440> be<00:17:23.500> doing<00:17:23.620> a<00:17:23.740> Q&A<00:17:23.980> session<00:17:24.370> from<00:17:24.760> 9 00:17:24.960 --> 00:17:24.970 align:start position:0% going to be doing a Q&A session from 9 00:17:24.970 --> 00:17:28.079 align:start position:0% going to be doing a Q&A session from 9 a.m.<00:17:25.000> to<00:17:25.449> noon<00:17:25.480> tomorrow<00:17:26.110> and<00:17:26.970> at<00:17:27.970> the 00:17:28.079 --> 00:17:28.089 align:start position:0% a.m. to noon tomorrow and at the 00:17:28.089 --> 00:17:30.690 align:start position:0% a.m. to noon tomorrow and at the consensus<00:17:28.630> view<00:17:28.660> please<00:17:29.530> stop<00:17:29.800> by<00:17:30.010> ask<00:17:30.460> us 00:17:30.690 --> 00:17:30.700 align:start position:0% consensus view please stop by ask us 00:17:30.700 --> 00:17:34.370 align:start position:0% consensus view please stop by ask us about<00:17:30.850> because<00:17:31.510> adherent<00:17:32.110> or<00:17:32.290> plus<00:17:32.650> this 00:17:34.370 --> 00:17:34.380 align:start position:0% about because adherent or plus this 00:17:34.380 --> 00:17:36.390 align:start position:0% about because adherent or plus this architecture<00:17:35.380> initiative<00:17:35.890> I've<00:17:36.100> just<00:17:36.280> driven 00:17:36.390 --> 00:17:36.400 align:start position:0% architecture initiative I've just driven 00:17:36.400 --> 00:17:39.420 align:start position:0% architecture initiative I've just driven by<00:17:36.820> and<00:17:36.970> check<00:17:37.270> out<00:17:37.510> these<00:17:37.870> great<00:17:38.140> DEFCON<00:17:39.130> 5 00:17:39.420 --> 00:17:39.430 align:start position:0% by and check out these great DEFCON 5 00:17:39.430 --> 00:17:41.790 align:start position:0% by and check out these great DEFCON 5 limited<00:17:40.210> edition<00:17:40.750> he's<00:17:41.110> available<00:17:41.380> if<00:17:41.710> you 00:17:41.790 --> 00:17:41.800 align:start position:0% limited edition he's available if you 00:17:41.800 --> 00:17:45.810 align:start position:0% limited edition he's available if you want<00:17:41.950> to<00:17:42.100> check<00:17:42.550> that<00:17:42.600> and<00:17:44.460> kind<00:17:45.460> of<00:17:45.520> numbers 00:17:45.810 --> 00:17:45.820 align:start position:0% want to check that and kind of numbers 00:17:45.820 --> 00:17:47.820 align:start position:0% want to check that and kind of numbers right<00:17:45.850> here<00:17:46.180> anybody<00:17:46.450> in<00:17:46.930> the<00:17:47.020> back<00:17:47.170> handouts 00:17:47.820 --> 00:17:47.830 align:start position:0% right here anybody in the back handouts 00:17:47.830 --> 00:17:50.950 align:start position:0% right here anybody in the back handouts and<00:17:48.100> swag<00:17:48.730> after<00:17:49.150> this 00:17:50.950 --> 00:17:50.960 align:start position:0% and swag after this 00:17:50.960 --> 00:17:57.700 align:start position:0% and swag after this and<00:17:51.049> Angie<00:17:51.460> and<00:17:52.460> that's<00:17:52.700> it<00:17:52.880> thank<00:17:53.210> you 00:17:57.700 --> 00:17:57.710 align:start position:0% 00:17:57.710 --> 00:18:03.900 align:start position:0% [Applause]