WEBVTT Kind: captions Language: en 00:00:13.959 --> 00:00:16.570 align:start position:0% hello<00:00:14.959> everybody<00:00:15.110> I'm<00:00:15.740> Alexi<00:00:16.100> crapper<00:00:16.340> the 00:00:16.570 --> 00:00:16.580 align:start position:0% hello everybody I'm Alexi crapper the 00:00:16.580 --> 00:00:18.700 align:start position:0% hello everybody I'm Alexi crapper the organizer<00:00:16.940> office<00:00:17.360> of<00:00:17.480> Scala<00:00:17.750> he<00:00:18.500> were<00:00:18.680> a 00:00:18.700 --> 00:00:18.710 align:start position:0% organizer office of Scala he were a 00:00:18.710 --> 00:00:20.950 align:start position:0% organizer office of Scala he were a locational<00:00:19.220> former<00:00:19.670> and<00:00:19.910> with<00:00:20.480> us<00:00:20.630> we<00:00:20.780> have 00:00:20.950 --> 00:00:20.960 align:start position:0% locational former and with us we have 00:00:20.960 --> 00:00:23.200 align:start position:0% locational former and with us we have Evan<00:00:21.530> Evan<00:00:22.040> this<00:00:22.340> is<00:00:22.400> the<00:00:22.520> CEO<00:00:22.700> and<00:00:22.820> founder<00:00:23.180> of 00:00:23.200 --> 00:00:23.210 align:start position:0% Evan Evan this is the CEO and founder of 00:00:23.210 --> 00:00:25.960 align:start position:0% Evan Evan this is the CEO and founder of fauna<00:00:23.840> and<00:00:24.110> we<00:00:24.260> actually<00:00:24.350> met<00:00:24.740> I<00:00:25.070> would<00:00:25.700> say 00:00:25.960 --> 00:00:25.970 align:start position:0% fauna and we actually met I would say 00:00:25.970 --> 00:00:28.480 align:start position:0% fauna and we actually met I would say about<00:00:26.450> a<00:00:26.510> year<00:00:26.600> ago<00:00:26.810> or<00:00:27.200> more<00:00:27.830> and<00:00:28.160> talked 00:00:28.480 --> 00:00:28.490 align:start position:0% about a year ago or more and talked 00:00:28.490 --> 00:00:32.880 align:start position:0% about a year ago or more and talked about<00:00:28.610> fauna<00:00:29.300> as<00:00:29.570> new<00:00:31.000> kind<00:00:32.000> of<00:00:32.029> database<00:00:32.300> and 00:00:32.880 --> 00:00:32.890 align:start position:0% about fauna as new kind of database and 00:00:32.890 --> 00:00:36.100 align:start position:0% about fauna as new kind of database and now<00:00:33.890> it<00:00:34.789> opens<00:00:34.969> his<00:00:35.360> doors<00:00:35.629> for<00:00:35.960> the 00:00:36.100 --> 00:00:36.110 align:start position:0% now it opens his doors for the 00:00:36.110 --> 00:00:37.960 align:start position:0% now it opens his doors for the subscriber<00:00:36.680> meter<00:00:36.890> for<00:00:37.040> the<00:00:37.100> first<00:00:37.280> time<00:00:37.460> so 00:00:37.960 --> 00:00:37.970 align:start position:0% subscriber meter for the first time so 00:00:37.970 --> 00:00:40.510 align:start position:0% subscriber meter for the first time so we're<00:00:38.120> really<00:00:38.210> excited<00:00:38.300> to<00:00:38.660> be<00:00:38.750> here<00:00:38.989> and<00:00:39.520> I'd 00:00:40.510 --> 00:00:40.520 align:start position:0% we're really excited to be here and I'd 00:00:40.520 --> 00:00:42.010 align:start position:0% we're really excited to be here and I'd like<00:00:40.640> to<00:00:40.700> catch<00:00:41.000> up<00:00:41.150> and<00:00:41.300> see<00:00:41.450> what's<00:00:41.660> new<00:00:41.870> with 00:00:42.010 --> 00:00:42.020 align:start position:0% like to catch up and see what's new with 00:00:42.020 --> 00:00:46.780 align:start position:0% like to catch up and see what's new with form<00:00:42.610> thanks<00:00:43.610> Lexi<00:00:44.950> yeah<00:00:45.950> we<00:00:46.100> moved<00:00:46.250> into<00:00:46.520> this 00:00:46.780 --> 00:00:46.790 align:start position:0% form thanks Lexi yeah we moved into this 00:00:46.790 --> 00:00:51.520 align:start position:0% form thanks Lexi yeah we moved into this place<00:00:47.540> about<00:00:48.470> two<00:00:49.100> months<00:00:49.370> ago<00:00:50.290> before<00:00:51.290> that 00:00:51.520 --> 00:00:51.530 align:start position:0% place about two months ago before that 00:00:51.530 --> 00:00:54.310 align:start position:0% place about two months ago before that we<00:00:51.890> were<00:00:51.980> in<00:00:52.070> the<00:00:52.910> top<00:00:53.210> floor<00:00:53.540> of<00:00:53.570> a<00:00:53.750> converted 00:00:54.310 --> 00:00:54.320 align:start position:0% we were in the top floor of a converted 00:00:54.320 --> 00:00:57.010 align:start position:0% we were in the top floor of a converted Victorian<00:00:54.470> near<00:00:55.160> South<00:00:55.489> Park<00:00:55.940> oh<00:00:56.090> yes<00:00:56.300> that's 00:00:57.010 --> 00:00:57.020 align:start position:0% Victorian near South Park oh yes that's 00:00:57.020 --> 00:00:58.840 align:start position:0% Victorian near South Park oh yes that's where<00:00:57.230> I<00:00:57.260> first<00:00:57.469> met<00:00:57.649> you<00:00:57.950> so<00:00:58.219> before<00:00:58.579> that<00:00:58.730> way 00:00:58.840 --> 00:00:58.850 align:start position:0% where I first met you so before that way 00:00:58.850 --> 00:01:01.350 align:start position:0% where I first met you so before that way or<00:00:59.000> my<00:00:59.120> basement<00:00:59.360> that<00:00:59.750> was<00:00:59.989> a<00:01:00.079> long<00:01:00.260> time<00:01:00.440> ago 00:01:01.350 --> 00:01:01.360 align:start position:0% or my basement that was a long time ago 00:01:01.360 --> 00:01:04.509 align:start position:0% or my basement that was a long time ago but<00:01:02.360> yeah<00:01:02.570> we're<00:01:02.750> 14<00:01:03.140> people<00:01:03.410> now<00:01:03.620> preparing 00:01:04.509 --> 00:01:04.519 align:start position:0% but yeah we're 14 people now preparing 00:01:04.519 --> 00:01:07.870 align:start position:0% but yeah we're 14 people now preparing for<00:01:04.610> our<00:01:05.000> public<00:01:05.449> launch<00:01:05.719> of<00:01:06.070> phone<00:01:07.070> NDB<00:01:07.520> in 00:01:07.870 --> 00:01:07.880 align:start position:0% for our public launch of phone NDB in 00:01:07.880 --> 00:01:12.129 align:start position:0% for our public launch of phone NDB in March<00:01:08.539> so<00:01:10.329> we're<00:01:11.329> rolling<00:01:11.450> out<00:01:11.689> previews 00:01:12.129 --> 00:01:12.139 align:start position:0% March so we're rolling out previews 00:01:12.139 --> 00:01:14.679 align:start position:0% March so we're rolling out previews especially<00:01:12.969> previews<00:01:13.969> of<00:01:13.999> the<00:01:14.179> serverless 00:01:14.679 --> 00:01:14.689 align:start position:0% especially previews of the serverless 00:01:14.689 --> 00:01:21.550 align:start position:0% especially previews of the serverless cloud<00:01:15.079> product<00:01:15.639> and<00:01:19.299> basically<00:01:20.439> finishing<00:01:21.439> of 00:01:21.550 --> 00:01:21.560 align:start position:0% cloud product and basically finishing of 00:01:21.560 --> 00:01:24.010 align:start position:0% cloud product and basically finishing of the<00:01:21.649> business<00:01:22.009> side<00:01:22.189> of<00:01:22.219> things<00:01:22.369> with<00:01:23.020> billing 00:01:24.010 --> 00:01:24.020 align:start position:0% the business side of things with billing 00:01:24.020 --> 00:01:26.620 align:start position:0% the business side of things with billing systems<00:01:25.090> improving<00:01:26.090> tutorials 00:01:26.620 --> 00:01:26.630 align:start position:0% systems improving tutorials 00:01:26.630 --> 00:01:28.090 align:start position:0% systems improving tutorials documentation<00:01:26.810> all<00:01:27.529> that<00:01:27.709> kind<00:01:27.920> of<00:01:28.009> stuff 00:01:28.090 --> 00:01:28.100 align:start position:0% documentation all that kind of stuff 00:01:28.100 --> 00:01:32.559 align:start position:0% documentation all that kind of stuff that<00:01:28.249> you<00:01:28.459> need<00:01:28.639> to<00:01:30.939> use<00:01:31.939> phone<00:01:32.209> as<00:01:32.450> a 00:01:32.559 --> 00:01:32.569 align:start position:0% that you need to use phone as a 00:01:32.569 --> 00:01:35.129 align:start position:0% that you need to use phone as a self-service<00:01:33.439> adopter<00:01:34.009> in<00:01:34.159> particular<00:01:34.759> and 00:01:35.129 --> 00:01:35.139 align:start position:0% self-service adopter in particular and 00:01:35.139 --> 00:01:37.629 align:start position:0% self-service adopter in particular and the<00:01:36.139> database<00:01:36.590> has<00:01:36.829> been<00:01:36.859> in<00:01:37.099> production<00:01:37.249> for 00:01:37.629 --> 00:01:37.639 align:start position:0% the database has been in production for 00:01:37.639 --> 00:01:39.879 align:start position:0% the database has been in production for a<00:01:37.909> couple<00:01:38.299> years<00:01:38.509> now<00:01:38.569> I'm<00:01:38.990> in<00:01:39.380> particular 00:01:39.879 --> 00:01:39.889 align:start position:0% a couple years now I'm in particular 00:01:39.889 --> 00:01:44.039 align:start position:0% a couple years now I'm in particular Nvidia<00:01:40.459> is<00:01:40.999> our<00:01:41.240> biggest<00:01:42.429> early<00:01:43.429> partner 00:01:44.039 --> 00:01:44.049 align:start position:0% Nvidia is our biggest early partner 00:01:44.049 --> 00:01:45.219 align:start position:0% Nvidia is our biggest early partner neiva 00:01:45.219 --> 00:01:45.229 align:start position:0% neiva 00:01:45.229 --> 00:01:48.309 align:start position:0% neiva on-premises<00:01:45.920> deployment<00:01:46.579> which<00:01:46.819> is<00:01:47.029> in<00:01:47.319> three 00:01:48.309 --> 00:01:48.319 align:start position:0% on-premises deployment which is in three 00:01:48.319 --> 00:01:50.949 align:start position:0% on-premises deployment which is in three data<00:01:48.529> centers<00:01:48.969> couple<00:01:49.969> dozen<00:01:50.329> nodes<00:01:50.569> and 00:01:50.949 --> 00:01:50.959 align:start position:0% data centers couple dozen nodes and 00:01:50.959 --> 00:01:53.550 align:start position:0% data centers couple dozen nodes and they've<00:01:51.109> scaled<00:01:51.409> it<00:01:51.529> up<00:01:51.649> and<00:01:51.859> down<00:01:51.979> over<00:01:52.039> time 00:01:53.550 --> 00:01:53.560 align:start position:0% they've scaled it up and down over time 00:01:53.560 --> 00:01:56.139 align:start position:0% they've scaled it up and down over time so<00:01:54.560> I<00:01:54.590> remember<00:01:54.950> we<00:01:55.069> talked<00:01:55.310> about 00:01:56.139 --> 00:01:56.149 align:start position:0% so I remember we talked about 00:01:56.149 --> 00:02:00.129 align:start position:0% so I remember we talked about Fona<00:01:56.779> and<00:01:57.109> I<00:01:57.740> thought<00:01:58.429> it's<00:01:58.609> really<00:01:58.700> a<00:01:59.659> cool 00:02:00.129 --> 00:02:00.139 align:start position:0% Fona and I thought it's really a cool 00:02:00.139 --> 00:02:02.050 align:start position:0% Fona and I thought it's really a cool way<00:02:00.380> kind<00:02:00.649> of<00:02:00.709> to<00:02:00.919> to<00:02:01.249> use<00:02:01.399> the<00:02:01.429> database<00:02:01.849> right 00:02:02.050 --> 00:02:02.060 align:start position:0% way kind of to to use the database right 00:02:02.060 --> 00:02:03.940 align:start position:0% way kind of to to use the database right because<00:02:02.329> it's<00:02:02.599> more<00:02:02.810> than<00:02:02.840> a<00:02:03.259> key<00:02:03.469> value<00:02:03.739> store 00:02:03.940 --> 00:02:03.950 align:start position:0% because it's more than a key value store 00:02:03.950 --> 00:02:05.889 align:start position:0% because it's more than a key value store right<00:02:04.639> it's<00:02:04.819> it's<00:02:05.060> an<00:02:05.179> object<00:02:05.509> store<00:02:05.689> can<00:02:05.840> you 00:02:05.889 --> 00:02:05.899 align:start position:0% right it's it's an object store can you 00:02:05.899 --> 00:02:09.070 align:start position:0% right it's it's an object store can you talk<00:02:06.079> a<00:02:06.109> little<00:02:06.169> bit<00:02:06.409> about<00:02:06.789> for<00:02:07.789> now<00:02:07.999> as<00:02:08.810> kind 00:02:09.070 --> 00:02:09.080 align:start position:0% talk a little bit about for now as kind 00:02:09.080 --> 00:02:10.389 align:start position:0% talk a little bit about for now as kind of<00:02:09.140> your<00:02:09.200> core<00:02:09.410> database<00:02:09.770> what<00:02:09.950> does<00:02:10.069> it<00:02:10.190> give 00:02:10.389 --> 00:02:10.399 align:start position:0% of your core database what does it give 00:02:10.399 --> 00:02:13.180 align:start position:0% of your core database what does it give you<00:02:10.610> more<00:02:11.110> than<00:02:12.110> kind<00:02:12.470> of<00:02:12.560> traditional 00:02:13.180 --> 00:02:13.190 align:start position:0% you more than kind of traditional 00:02:13.190 --> 00:02:16.850 align:start position:0% you more than kind of traditional databases<00:02:13.640> give<00:02:13.910> you<00:02:14.030> yes<00:02:14.840> so<00:02:15.110> fauna<00:02:15.440> is<00:02:15.800> a 00:02:16.850 --> 00:02:16.860 align:start position:0% databases give you yes so fauna is a 00:02:16.860 --> 00:02:20.820 align:start position:0% databases give you yes so fauna is a temporal<00:02:17.860> object-relational<00:02:19.830> consistent 00:02:20.820 --> 00:02:20.830 align:start position:0% temporal object-relational consistent 00:02:20.830 --> 00:02:24.449 align:start position:0% temporal object-relational consistent distributed<00:02:21.730> database<00:02:22.980> our<00:02:23.980> goal<00:02:24.280> is<00:02:24.430> to 00:02:24.449 --> 00:02:24.459 align:start position:0% distributed database our goal is to 00:02:24.459 --> 00:02:26.430 align:start position:0% distributed database our goal is to basically<00:02:24.850> marry<00:02:25.569> all<00:02:25.930> the<00:02:25.959> kind<00:02:26.290> of 00:02:26.430 --> 00:02:26.440 align:start position:0% basically marry all the kind of 00:02:26.440 --> 00:02:28.530 align:start position:0% basically marry all the kind of different<00:02:26.920> query<00:02:27.280> patterns<00:02:27.819> you<00:02:28.390> it 00:02:28.530 --> 00:02:28.540 align:start position:0% different query patterns you it 00:02:28.540 --> 00:02:32.120 align:start position:0% different query patterns you it typically<00:02:28.959> is<00:02:29.640> from<00:02:30.640> different<00:02:31.090> domains<00:02:31.510> like 00:02:32.120 --> 00:02:32.130 align:start position:0% typically is from different domains like 00:02:32.130 --> 00:02:35.370 align:start position:0% typically is from different domains like relational<00:02:33.130> document<00:02:33.790> graph<00:02:34.120> even<00:02:34.810> search 00:02:35.370 --> 00:02:35.380 align:start position:0% relational document graph even search 00:02:35.380 --> 00:02:38.400 align:start position:0% relational document graph even search analytics<00:02:35.790> eventually<00:02:36.810> into<00:02:37.810> a<00:02:37.840> single 00:02:38.400 --> 00:02:38.410 align:start position:0% analytics eventually into a single 00:02:38.410 --> 00:02:41.150 align:start position:0% analytics eventually into a single coherent<00:02:39.069> system<00:02:39.640> so<00:02:39.910> you<00:02:40.000> can<00:02:40.030> scale<00:02:40.480> that 00:02:41.150 --> 00:02:41.160 align:start position:0% coherent system so you can scale that 00:02:41.160 --> 00:02:43.590 align:start position:0% coherent system so you can scale that underlying<00:02:42.160> piece<00:02:42.400> of<00:02:42.550> infrastructure<00:02:43.120> and 00:02:43.590 --> 00:02:43.600 align:start position:0% underlying piece of infrastructure and 00:02:43.600 --> 00:02:45.630 align:start position:0% underlying piece of infrastructure and use<00:02:44.140> it<00:02:44.319> for<00:02:44.500> all<00:02:44.680> your<00:02:44.830> different<00:02:45.190> workloads 00:02:45.630 --> 00:02:45.640 align:start position:0% use it for all your different workloads 00:02:45.640 --> 00:02:49.199 align:start position:0% use it for all your different workloads and<00:02:45.940> share<00:02:46.180> data<00:02:46.450> across<00:02:46.660> teams<00:02:47.970> share<00:02:48.970> data 00:02:49.199 --> 00:02:49.209 align:start position:0% and share data across teams share data 00:02:49.209 --> 00:02:51.080 align:start position:0% and share data across teams share data across<00:02:49.390> data<00:02:49.900> centers<00:02:50.019> because<00:02:50.590> it's<00:02:50.769> a 00:02:51.080 --> 00:02:51.090 align:start position:0% across data centers because it's a 00:02:51.090 --> 00:02:53.490 align:start position:0% across data centers because it's a globally<00:02:52.090> distributed<00:02:52.269> system<00:02:53.080> as<00:02:53.200> well<00:02:53.380> and 00:02:53.490 --> 00:02:53.500 align:start position:0% globally distributed system as well and 00:02:53.500 --> 00:02:55.530 align:start position:0% globally distributed system as well and basically<00:02:53.620> get<00:02:54.550> back<00:02:54.730> to<00:02:54.910> a<00:02:54.940> world<00:02:55.180> where<00:02:55.450> you 00:02:55.530 --> 00:02:55.540 align:start position:0% basically get back to a world where you 00:02:55.540 --> 00:02:56.820 align:start position:0% basically get back to a world where you can<00:02:55.660> integrate<00:02:55.810> through<00:02:56.230> the<00:02:56.380> database<00:02:56.800> and 00:02:56.820 --> 00:02:56.830 align:start position:0% can integrate through the database and 00:02:56.830 --> 00:03:00.509 align:start position:0% can integrate through the database and trust<00:02:57.310> that<00:02:57.400> the<00:02:57.610> database<00:02:58.060> will<00:02:58.090> be<00:02:59.519> the 00:03:00.509 --> 00:03:00.519 align:start position:0% trust that the database will be the 00:03:00.519 --> 00:03:02.370 align:start position:0% trust that the database will be the single<00:03:00.790> lever<00:03:01.150> you<00:03:01.390> can<00:03:01.420> move<00:03:01.780> when<00:03:02.110> you<00:03:02.230> need 00:03:02.370 --> 00:03:02.380 align:start position:0% single lever you can move when you need 00:03:02.380 --> 00:03:04.490 align:start position:0% single lever you can move when you need to<00:03:02.500> scale<00:03:02.709> your<00:03:02.890> application<00:03:02.920> up<00:03:03.700> and<00:03:03.819> down 00:03:04.490 --> 00:03:04.500 align:start position:0% to scale your application up and down 00:03:04.500 --> 00:03:07.500 align:start position:0% to scale your application up and down right<00:03:05.500> and<00:03:05.920> so<00:03:06.250> it<00:03:06.400> for<00:03:06.610> this<00:03:06.790> you<00:03:07.209> need 00:03:07.500 --> 00:03:07.510 align:start position:0% right and so it for this you need 00:03:07.510 --> 00:03:09.210 align:start position:0% right and so it for this you need basically<00:03:08.170> two<00:03:08.500> so<00:03:08.860> you<00:03:08.920> all<00:03:09.100> right 00:03:09.210 --> 00:03:09.220 align:start position:0% basically two so you all right 00:03:09.220 --> 00:03:11.090 align:start position:0% basically two so you all right everything<00:03:09.610> inside<00:03:09.819> of<00:03:09.880> the<00:03:10.030> base<00:03:10.180> Iran 00:03:11.090 --> 00:03:11.100 align:start position:0% everything inside of the base Iran 00:03:11.100 --> 00:03:14.970 align:start position:0% everything inside of the base Iran analytics<00:03:12.100> queries<00:03:12.750> inside<00:03:13.750> other<00:03:13.930> ways<00:03:14.140> so 00:03:14.970 --> 00:03:14.980 align:start position:0% analytics queries inside other ways so 00:03:14.980 --> 00:03:19.350 align:start position:0% analytics queries inside other ways so you<00:03:15.040> have<00:03:15.340> your<00:03:15.580> own<00:03:16.380> DSL<00:03:17.380> for<00:03:18.160> the<00:03:18.340> queries<00:03:18.670> we 00:03:19.350 --> 00:03:19.360 align:start position:0% you have your own DSL for the queries we 00:03:19.360 --> 00:03:21.330 align:start position:0% you have your own DSL for the queries we should<00:03:19.540> control<00:03:19.840> what<00:03:20.260> support<00:03:20.650> yeah<00:03:21.070> the 00:03:21.330 --> 00:03:21.340 align:start position:0% should control what support yeah the 00:03:21.340 --> 00:03:23.610 align:start position:0% should control what support yeah the interface<00:03:22.299> is<00:03:22.540> a<00:03:22.570> functional<00:03:23.170> interface 00:03:23.610 --> 00:03:23.620 align:start position:0% interface is a functional interface 00:03:23.620 --> 00:03:26.759 align:start position:0% interface is a functional interface similar<00:03:24.010> to<00:03:24.430> link<00:03:25.000> in<00:03:25.360> the<00:03:25.540> c-sharp<00:03:26.049> world<00:03:26.470> you 00:03:26.759 --> 00:03:26.769 align:start position:0% similar to link in the c-sharp world you 00:03:26.769 --> 00:03:29.370 align:start position:0% similar to link in the c-sharp world you use<00:03:27.040> embedded<00:03:27.760> ESL's<00:03:28.390> in<00:03:28.630> your<00:03:28.780> application 00:03:29.370 --> 00:03:29.380 align:start position:0% use embedded ESL's in your application 00:03:29.380 --> 00:03:31.650 align:start position:0% use embedded ESL's in your application languages<00:03:29.980> and<00:03:30.160> that<00:03:30.280> means<00:03:30.489> that<00:03:30.790> your 00:03:31.650 --> 00:03:31.660 align:start position:0% languages and that means that your 00:03:31.660 --> 00:03:33.600 align:start position:0% languages and that means that your queries<00:03:31.959> are<00:03:32.079> type<00:03:32.290> safe<00:03:32.590> you<00:03:33.100> don't<00:03:33.130> to<00:03:33.430> learn 00:03:33.600 --> 00:03:33.610 align:start position:0% queries are type safe you don't to learn 00:03:33.610 --> 00:03:35.819 align:start position:0% queries are type safe you don't to learn new<00:03:33.790> syntax<00:03:34.360> you<00:03:35.200> just<00:03:35.440> have<00:03:35.590> to<00:03:35.709> learn 00:03:35.819 --> 00:03:35.829 align:start position:0% new syntax you just have to learn 00:03:35.829 --> 00:03:38.490 align:start position:0% new syntax you just have to learn phonosemantics<00:03:36.459> and<00:03:37.230> it's<00:03:38.230> pretty 00:03:38.490 --> 00:03:38.500 align:start position:0% phonosemantics and it's pretty 00:03:38.500 --> 00:03:41.699 align:start position:0% phonosemantics and it's pretty functional<00:03:38.829> too<00:03:40.200> in<00:03:41.200> a<00:03:41.260> functional 00:03:41.699 --> 00:03:41.709 align:start position:0% functional too in a functional 00:03:41.709 --> 00:03:43.470 align:start position:0% functional too in a functional programming<00:03:42.100> way<00:03:42.370> and<00:03:42.640> you<00:03:42.970> do<00:03:43.090> things<00:03:43.329> like 00:03:43.470 --> 00:03:43.480 align:start position:0% programming way and you do things like 00:03:43.480 --> 00:03:46.229 align:start position:0% programming way and you do things like my<00:03:43.630> app<00:03:43.750> and<00:03:43.780> fold<00:03:44.200> over<00:03:44.560> the<00:03:45.310> core<00:03:45.700> database 00:03:46.229 --> 00:03:46.239 align:start position:0% my app and fold over the core database 00:03:46.239 --> 00:03:48.960 align:start position:0% my app and fold over the core database primitives<00:03:46.810> and<00:03:47.109> page<00:03:47.859> through<00:03:48.130> indexes<00:03:48.760> and 00:03:48.960 --> 00:03:48.970 align:start position:0% primitives and page through indexes and 00:03:48.970 --> 00:03:50.400 align:start position:0% primitives and page through indexes and you<00:03:49.030> can<00:03:49.180> do<00:03:49.269> compute<00:03:49.720> and<00:03:49.870> you<00:03:49.930> can<00:03:50.049> do<00:03:50.170> set 00:03:50.400 --> 00:03:50.410 align:start position:0% you can do compute and you can do set 00:03:50.410 --> 00:03:52.400 align:start position:0% you can do compute and you can do set arithmetic<00:03:51.070> and<00:03:51.310> that<00:03:51.430> kind<00:03:51.670> of<00:03:51.730> thing<00:03:51.970> and 00:03:52.400 --> 00:03:52.410 align:start position:0% arithmetic and that kind of thing and 00:03:52.410 --> 00:03:55.490 align:start position:0% arithmetic and that kind of thing and ultimately<00:03:53.410> you<00:03:54.280> can<00:03:54.430> write<00:03:54.579> our<00:03:54.730> very<00:03:54.940> rich 00:03:55.490 --> 00:03:55.500 align:start position:0% ultimately you can write our very rich 00:03:55.500 --> 00:03:58.440 align:start position:0% ultimately you can write our very rich query<00:03:56.500> even<00:03:56.859> more<00:03:57.040> rich<00:03:57.250> than<00:03:57.280> sequel<00:03:58.180> allows 00:03:58.440 --> 00:03:58.450 align:start position:0% query even more rich than sequel allows 00:03:58.450 --> 00:04:00.960 align:start position:0% query even more rich than sequel allows remote<00:03:59.290> it<00:03:59.590> to<00:03:59.739> the<00:03:59.829> database<00:04:00.280> and<00:04:00.579> trust<00:04:00.850> that 00:04:00.960 --> 00:04:00.970 align:start position:0% remote it to the database and trust that 00:04:00.970 --> 00:04:02.990 align:start position:0% remote it to the database and trust that the<00:04:01.180> database<00:04:01.600> will<00:04:01.870> execute<00:04:02.200> it<00:04:02.530> in<00:04:02.650> the 00:04:02.990 --> 00:04:03.000 align:start position:0% the database will execute it in the 00:04:03.000 --> 00:04:06.330 align:start position:0% the database will execute it in the maximally<00:04:04.000> optimal<00:04:04.570> way<00:04:05.310> against<00:04:06.310> the 00:04:06.330 --> 00:04:06.340 align:start position:0% maximally optimal way against the 00:04:06.340 --> 00:04:09.750 align:start position:0% maximally optimal way against the underlying<00:04:06.850> data<00:04:07.239> interesting<00:04:08.230> so<00:04:08.950> I<00:04:09.250> already 00:04:09.750 --> 00:04:09.760 align:start position:0% underlying data interesting so I already 00:04:09.760 --> 00:04:10.979 align:start position:0% underlying data interesting so I already like<00:04:09.910> it<00:04:10.030> right<00:04:10.150> because<00:04:10.420> you<00:04:10.600> know<00:04:10.630> I'd<00:04:10.810> like 00:04:10.979 --> 00:04:10.989 align:start position:0% like it right because you know I'd like 00:04:10.989 --> 00:04:12.780 align:start position:0% like it right because you know I'd like you<00:04:11.170> know<00:04:11.290> I'd<00:04:11.709> like<00:04:11.859> my<00:04:12.070> my<00:04:12.280> query<00:04:12.489> language 00:04:12.780 --> 00:04:12.790 align:start position:0% you know I'd like my my query language 00:04:12.790 --> 00:04:14.699 align:start position:0% you know I'd like my my query language to<00:04:12.820> be<00:04:13.030> more<00:04:13.209> fun<00:04:13.390> than<00:04:13.420> psycho<00:04:13.810> and<00:04:14.440> if<00:04:14.590> it's 00:04:14.699 --> 00:04:14.709 align:start position:0% to be more fun than psycho and if it's 00:04:14.709 --> 00:04:17.370 align:start position:0% to be more fun than psycho and if it's functional<00:04:15.100> it's<00:04:15.220> even<00:04:15.370> better<00:04:15.750> so<00:04:16.750> so<00:04:17.109> is<00:04:17.229> it 00:04:17.370 --> 00:04:17.380 align:start position:0% functional it's even better so so is it 00:04:17.380 --> 00:04:21.960 align:start position:0% functional it's even better so so is it is<00:04:17.560> it<00:04:17.680> similar<00:04:17.859> in<00:04:18.549> a<00:04:18.669> way<00:04:18.700> I<00:04:20.700> mean<00:04:21.700> this<00:04:21.789> is 00:04:21.960 --> 00:04:21.970 align:start position:0% is it similar in a way I mean this is 00:04:21.970 --> 00:04:23.760 align:start position:0% is it similar in a way I mean this is closer<00:04:22.300> to<00:04:22.419> functional<00:04:22.900> languages<00:04:23.380> right 00:04:23.760 --> 00:04:23.770 align:start position:0% closer to functional languages right 00:04:23.770 --> 00:04:25.320 align:start position:0% closer to functional languages right because<00:04:24.010> you<00:04:24.460> know<00:04:24.550> the<00:04:24.700> problem<00:04:24.940> of<00:04:25.000> sequel 00:04:25.320 --> 00:04:25.330 align:start position:0% because you know the problem of sequel 00:04:25.330 --> 00:04:27.630 align:start position:0% because you know the problem of sequel it's<00:04:25.570> it's<00:04:25.750> so<00:04:26.140> declarative<00:04:26.770> right<00:04:27.460> so 00:04:27.630 --> 00:04:27.640 align:start position:0% it's it's so declarative right so 00:04:27.640 --> 00:04:29.620 align:start position:0% it's it's so declarative right so basically<00:04:28.060> you<00:04:28.210> can<00:04:28.360> lose<00:04:28.570> track<00:04:28.840> right<00:04:29.200> and 00:04:29.620 --> 00:04:29.630 align:start position:0% basically you can lose track right and 00:04:29.630 --> 00:04:31.360 align:start position:0% basically you can lose track right and to<00:04:29.720> create<00:04:30.020> a<00:04:30.080> bunch<00:04:30.230> of<00:04:30.290> temporary<00:04:30.770> tape 00:04:31.360 --> 00:04:31.370 align:start position:0% to create a bunch of temporary tape 00:04:31.370 --> 00:04:33.430 align:start position:0% to create a bunch of temporary tape tables<00:04:31.850> have<00:04:32.180> you<00:04:32.330> kind<00:04:32.510> of<00:04:32.570> decomposed<00:04:32.960> it<00:04:33.230> in 00:04:33.430 --> 00:04:33.440 align:start position:0% tables have you kind of decomposed it in 00:04:33.440 --> 00:04:36.880 align:start position:0% tables have you kind of decomposed it in weird<00:04:33.740> ways<00:04:33.800> so<00:04:34.580> how<00:04:35.300> does<00:04:35.360> it<00:04:35.630> feel<00:04:35.840> to<00:04:36.560> write 00:04:36.880 --> 00:04:36.890 align:start position:0% weird ways so how does it feel to write 00:04:36.890 --> 00:04:39.070 align:start position:0% weird ways so how does it feel to write like<00:04:37.100> a<00:04:37.130> long<00:04:37.610> complicated<00:04:37.850> form<00:04:38.390> of<00:04:38.510> queries 00:04:39.070 --> 00:04:39.080 align:start position:0% like a long complicated form of queries 00:04:39.080 --> 00:04:41.200 align:start position:0% like a long complicated form of queries to<00:04:39.170> give<00:04:39.290> it<00:04:39.350> a<00:04:39.410> program<00:04:39.830> you<00:04:40.400> like<00:04:40.820> a<00:04:40.850> little 00:04:41.200 --> 00:04:41.210 align:start position:0% to give it a program you like a little 00:04:41.210 --> 00:04:42.790 align:start position:0% to give it a program you like a little free<00:04:41.360> program<00:04:41.780> which<00:04:41.900> is<00:04:42.020> gonna<00:04:42.230> be<00:04:42.380> basically 00:04:42.790 --> 00:04:42.800 align:start position:0% free program which is gonna be basically 00:04:42.800 --> 00:04:46.330 align:start position:0% free program which is gonna be basically run<00:04:43.070> on<00:04:44.000> the<00:04:44.270> cluster<00:04:44.450> yeah<00:04:45.260> it's<00:04:45.950> it's 00:04:46.330 --> 00:04:46.340 align:start position:0% run on the cluster yeah it's it's 00:04:46.340 --> 00:04:47.830 align:start position:0% run on the cluster yeah it's it's exactly<00:04:46.760> like<00:04:46.850> that<00:04:47.180> so<00:04:47.390> you're<00:04:47.540> dealing<00:04:47.810> with 00:04:47.830 --> 00:04:47.840 align:start position:0% exactly like that so you're dealing with 00:04:47.840 --> 00:04:50.740 align:start position:0% exactly like that so you're dealing with immutable<00:04:48.620> data<00:04:48.650> structures<00:04:49.220> and<00:04:49.750> parallel 00:04:50.740 --> 00:04:50.750 align:start position:0% immutable data structures and parallel 00:04:50.750 --> 00:04:52.750 align:start position:0% immutable data structures and parallel computation<00:04:51.500> but<00:04:51.770> the<00:04:51.950> commutation<00:04:52.460> is 00:04:52.750 --> 00:04:52.760 align:start position:0% computation but the commutation is 00:04:52.760 --> 00:04:56.490 align:start position:0% computation but the commutation is explicit<00:04:53.390> oh<00:04:53.570> like<00:04:54.320> you're<00:04:54.830> you<00:04:55.070> essentially 00:04:56.490 --> 00:04:56.500 align:start position:0% explicit oh like you're you essentially 00:04:56.500 --> 00:04:59.200 align:start position:0% explicit oh like you're you essentially you<00:04:57.500> essentially<00:04:57.890> compose<00:04:58.370> the<00:04:58.610> query<00:04:58.880> plan 00:04:59.200 --> 00:04:59.210 align:start position:0% you essentially compose the query plan 00:04:59.210 --> 00:05:01.780 align:start position:0% you essentially compose the query plan in<00:04:59.540> your<00:04:59.750> in<00:05:00.170> your<00:05:00.200> query<00:05:00.620> so<00:05:01.400> you<00:05:01.460> know<00:05:01.640> what 00:05:01.780 --> 00:05:01.790 align:start position:0% in your in your query so you know what 00:05:01.790 --> 00:05:03.520 align:start position:0% in your in your query so you know what the<00:05:01.850> database<00:05:02.240> is<00:05:02.390> gonna<00:05:02.600> do<00:05:02.840> it's<00:05:03.200> not<00:05:03.410> gonna 00:05:03.520 --> 00:05:03.530 align:start position:0% the database is gonna do it's not gonna 00:05:03.530 --> 00:05:05.500 align:start position:0% the database is gonna do it's not gonna change<00:05:03.650> its<00:05:04.040> mind<00:05:04.190> and<00:05:04.490> start<00:05:04.730> optimizing<00:05:04.910> in 00:05:05.500 --> 00:05:05.510 align:start position:0% change its mind and start optimizing in 00:05:05.510 --> 00:05:07.390 align:start position:0% change its mind and start optimizing in a<00:05:05.600> different<00:05:05.990> way<00:05:06.110> as<00:05:06.380> your<00:05:06.620> data<00:05:06.830> set<00:05:07.100> gross 00:05:07.390 --> 00:05:07.400 align:start position:0% a different way as your data set gross 00:05:07.400 --> 00:05:09.340 align:start position:0% a different way as your data set gross you<00:05:07.670> don't<00:05:07.850> run<00:05:08.060> explain<00:05:08.510> to<00:05:08.840> understand 00:05:09.340 --> 00:05:09.350 align:start position:0% you don't run explain to understand 00:05:09.350 --> 00:05:11.920 align:start position:0% you don't run explain to understand which<00:05:09.530> index<00:05:09.980> it's<00:05:10.190> gonna<00:05:10.370> use<00:05:10.670> you<00:05:11.000> say<00:05:11.240> these 00:05:11.920 --> 00:05:11.930 align:start position:0% which index it's gonna use you say these 00:05:11.930 --> 00:05:13.720 align:start position:0% which index it's gonna use you say these are<00:05:12.050> my<00:05:12.230> indexes<00:05:12.830> I'm<00:05:13.010> gonna<00:05:13.130> start<00:05:13.370> with<00:05:13.490> them 00:05:13.720 --> 00:05:13.730 align:start position:0% are my indexes I'm gonna start with them 00:05:13.730 --> 00:05:15.700 align:start position:0% are my indexes I'm gonna start with them then<00:05:14.030> I<00:05:14.090> want<00:05:14.240> to<00:05:14.330> do<00:05:14.420> these<00:05:14.600> operations<00:05:15.290> I'm 00:05:15.700 --> 00:05:15.710 align:start position:0% then I want to do these operations I'm 00:05:15.710 --> 00:05:18.970 align:start position:0% then I want to do these operations I'm gonna<00:05:15.860> do<00:05:16.010> this<00:05:16.300> this<00:05:17.300> set<00:05:17.690> algebra<00:05:18.230> gets<00:05:18.710> some 00:05:18.970 --> 00:05:18.980 align:start position:0% gonna do this this set algebra gets some 00:05:18.980 --> 00:05:20.920 align:start position:0% gonna do this this set algebra gets some results<00:05:19.460> cursor<00:05:19.910> through<00:05:20.180> it<00:05:20.360> that<00:05:20.570> kind<00:05:20.810> of 00:05:20.920 --> 00:05:20.930 align:start position:0% results cursor through it that kind of 00:05:20.930 --> 00:05:23.800 align:start position:0% results cursor through it that kind of thing<00:05:21.110> so<00:05:21.350> it's<00:05:21.500> very<00:05:21.620> explicit<00:05:22.690> and<00:05:23.690> that 00:05:23.800 --> 00:05:23.810 align:start position:0% thing so it's very explicit and that 00:05:23.810 --> 00:05:25.780 align:start position:0% thing so it's very explicit and that lets<00:05:24.080> us<00:05:24.230> guarantee<00:05:24.770> a<00:05:25.130> very<00:05:25.400> consistent 00:05:25.780 --> 00:05:25.790 align:start position:0% lets us guarantee a very consistent 00:05:25.790 --> 00:05:27.850 align:start position:0% lets us guarantee a very consistent performance<00:05:26.600> profile<00:05:27.050> as<00:05:27.290> you<00:05:27.320> scale<00:05:27.650> your 00:05:27.850 --> 00:05:27.860 align:start position:0% performance profile as you scale your 00:05:27.860 --> 00:05:29.590 align:start position:0% performance profile as you scale your systems<00:05:28.310> up<00:05:28.490> and<00:05:28.670> down<00:05:28.820> you<00:05:29.060> can<00:05:29.090> trust<00:05:29.480> that 00:05:29.590 --> 00:05:29.600 align:start position:0% systems up and down you can trust that 00:05:29.600 --> 00:05:32.370 align:start position:0% systems up and down you can trust that the<00:05:29.840> execution<00:05:30.200> pattern<00:05:30.860> isn't<00:05:31.010> gonna<00:05:31.220> change 00:05:32.370 --> 00:05:32.380 align:start position:0% the execution pattern isn't gonna change 00:05:32.380 --> 00:05:33.970 align:start position:0% the execution pattern isn't gonna change interesting 00:05:33.970 --> 00:05:33.980 align:start position:0% interesting 00:05:33.980 --> 00:05:36.790 align:start position:0% interesting so<00:05:34.370> how<00:05:34.580> do<00:05:34.640> you<00:05:34.820> feed<00:05:35.150> your<00:05:35.390> data<00:05:35.780> base<00:05:36.380> right 00:05:36.790 --> 00:05:36.800 align:start position:0% so how do you feed your data base right 00:05:36.800 --> 00:05:39.610 align:start position:0% so how do you feed your data base right like<00:05:37.040> I<00:05:37.370> think<00:05:37.940> there<00:05:38.060> is<00:05:38.120> a<00:05:38.180> lot<00:05:38.360> of<00:05:38.620> activity 00:05:39.610 --> 00:05:39.620 align:start position:0% like I think there is a lot of activity 00:05:39.620 --> 00:05:41.590 align:start position:0% like I think there is a lot of activity in<00:05:39.650> open<00:05:39.950> source<00:05:40.130> text<00:05:40.550> to<00:05:40.610> put<00:05:40.790> together<00:05:40.910> data 00:05:41.590 --> 00:05:41.600 align:start position:0% in open source text to put together data 00:05:41.600 --> 00:05:43.900 align:start position:0% in open source text to put together data pipelines<00:05:42.020> right<00:05:42.380> sort<00:05:42.590> of<00:05:42.680> Kafka<00:05:43.100> feeding 00:05:43.900 --> 00:05:43.910 align:start position:0% pipelines right sort of Kafka feeding 00:05:43.910 --> 00:05:47.080 align:start position:0% pipelines right sort of Kafka feeding spark<00:05:44.300> reading<00:05:44.810> Cassandra<00:05:45.820> right<00:05:46.820> on<00:05:46.910> top<00:05:47.060> of 00:05:47.080 --> 00:05:47.090 align:start position:0% spark reading Cassandra right on top of 00:05:47.090 --> 00:05:50.050 align:start position:0% spark reading Cassandra right on top of messes<00:05:47.570> how<00:05:48.200> do<00:05:48.260> you<00:05:48.530> compare<00:05:49.040> to<00:05:49.490> this<00:05:49.850> mac 00:05:50.050 --> 00:05:50.060 align:start position:0% messes how do you compare to this mac 00:05:50.060 --> 00:05:56.260 align:start position:0% messes how do you compare to this mac stack<00:05:50.270> effectively<00:05:51.190> so<00:05:52.190> umm<00:05:52.400> I<00:05:53.770> mean<00:05:54.770> funny<00:05:55.270> in 00:05:56.260 --> 00:05:56.270 align:start position:0% stack effectively so umm I mean funny in 00:05:56.270 --> 00:05:58.360 align:start position:0% stack effectively so umm I mean funny in a<00:05:56.390> way<00:05:56.540> it's<00:05:56.720> a<00:05:56.810> traditional<00:05:57.410> relational 00:05:58.360 --> 00:05:58.370 align:start position:0% a way it's a traditional relational 00:05:58.370 --> 00:06:01.600 align:start position:0% a way it's a traditional relational database<00:05:58.910> it's<00:05:59.180> just<00:05:59.390> not<00:05:59.570> SQL<00:06:00.170> so<00:06:00.560> you<00:06:01.460> can 00:06:01.600 --> 00:06:01.610 align:start position:0% database it's just not SQL so you can 00:06:01.610 --> 00:06:03.580 align:start position:0% database it's just not SQL so you can use<00:06:01.730> it<00:06:01.880> as<00:06:01.970> a<00:06:02.000> sink<00:06:02.390> for<00:06:02.720> data<00:06:02.960> you<00:06:03.170> compute 00:06:03.580 --> 00:06:03.590 align:start position:0% use it as a sink for data you compute 00:06:03.590 --> 00:06:06.010 align:start position:0% use it as a sink for data you compute somewhere<00:06:03.950> else<00:06:04.130> but<00:06:04.520> you<00:06:04.640> can<00:06:04.760> also<00:06:05.020> keep 00:06:06.010 --> 00:06:06.020 align:start position:0% somewhere else but you can also keep 00:06:06.020 --> 00:06:07.840 align:start position:0% somewhere else but you can also keep your<00:06:06.200> core<00:06:06.440> business<00:06:06.620> objects<00:06:07.340> in<00:06:07.460> it<00:06:07.610> in<00:06:07.760> a 00:06:07.840 --> 00:06:07.850 align:start position:0% your core business objects in it in a 00:06:07.850 --> 00:06:10.330 align:start position:0% your core business objects in it in a fully<00:06:08.090> normalized<00:06:08.630> way<00:06:08.980> compose<00:06:09.980> them<00:06:10.220> with 00:06:10.330 --> 00:06:10.340 align:start position:0% fully normalized way compose them with 00:06:10.340 --> 00:06:13.830 align:start position:0% fully normalized way compose them with queries<00:06:10.990> push<00:06:11.990> a<00:06:12.020> lot<00:06:12.290> of<00:06:12.440> it<00:06:12.590> um<00:06:12.800> especially 00:06:13.830 --> 00:06:13.840 align:start position:0% queries push a lot of it um especially 00:06:13.840 --> 00:06:16.480 align:start position:0% queries push a lot of it um especially index<00:06:14.840> computation<00:06:15.620> that<00:06:15.650> you<00:06:15.830> might<00:06:16.070> do<00:06:16.280> in<00:06:16.310> a 00:06:16.480 --> 00:06:16.490 align:start position:0% index computation that you might do in a 00:06:16.490 --> 00:06:18.520 align:start position:0% index computation that you might do in a second<00:06:16.910> system<00:06:17.120> like<00:06:17.840> spark<00:06:18.260> or 00:06:18.520 --> 00:06:18.530 align:start position:0% second system like spark or 00:06:18.530 --> 00:06:22.660 align:start position:0% second system like spark or elasticsearch<00:06:19.460> intifada<00:06:21.070> in<00:06:22.070> terms<00:06:22.400> of<00:06:22.580> a 00:06:22.660 --> 00:06:22.670 align:start position:0% elasticsearch intifada in terms of a 00:06:22.670 --> 00:06:24.190 align:start position:0% elasticsearch intifada in terms of a source<00:06:22.970> though<00:06:23.270> because<00:06:23.480> the<00:06:23.750> underlying 00:06:24.190 --> 00:06:24.200 align:start position:0% source though because the underlying 00:06:24.200 --> 00:06:26.260 align:start position:0% source though because the underlying data<00:06:24.530> model<00:06:24.980> is<00:06:25.130> temporal<00:06:25.790> you<00:06:25.970> can<00:06:26.120> get 00:06:26.260 --> 00:06:26.270 align:start position:0% data model is temporal you can get 00:06:26.270 --> 00:06:28.090 align:start position:0% data model is temporal you can get change<00:06:26.570> feeds<00:06:26.870> for<00:06:27.170> any<00:06:27.350> query<00:06:27.650> out<00:06:27.860> of<00:06:27.980> the 00:06:28.090 --> 00:06:28.100 align:start position:0% change feeds for any query out of the 00:06:28.100 --> 00:06:30.130 align:start position:0% change feeds for any query out of the system<00:06:28.550> yes<00:06:28.970> you<00:06:29.180> can<00:06:29.300> say<00:06:29.480> like<00:06:29.690> oh<00:06:29.840> here's<00:06:30.080> a 00:06:30.130 --> 00:06:30.140 align:start position:0% system yes you can say like oh here's a 00:06:30.140 --> 00:06:32.920 align:start position:0% system yes you can say like oh here's a distributed<00:06:30.740> graph<00:06:30.950> join<00:06:31.280> an<00:06:32.060> activity<00:06:32.630> feed 00:06:32.920 --> 00:06:32.930 align:start position:0% distributed graph join an activity feed 00:06:32.930 --> 00:06:35.590 align:start position:0% distributed graph join an activity feed well<00:06:33.890> what<00:06:34.040> happened<00:06:34.460> between<00:06:34.730> the<00:06:35.120> last<00:06:35.330> time 00:06:35.590 --> 00:06:35.600 align:start position:0% well what happened between the last time 00:06:35.600 --> 00:06:36.230 align:start position:0% well what happened between the last time I<00:06:35.630> looked<00:06:35.930> at 00:06:36.230 --> 00:06:36.240 align:start position:0% I looked at 00:06:36.240 --> 00:06:39.499 align:start position:0% I looked at now<00:06:36.569> and<00:06:36.810> you<00:06:36.840> get<00:06:37.050> a<00:06:37.080> bunch<00:06:37.319> of<00:06:38.330> rather<00:06:39.330> than 00:06:39.499 --> 00:06:39.509 align:start position:0% now and you get a bunch of rather than 00:06:39.509 --> 00:06:41.180 align:start position:0% now and you get a bunch of rather than just<00:06:39.840> a<00:06:39.930> different<00:06:40.289> results<00:06:40.710> that<00:06:40.770> you<00:06:41.009> get<00:06:41.160> a 00:06:41.180 --> 00:06:41.190 align:start position:0% just a different results that you get a 00:06:41.190 --> 00:06:42.830 align:start position:0% just a different results that you get a bunch<00:06:41.340> of<00:06:41.490> change<00:06:41.819> events<00:06:42.270> that<00:06:42.419> you<00:06:42.509> can<00:06:42.660> use 00:06:42.830 --> 00:06:42.840 align:start position:0% bunch of change events that you can use 00:06:42.840 --> 00:06:45.770 align:start position:0% bunch of change events that you can use to<00:06:43.050> synchronize<00:06:43.590> something<00:06:44.069> downstream<00:06:44.780> so 00:06:45.770 --> 00:06:45.780 align:start position:0% to synchronize something downstream so 00:06:45.780 --> 00:06:48.110 align:start position:0% to synchronize something downstream so the<00:06:46.620> goal<00:06:46.830> eventually<00:06:46.979> is<00:06:47.400> to<00:06:47.580> internalize 00:06:48.110 --> 00:06:48.120 align:start position:0% the goal eventually is to internalize 00:06:48.120 --> 00:06:51.170 align:start position:0% the goal eventually is to internalize all<00:06:48.180> those<00:06:48.479> concerns<00:06:49.669> right<00:06:50.669> now<00:06:50.849> it<00:06:51.000> works 00:06:51.170 --> 00:06:51.180 align:start position:0% all those concerns right now it works 00:06:51.180 --> 00:06:54.800 align:start position:0% all those concerns right now it works really<00:06:51.449> well<00:06:51.569> as<00:06:52.080> a<00:06:52.759> canonical<00:06:53.759> store<00:06:54.300> for 00:06:54.800 --> 00:06:54.810 align:start position:0% really well as a canonical store for 00:06:54.810 --> 00:06:57.589 align:start position:0% really well as a canonical store for fully<00:06:55.319> normalized<00:06:55.860> Business<00:06:56.250> Objects<00:06:56.789> in 00:06:57.589 --> 00:06:57.599 align:start position:0% fully normalized Business Objects in 00:06:57.599 --> 00:06:59.480 align:start position:0% fully normalized Business Objects in particular<00:06:58.139> social<00:06:58.470> graphs<00:06:58.889> that<00:06:59.039> kind<00:06:59.400> of 00:06:59.480 --> 00:06:59.490 align:start position:0% particular social graphs that kind of 00:06:59.490 --> 00:07:04.249 align:start position:0% particular social graphs that kind of thing<00:07:00.530> or<00:07:01.530> as<00:07:02.190> a<00:07:02.220> low<00:07:02.520> latency<00:07:03.259> distributed 00:07:04.249 --> 00:07:04.259 align:start position:0% thing or as a low latency distributed 00:07:04.259 --> 00:07:06.620 align:start position:0% thing or as a low latency distributed sync<00:07:04.590> for<00:07:05.580> stuff<00:07:05.819> you<00:07:05.970> might<00:07:06.120> compete<00:07:06.569> at 00:07:06.620 --> 00:07:06.630 align:start position:0% sync for stuff you might compete at 00:07:06.630 --> 00:07:08.960 align:start position:0% sync for stuff you might compete at upstream<00:07:06.960> like<00:07:07.289> he<00:07:07.440> went<00:07:07.940> essentially<00:07:08.940> a 00:07:08.960 --> 00:07:08.970 align:start position:0% upstream like he went essentially a 00:07:08.970 --> 00:07:11.300 align:start position:0% upstream like he went essentially a document<00:07:09.810> database<00:07:10.080> that<00:07:10.409> you<00:07:10.530> can<00:07:10.560> index<00:07:11.099> and 00:07:11.300 --> 00:07:11.310 align:start position:0% document database that you can index and 00:07:11.310 --> 00:07:13.249 align:start position:0% document database that you can index and scale<00:07:11.580> because<00:07:11.909> you<00:07:12.030> have<00:07:12.210> all<00:07:12.360> this<00:07:12.509> offline 00:07:13.249 --> 00:07:13.259 align:start position:0% scale because you have all this offline 00:07:13.259 --> 00:07:15.529 align:start position:0% scale because you have all this offline commutation<00:07:13.919> from<00:07:14.220> ml<00:07:14.550> privacy<00:07:15.090> so<00:07:15.300> where<00:07:15.479> are 00:07:15.529 --> 00:07:15.539 align:start position:0% commutation from ml privacy so where are 00:07:15.539 --> 00:07:17.839 align:start position:0% commutation from ml privacy so where are you<00:07:15.599> going<00:07:15.780> to<00:07:15.840> put<00:07:16.020> it<00:07:16.199> mm-hmm<00:07:16.889> wow<00:07:17.669> this 00:07:17.839 --> 00:07:17.849 align:start position:0% you going to put it mm-hmm wow this 00:07:17.849 --> 00:07:19.610 align:start position:0% you going to put it mm-hmm wow this sounds<00:07:18.000> really<00:07:18.240> really<00:07:18.419> cool<00:07:18.690> I<00:07:18.960> mean<00:07:19.380> it 00:07:19.610 --> 00:07:19.620 align:start position:0% sounds really really cool I mean it 00:07:19.620 --> 00:07:21.740 align:start position:0% sounds really really cool I mean it sounds<00:07:19.889> almost<00:07:20.039> like<00:07:20.370> you<00:07:21.240> know<00:07:21.360> if<00:07:21.479> I<00:07:21.539> want<00:07:21.720> to 00:07:21.740 --> 00:07:21.750 align:start position:0% sounds almost like you know if I want to 00:07:21.750 --> 00:07:23.270 align:start position:0% sounds almost like you know if I want to build<00:07:21.930> a<00:07:22.020> startup<00:07:22.380> I<00:07:22.500> can<00:07:22.650> take<00:07:22.800> this<00:07:22.949> and 00:07:23.270 --> 00:07:23.280 align:start position:0% build a startup I can take this and 00:07:23.280 --> 00:07:25.820 align:start position:0% build a startup I can take this and solve<00:07:24.270> all<00:07:24.360> the<00:07:24.479> problems<00:07:24.870> so<00:07:25.380> I<00:07:25.409> wonder<00:07:25.740> what 00:07:25.820 --> 00:07:25.830 align:start position:0% solve all the problems so I wonder what 00:07:25.830 --> 00:07:29.029 align:start position:0% solve all the problems so I wonder what does<00:07:26.009> you<00:07:26.180> like<00:07:27.180> impression<00:07:28.139> from<00:07:28.560> customers 00:07:29.029 --> 00:07:29.039 align:start position:0% does you like impression from customers 00:07:29.039 --> 00:07:31.760 align:start position:0% does you like impression from customers what<00:07:29.250> are<00:07:29.370> the<00:07:29.430> early<00:07:29.460> experiences<00:07:30.590> when<00:07:31.590> they 00:07:31.760 --> 00:07:31.770 align:start position:0% what are the early experiences when they 00:07:31.770 --> 00:07:34.490 align:start position:0% what are the early experiences when they take<00:07:31.979> this<00:07:32.720> instead<00:07:33.720> of<00:07:33.780> a<00:07:34.050> bunch<00:07:34.229> of<00:07:34.349> other 00:07:34.490 --> 00:07:34.500 align:start position:0% take this instead of a bunch of other 00:07:34.500 --> 00:07:36.589 align:start position:0% take this instead of a bunch of other things<00:07:34.620> I<00:07:34.949> will<00:07:35.099> do<00:07:35.220> it<00:07:35.340> what<00:07:35.759> what<00:07:36.060> what<00:07:36.479> are 00:07:36.589 --> 00:07:36.599 align:start position:0% things I will do it what what what are 00:07:36.599 --> 00:07:40.459 align:start position:0% things I will do it what what what are the<00:07:36.630> thing<00:07:36.900> I<00:07:37.199> mean<00:07:38.099> like<00:07:38.669> the<00:07:39.110> usually<00:07:40.110> people 00:07:40.459 --> 00:07:40.469 align:start position:0% the thing I mean like the usually people 00:07:40.469 --> 00:07:44.209 align:start position:0% the thing I mean like the usually people don't<00:07:40.979> believe<00:07:41.250> it<00:07:41.430> can<00:07:41.580> be<00:07:41.610> true<00:07:43.009> like<00:07:44.009> your 00:07:44.209 --> 00:07:44.219 align:start position:0% don't believe it can be true like your 00:07:44.219 --> 00:07:46.610 align:start position:0% don't believe it can be true like your queries<00:07:44.490> are<00:07:44.610> isolated<00:07:45.300> like<00:07:45.509> you<00:07:45.690> can 00:07:46.610 --> 00:07:46.620 align:start position:0% queries are isolated like you can 00:07:46.620 --> 00:07:48.290 align:start position:0% queries are isolated like you can dynamically<00:07:47.130> provision<00:07:47.729> where<00:07:47.969> your<00:07:48.120> data 00:07:48.290 --> 00:07:48.300 align:start position:0% dynamically provision where your data 00:07:48.300 --> 00:07:50.270 align:start position:0% dynamically provision where your data lives<00:07:48.659> you<00:07:48.990> can<00:07:49.139> use<00:07:49.320> our<00:07:49.469> server<00:07:49.740> less<00:07:49.979> cloud 00:07:50.270 --> 00:07:50.280 align:start position:0% lives you can use our server less cloud 00:07:50.280 --> 00:07:52.249 align:start position:0% lives you can use our server less cloud and<00:07:50.550> not<00:07:50.669> even<00:07:50.940> think<00:07:51.180> about<00:07:51.419> the<00:07:51.630> backend<00:07:52.080> at 00:07:52.249 --> 00:07:52.259 align:start position:0% and not even think about the backend at 00:07:52.259 --> 00:07:54.680 align:start position:0% and not even think about the backend at all<00:07:52.409> and<00:07:52.860> people<00:07:53.580> have<00:07:53.699> been<00:07:53.820> so<00:07:54.030> badly<00:07:54.300> burned 00:07:54.680 --> 00:07:54.690 align:start position:0% all and people have been so badly burned 00:07:54.690 --> 00:07:58.089 align:start position:0% all and people have been so badly burned in<00:07:55.050> particular<00:07:55.639> by<00:07:56.639> the<00:07:56.669> no<00:07:56.969> SQL<00:07:57.240> movement 00:07:58.089 --> 00:07:58.099 align:start position:0% in particular by the no SQL movement 00:07:58.099 --> 00:08:00.980 align:start position:0% in particular by the no SQL movement that<00:07:59.099> they<00:07:59.610> want<00:07:59.849> to<00:07:59.909> they<00:08:00.270> want<00:08:00.300> us<00:08:00.570> to<00:08:00.750> show 00:08:00.980 --> 00:08:00.990 align:start position:0% that they want to they want us to show 00:08:00.990 --> 00:08:04.520 align:start position:0% that they want to they want us to show them<00:08:01.199> so<00:08:02.449> we<00:08:03.449> have<00:08:03.570> to<00:08:03.690> do<00:08:03.840> a<00:08:03.870> lot<00:08:04.080> of<00:08:04.110> work<00:08:04.349> to 00:08:04.520 --> 00:08:04.530 align:start position:0% them so we have to do a lot of work to 00:08:04.530 --> 00:08:07.070 align:start position:0% them so we have to do a lot of work to prove<00:08:04.800> that<00:08:05.099> the<00:08:05.250> databases<00:08:05.729> sound<00:08:06.659> and 00:08:07.070 --> 00:08:07.080 align:start position:0% prove that the databases sound and 00:08:07.080 --> 00:08:10.399 align:start position:0% prove that the databases sound and secure<00:08:07.560> and<00:08:07.860> performance<00:08:08.729> is<00:08:08.909> good<00:08:09.150> and<00:08:09.539> show 00:08:10.399 --> 00:08:10.409 align:start position:0% secure and performance is good and show 00:08:10.409 --> 00:08:11.990 align:start position:0% secure and performance is good and show that<00:08:10.620> on<00:08:10.770> their<00:08:10.949> data<00:08:11.190> sets<00:08:11.550> like<00:08:11.669> you're 00:08:11.990 --> 00:08:12.000 align:start position:0% that on their data sets like you're 00:08:12.000 --> 00:08:13.939 align:start position:0% that on their data sets like you're important<00:08:12.599> here's<00:08:12.900> the<00:08:13.080> query<00:08:13.319> pattern<00:08:13.770> so 00:08:13.939 --> 00:08:13.949 align:start position:0% important here's the query pattern so 00:08:13.949 --> 00:08:15.200 align:start position:0% important here's the query pattern so you<00:08:14.039> can<00:08:14.130> replicate<00:08:14.310> what<00:08:14.729> you<00:08:14.819> already<00:08:14.940> do 00:08:15.200 --> 00:08:15.210 align:start position:0% you can replicate what you already do 00:08:15.210 --> 00:08:16.850 align:start position:0% you can replicate what you already do but<00:08:15.419> now<00:08:15.539> you<00:08:15.599> get<00:08:15.810> all<00:08:15.960> these<00:08:16.050> scalability 00:08:16.850 --> 00:08:16.860 align:start position:0% but now you get all these scalability 00:08:16.860 --> 00:08:19.399 align:start position:0% but now you get all these scalability isolation<00:08:17.849> performance<00:08:18.599> benefits<00:08:19.080> out<00:08:19.289> of 00:08:19.399 --> 00:08:19.409 align:start position:0% isolation performance benefits out of 00:08:19.409 --> 00:08:25.279 align:start position:0% isolation performance benefits out of the<00:08:19.500> system<00:08:22.039> and<00:08:23.039> people<00:08:23.990> people<00:08:24.990> like<00:08:25.139> the 00:08:25.279 --> 00:08:25.289 align:start position:0% the system and people people like the 00:08:25.289 --> 00:08:28.309 align:start position:0% the system and people people like the interface<00:08:25.590> they're<00:08:26.280> tired<00:08:26.550> of<00:08:26.849> SQL<00:08:27.479> it's 00:08:28.309 --> 00:08:28.319 align:start position:0% interface they're tired of SQL it's 00:08:28.319 --> 00:08:30.649 align:start position:0% interface they're tired of SQL it's unsafe<00:08:28.800> it's<00:08:29.550> hard<00:08:29.819> to<00:08:29.969> reason<00:08:30.150> about<00:08:30.360> the 00:08:30.649 --> 00:08:30.659 align:start position:0% unsafe it's hard to reason about the 00:08:30.659 --> 00:08:33.740 align:start position:0% unsafe it's hard to reason about the performance<00:08:31.199> profile<00:08:32.000> the<00:08:33.000> security<00:08:33.570> model 00:08:33.740 --> 00:08:33.750 align:start position:0% performance profile the security model 00:08:33.750 --> 00:08:35.959 align:start position:0% performance profile the security model doesn't<00:08:34.260> work<00:08:34.560> with<00:08:35.190> the<00:08:35.399> way<00:08:35.520> people<00:08:35.849> write 00:08:35.959 --> 00:08:35.969 align:start position:0% doesn't work with the way people write 00:08:35.969 --> 00:08:39.769 align:start position:0% doesn't work with the way people write modern<00:08:36.360> applications<00:08:37.050> and<00:08:38.419> like<00:08:39.419> the<00:08:39.570> proof 00:08:39.769 --> 00:08:39.779 align:start position:0% modern applications and like the proof 00:08:39.779 --> 00:08:42.230 align:start position:0% modern applications and like the proof of<00:08:39.930> that<00:08:39.990> is<00:08:40.380> people<00:08:40.829> put<00:08:41.130> our<00:08:41.310> Elms<00:08:41.789> in<00:08:41.940> front 00:08:42.230 --> 00:08:42.240 align:start position:0% of that is people put our Elms in front 00:08:42.240 --> 00:08:45.019 align:start position:0% of that is people put our Elms in front of<00:08:42.360> other<00:08:42.890> relational<00:08:43.890> databases<00:08:44.400> for 00:08:45.019 --> 00:08:45.029 align:start position:0% of other relational databases for 00:08:45.029 --> 00:08:47.060 align:start position:0% of other relational databases for operational<00:08:45.779> workloads<00:08:46.260> so<00:08:46.500> not<00:08:46.709> having<00:08:46.980> to 00:08:47.060 --> 00:08:47.070 align:start position:0% operational workloads so not having to 00:08:47.070 --> 00:08:48.030 align:start position:0% operational workloads so not having to deal<00:08:47.250> with<00:08:47.279> that<00:08:47.579> and<00:08:47.730> meaning 00:08:48.030 --> 00:08:48.040 align:start position:0% deal with that and meaning 00:08:48.040 --> 00:08:49.860 align:start position:0% deal with that and meaning directly<00:08:48.610> talk<00:08:48.850> to<00:08:48.880> your<00:08:49.089> database<00:08:49.360> again 00:08:49.860 --> 00:08:49.870 align:start position:0% directly talk to your database again 00:08:49.870 --> 00:08:57.810 align:start position:0% directly talk to your database again it's<00:08:50.699> um<00:08:55.589> what's<00:08:56.589> the<00:08:56.769> word<00:08:56.820> refreshing 00:08:57.810 --> 00:08:57.820 align:start position:0% it's um what's the word refreshing 00:08:57.820 --> 00:09:00.420 align:start position:0% it's um what's the word refreshing mm-hmm 00:09:00.420 --> 00:09:00.430 align:start position:0% mm-hmm 00:09:00.430 --> 00:09:06.180 align:start position:0% mm-hmm so<00:09:01.410> so<00:09:02.410> is<00:09:02.680> it<00:09:02.829> Soho<00:09:03.519> is<00:09:03.670> kind<00:09:03.880> of<00:09:03.910> your<00:09:05.190> go-to 00:09:06.180 --> 00:09:06.190 align:start position:0% so so is it Soho is kind of your go-to 00:09:06.190 --> 00:09:08.639 align:start position:0% so so is it Soho is kind of your go-to markets<00:09:06.639> stage<00:09:07.269> so<00:09:07.779> you<00:09:07.810> know<00:09:07.990> out<00:09:08.170> of<00:09:08.199> stealth 00:09:08.639 --> 00:09:08.649 align:start position:0% markets stage so you know out of stealth 00:09:08.649 --> 00:09:13.530 align:start position:0% markets stage so you know out of stealth or<00:09:10.620> yeah<00:09:11.620> we're<00:09:12.130> out<00:09:12.160> of<00:09:12.459> stealth<00:09:12.730> we<00:09:13.389> have 00:09:13.530 --> 00:09:13.540 align:start position:0% or yeah we're out of stealth we have 00:09:13.540 --> 00:09:16.769 align:start position:0% or yeah we're out of stealth we have beta<00:09:14.050> customers<00:09:14.410> both<00:09:15.360> on-premises<00:09:16.360> and<00:09:16.690> in 00:09:16.769 --> 00:09:16.779 align:start position:0% beta customers both on-premises and in 00:09:16.779 --> 00:09:20.069 align:start position:0% beta customers both on-premises and in the<00:09:16.930> service<00:09:17.470> cloud<00:09:18.389> we're<00:09:19.389> looking<00:09:19.690> for<00:09:19.899> more 00:09:20.069 --> 00:09:20.079 align:start position:0% the service cloud we're looking for more 00:09:20.079 --> 00:09:22.319 align:start position:0% the service cloud we're looking for more and<00:09:20.110> we're<00:09:20.410> preparing<00:09:20.769> for<00:09:21.130> our<00:09:21.190> GA<00:09:21.639> lodge<00:09:21.970> in 00:09:22.319 --> 00:09:22.329 align:start position:0% and we're preparing for our GA lodge in 00:09:22.329 --> 00:09:25.019 align:start position:0% and we're preparing for our GA lodge in the<00:09:22.420> next<00:09:22.690> couple<00:09:22.990> months<00:09:23.610> so<00:09:24.610> if<00:09:24.730> somebody 00:09:25.019 --> 00:09:25.029 align:start position:0% the next couple months so if somebody 00:09:25.029 --> 00:09:27.870 align:start position:0% the next couple months so if somebody wants<00:09:25.269> to<00:09:25.329> try<00:09:25.540> for<00:09:26.380> my<00:09:26.500> Oh<00:09:26.680> hold<00:09:27.399> the<00:09:27.519> go<00:09:27.730> about 00:09:27.870 --> 00:09:27.880 align:start position:0% wants to try for my Oh hold the go about 00:09:27.880 --> 00:09:31.290 align:start position:0% wants to try for my Oh hold the go about it<00:09:28.120> I<00:09:28.329> just<00:09:29.139> go<00:09:29.470> there<00:09:29.500> website<00:09:30.269> click<00:09:31.269> the 00:09:31.290 --> 00:09:31.300 align:start position:0% it I just go there website click the 00:09:31.300 --> 00:09:34.019 align:start position:0% it I just go there website click the request<00:09:31.720> invite<00:09:32.259> link<00:09:32.500> and<00:09:32.829> we'll<00:09:33.730> hook<00:09:33.850> you 00:09:34.019 --> 00:09:34.029 align:start position:0% request invite link and we'll hook you 00:09:34.029 --> 00:09:37.620 align:start position:0% request invite link and we'll hook you up<00:09:34.089> and<00:09:34.480> so<00:09:35.730> can<00:09:36.730> you<00:09:36.880> can<00:09:37.060> you<00:09:37.180> dim<00:09:37.360> what<00:09:37.540> the 00:09:37.620 --> 00:09:37.630 align:start position:0% up and so can you can you dim what the 00:09:37.630 --> 00:09:40.050 align:start position:0% up and so can you can you dim what the center<00:09:37.899> metal<00:09:38.230> like<00:09:38.649> with<00:09:38.860> a<00:09:39.060> realistic 00:09:40.050 --> 00:09:40.060 align:start position:0% center metal like with a realistic 00:09:40.060 --> 00:09:43.199 align:start position:0% center metal like with a realistic application<00:09:40.389> yes<00:09:41.380> all<00:09:42.100> this<00:09:42.250> yeah<00:09:42.790> Chris 00:09:43.199 --> 00:09:43.209 align:start position:0% application yes all this yeah Chris 00:09:43.209 --> 00:09:46.379 align:start position:0% application yes all this yeah Chris Anderson<00:09:43.810> I'm<00:09:44.130> Chris<00:09:45.130> Anderson<00:09:45.639> who<00:09:46.120> was<00:09:46.240> one 00:09:46.379 --> 00:09:46.389 align:start position:0% Anderson I'm Chris Anderson who was one 00:09:46.389 --> 00:09:47.819 align:start position:0% Anderson I'm Chris Anderson who was one of<00:09:46.420> the<00:09:46.480> Couchbase<00:09:46.959> founders<00:09:47.440> joined<00:09:47.709> our 00:09:47.819 --> 00:09:47.829 align:start position:0% of the Couchbase founders joined our 00:09:47.829 --> 00:09:49.860 align:start position:0% of the Couchbase founders joined our team<00:09:47.889> recently<00:09:48.579> yeah<00:09:48.730> he's<00:09:49.420> working<00:09:49.569> on<00:09:49.810> a 00:09:49.860 --> 00:09:49.870 align:start position:0% team recently yeah he's working on a 00:09:49.870 --> 00:09:52.430 align:start position:0% team recently yeah he's working on a surrealist<00:09:50.199> presentation<00:09:51.190> that'll<00:09:51.550> have<00:09:51.699> a 00:09:52.430 --> 00:09:52.440 align:start position:0% surrealist presentation that'll have a 00:09:52.440 --> 00:09:53.639 align:start position:0% surrealist presentation that'll have a do 00:09:53.639 --> 00:09:53.649 align:start position:0% do 00:09:53.649 --> 00:09:55.889 align:start position:0% do aw<00:09:54.100> s<00:09:54.220> lambda<00:09:54.430> executing<00:09:55.209> the<00:09:55.300> computer<00:09:55.779> and 00:09:55.889 --> 00:09:55.899 align:start position:0% aw s lambda executing the computer and 00:09:55.899 --> 00:09:58.590 align:start position:0% aw s lambda executing the computer and phone<00:09:56.170> as<00:09:56.350> the<00:09:56.560> backend<00:09:56.800> and<00:09:57.300> then<00:09:58.300> you<00:09:58.420> have<00:09:58.569> a 00:09:58.590 --> 00:09:58.600 align:start position:0% phone as the backend and then you have a 00:09:58.600 --> 00:10:00.870 align:start position:0% phone as the backend and then you have a fully<00:09:59.079> server<00:09:59.440> less<00:09:59.709> end-to-end<00:10:00.100> stack<00:10:00.579> where 00:10:00.870 --> 00:10:00.880 align:start position:0% fully server less end-to-end stack where 00:10:00.880 --> 00:10:01.889 align:start position:0% fully server less end-to-end stack where you<00:10:01.120> never<00:10:01.329> have<00:10:01.480> to<00:10:01.600> think<00:10:01.630> about 00:10:01.889 --> 00:10:01.899 align:start position:0% you never have to think about 00:10:01.899 --> 00:10:05.579 align:start position:0% you never have to think about provisioning<00:10:02.680> and<00:10:02.889> you<00:10:03.519> can<00:10:03.699> do<00:10:04.290> even<00:10:05.290> a 00:10:05.579 --> 00:10:05.589 align:start position:0% provisioning and you can do even a 00:10:05.589 --> 00:10:08.780 align:start position:0% provisioning and you can do even a globally<00:10:06.490> distributed<00:10:06.870> dynamic<00:10:07.870> application 00:10:08.780 --> 00:10:08.790 align:start position:0% globally distributed dynamic application 00:10:08.790 --> 00:10:11.519 align:start position:0% globally distributed dynamic application you<00:10:09.790> know<00:10:09.910> fully<00:10:10.149> service<00:10:10.690> model<00:10:11.050> I<00:10:11.260> will 00:10:11.519 --> 00:10:11.529 align:start position:0% you know fully service model I will 00:10:11.529 --> 00:10:13.079 align:start position:0% you know fully service model I will claim<00:10:11.709> dibs<00:10:11.980> on<00:10:12.130> this<00:10:12.279> presentation<00:10:12.910> once 00:10:13.079 --> 00:10:13.089 align:start position:0% claim dibs on this presentation once 00:10:13.089 --> 00:10:16.530 align:start position:0% claim dibs on this presentation once already<00:10:13.329> so<00:10:13.480> it<00:10:13.779> can<00:10:13.930> show<00:10:14.940> it's<00:10:15.940> also<00:10:16.120> sounds 00:10:16.530 --> 00:10:16.540 align:start position:0% already so it can show it's also sounds 00:10:16.540 --> 00:10:17.750 align:start position:0% already so it can show it's also sounds a<00:10:16.600> little<00:10:16.660> exciting<00:10:17.110> you<00:10:17.199> know<00:10:17.230> it's<00:10:17.410> kind<00:10:17.589> of 00:10:17.750 --> 00:10:17.760 align:start position:0% a little exciting you know it's kind of 00:10:17.760 --> 00:10:21.689 align:start position:0% a little exciting you know it's kind of it<00:10:18.760> makes<00:10:19.149> a<00:10:19.389> lot<00:10:19.480> of<00:10:19.510> sense<00:10:19.810> and<00:10:20.709> yeah<00:10:21.579> I<00:10:21.610> mean 00:10:21.689 --> 00:10:21.699 align:start position:0% it makes a lot of sense and yeah I mean 00:10:21.699 --> 00:10:23.579 align:start position:0% it makes a lot of sense and yeah I mean like<00:10:21.970> I<00:10:22.209> can't<00:10:22.420> wait<00:10:22.540> to<00:10:22.720> see<00:10:22.870> it<00:10:23.019> so<00:10:23.319> you<00:10:23.350> know 00:10:23.579 --> 00:10:23.589 align:start position:0% like I can't wait to see it so you know 00:10:23.589 --> 00:10:26.360 align:start position:0% like I can't wait to see it so you know thank<00:10:24.310> you<00:10:24.370> very<00:10:24.459> much<00:10:24.639> for<00:10:24.850> inviting<00:10:25.089> us 00:10:26.360 --> 00:10:26.370 align:start position:0% thank you very much for inviting us 00:10:26.370 --> 00:10:28.379 align:start position:0% thank you very much for inviting us looking<00:10:27.370> forward<00:10:27.639> to<00:10:27.760> playing<00:10:28.000> more<00:10:28.240> with 00:10:28.379 --> 00:10:28.389 align:start position:0% looking forward to playing more with 00:10:28.389 --> 00:10:29.579 align:start position:0% looking forward to playing more with this<00:10:28.510> yeah<00:10:28.779> are<00:10:29.260> you 00:10:29.579 --> 00:10:29.589 align:start position:0% this yeah are you 00:10:29.589 --> 00:10:30.870 align:start position:0% this yeah are you once<00:10:29.800> we<00:10:29.920> play<00:10:30.069> more<00:10:30.250> of<00:10:30.399> this<00:10:30.490> we'll<00:10:30.670> come 00:10:30.870 --> 00:10:30.880 align:start position:0% once we play more of this we'll come 00:10:30.880 --> 00:10:33.210 align:start position:0% once we play more of this we'll come back<00:10:31.000> an<00:10:31.120> eskimo<00:10:31.420> questions<00:10:32.040> thank<00:10:33.040> you 00:10:33.210 --> 00:10:33.220 align:start position:0% back an eskimo questions thank you 00:10:33.220 --> 00:10:37.019 align:start position:0% back an eskimo questions thank you thanks<00:10:34.000> really<00:10:34.630> appreciated