WEBVTT Kind: captions Language: en 00:00:09.870 --> 00:00:13.629 align:start position:0% [Music] 00:00:13.629 --> 00:00:13.639 align:start position:0% 00:00:13.639 --> 00:00:15.869 align:start position:0% hello<00:00:13.839> everybody<00:00:14.400> I'm<00:00:14.519> Alexi<00:00:14.879> kov<00:00:15.679> uh<00:00:15.799> the 00:00:15.869 --> 00:00:15.879 align:start position:0% hello everybody I'm Alexi kov uh the 00:00:15.879 --> 00:00:17.910 align:start position:0% hello everybody I'm Alexi kov uh the organizer<00:00:16.320> of<00:00:16.440> SF<00:00:16.760> spark<00:00:17.119> here<00:00:17.400> on<00:00:17.560> location 00:00:17.910 --> 00:00:17.920 align:start position:0% organizer of SF spark here on location 00:00:17.920 --> 00:00:20.470 align:start position:0% organizer of SF spark here on location at<00:00:18.039> splice<00:00:18.560> machine<00:00:19.560> and<00:00:19.760> the<00:00:19.880> main<00:00:20.080> talk 00:00:20.470 --> 00:00:20.480 align:start position:0% at splice machine and the main talk 00:00:20.480 --> 00:00:23.750 align:start position:0% at splice machine and the main talk tonight<00:00:20.880> will<00:00:21.119> be<00:00:21.840> uh<00:00:22.039> about<00:00:22.960> uh<00:00:23.080> aach<00:00:23.439> ignite 00:00:23.750 --> 00:00:23.760 align:start position:0% tonight will be uh about uh aach ignite 00:00:23.760 --> 00:00:27.990 align:start position:0% tonight will be uh about uh aach ignite and<00:00:24.359> G<00:00:24.680> gain<00:00:25.000> and<00:00:25.279> we<00:00:25.519> have<00:00:25.800> with<00:00:25.960> us<00:00:26.840> uhan<00:00:27.840> who 00:00:27.990 --> 00:00:28.000 align:start position:0% and G gain and we have with us uhan who 00:00:28.000 --> 00:00:31.269 align:start position:0% and G gain and we have with us uhan who is<00:00:28.240> a<00:00:28.439> chief<00:00:28.640> prot<00:00:29.039> officer<00:00:29.759> uh<00:00:30.199> of<00:00:30.679> gri<00:00:30.960> gain 00:00:31.269 --> 00:00:31.279 align:start position:0% is a chief prot officer uh of gri gain 00:00:31.279 --> 00:00:33.630 align:start position:0% is a chief prot officer uh of gri gain also<00:00:31.519> PMC<00:00:31.880> of<00:00:32.040> Papik<00:00:32.439> Knight<00:00:32.680> and<00:00:32.880> he's<00:00:33.079> also 00:00:33.630 --> 00:00:33.640 align:start position:0% also PMC of Papik Knight and he's also 00:00:33.640 --> 00:00:35.790 align:start position:0% also PMC of Papik Knight and he's also co-founder<00:00:34.079> of<00:00:34.200> G<00:00:34.440> gain<00:00:35.000> great<00:00:35.360> it's<00:00:35.520> great<00:00:35.680> to 00:00:35.790 --> 00:00:35.800 align:start position:0% co-founder of G gain great it's great to 00:00:35.800 --> 00:00:37.670 align:start position:0% co-founder of G gain great it's great to have<00:00:35.920> you<00:00:36.040> with<00:00:36.200> us<00:00:36.680> thank<00:00:36.840> you<00:00:37.120> thank<00:00:37.280> you 00:00:37.670 --> 00:00:37.680 align:start position:0% have you with us thank you thank you 00:00:37.680 --> 00:00:39.950 align:start position:0% have you with us thank you thank you great<00:00:38.399> tell<00:00:38.520> us<00:00:38.640> a<00:00:38.719> little<00:00:38.920> bit<00:00:39.440> uh<00:00:39.640> how<00:00:39.800> did 00:00:39.950 --> 00:00:39.960 align:start position:0% great tell us a little bit uh how did 00:00:39.960 --> 00:00:42.150 align:start position:0% great tell us a little bit uh how did you<00:00:40.360> come<00:00:40.520> up<00:00:40.680> with<00:00:40.840> this<00:00:41.039> idea<00:00:41.360> of<00:00:41.559> gri<00:00:41.840> gain 00:00:42.150 --> 00:00:42.160 align:start position:0% you come up with this idea of gri gain 00:00:42.160 --> 00:00:43.389 align:start position:0% you come up with this idea of gri gain it's<00:00:42.600> uh<00:00:42.719> it's<00:00:42.920> pretty<00:00:43.120> interesting 00:00:43.389 --> 00:00:43.399 align:start position:0% it's uh it's pretty interesting 00:00:43.399 --> 00:00:45.709 align:start position:0% it's uh it's pretty interesting technology<00:00:43.879> what<00:00:44.000> it<00:00:44.160> is<00:00:44.800> you<00:00:44.960> know<00:00:45.480> how<00:00:45.600> it 00:00:45.709 --> 00:00:45.719 align:start position:0% technology what it is you know how it 00:00:45.719 --> 00:00:49.990 align:start position:0% technology what it is you know how it came<00:00:45.840> to<00:00:46.039> be<00:00:46.440> where<00:00:46.559> it<00:00:46.640> is<00:00:47.239> now<00:00:48.239> well<00:00:49.000> uh 00:00:49.990 --> 00:00:50.000 align:start position:0% came to be where it is now well uh 00:00:50.000 --> 00:00:52.709 align:start position:0% came to be where it is now well uh Nikita<00:00:50.640> Nikita<00:00:51.079> my<00:00:51.239> co-founder<00:00:52.000> like<00:00:52.359> the<00:00:52.480> guy 00:00:52.709 --> 00:00:52.719 align:start position:0% Nikita Nikita my co-founder like the guy 00:00:52.719 --> 00:00:55.830 align:start position:0% Nikita Nikita my co-founder like the guy confounded<00:00:53.239> with<00:00:53.399> and<00:00:53.640> I<00:00:54.160> we<00:00:54.879> had<00:00:55.079> the<00:00:55.280> idea<00:00:55.640> we 00:00:55.830 --> 00:00:55.840 align:start position:0% confounded with and I we had the idea we 00:00:55.840 --> 00:00:57.910 align:start position:0% confounded with and I we had the idea we always<00:00:56.520> uh<00:00:56.719> were<00:00:57.000> part 00:00:57.910 --> 00:00:57.920 align:start position:0% always uh were part 00:00:57.920 --> 00:01:00.630 align:start position:0% always uh were part of<00:00:58.920> distributed<00:00:59.480> computing<00:01:00.039> and<00:01:00.160> we<00:01:00.399> always 00:01:00.630 --> 00:01:00.640 align:start position:0% of distributed computing and we always 00:01:00.640 --> 00:01:03.670 align:start position:0% of distributed computing and we always were<00:01:00.879> working<00:01:01.199> in<00:01:01.680> all<00:01:02.000> those<00:01:03.000> projects<00:01:03.519> that 00:01:03.670 --> 00:01:03.680 align:start position:0% were working in all those projects that 00:01:03.680 --> 00:01:07.109 align:start position:0% were working in all those projects that required<00:01:04.600> big<00:01:04.839> scale<00:01:05.280> and 00:01:07.109 --> 00:01:07.119 align:start position:0% required big scale and 00:01:07.119 --> 00:01:10.070 align:start position:0% required big scale and lots<00:01:08.119> lots<00:01:08.479> of<00:01:08.680> fance<00:01:09.280> and 00:01:10.070 --> 00:01:10.080 align:start position:0% lots lots of fance and 00:01:10.080 --> 00:01:13.190 align:start position:0% lots lots of fance and scalability<00:01:11.080> so<00:01:11.600> essentially<00:01:12.600> when<00:01:12.799> we<00:01:12.960> just 00:01:13.190 --> 00:01:13.200 align:start position:0% scalability so essentially when we just 00:01:13.200 --> 00:01:15.749 align:start position:0% scalability so essentially when we just started<00:01:13.799> I<00:01:13.880> mean<00:01:14.159> the<00:01:14.320> market<00:01:14.680> was<00:01:14.880> not<00:01:15.280> as 00:01:15.749 --> 00:01:15.759 align:start position:0% started I mean the market was not as 00:01:15.759 --> 00:01:18.550 align:start position:0% started I mean the market was not as populated<00:01:16.560> and<00:01:17.040> saturated<00:01:17.720> if<00:01:17.799> you<00:01:17.960> will<00:01:18.360> as 00:01:18.550 --> 00:01:18.560 align:start position:0% populated and saturated if you will as 00:01:18.560 --> 00:01:20.749 align:start position:0% populated and saturated if you will as it<00:01:18.799> it<00:01:18.920> is<00:01:19.040> today<00:01:19.799> at<00:01:19.960> that<00:01:20.119> time<00:01:20.320> we<00:01:20.479> had 00:01:20.749 --> 00:01:20.759 align:start position:0% it it is today at that time we had 00:01:20.759 --> 00:01:24.350 align:start position:0% it it is today at that time we had Globus<00:01:21.520> we<00:01:21.759> had<00:01:22.400> Sun<00:01:22.759> engine<00:01:23.159> Sun<00:01:23.479> GD<00:01:23.720> engine 00:01:24.350 --> 00:01:24.360 align:start position:0% Globus we had Sun engine Sun GD engine 00:01:24.360 --> 00:01:28.190 align:start position:0% Globus we had Sun engine Sun GD engine and<00:01:24.560> probably<00:01:24.840> a<00:01:24.920> couple<00:01:25.240> more<00:01:26.240> and<00:01:27.000> um<00:01:28.000> we 00:01:28.190 --> 00:01:28.200 align:start position:0% and probably a couple more and um we 00:01:28.200 --> 00:01:30.910 align:start position:0% and probably a couple more and um we just<00:01:28.720> uh<00:01:29.159> and<00:01:29.280> it<00:01:29.400> was<00:01:29.560> hard<00:01:30.159> it<00:01:30.280> was<00:01:30.479> hard<00:01:30.720> to 00:01:30.910 --> 00:01:30.920 align:start position:0% just uh and it was hard it was hard to 00:01:30.920 --> 00:01:34.069 align:start position:0% just uh and it was hard it was hard to use<00:01:31.159> grid<00:01:31.720> Computing<00:01:32.720> actually<00:01:33.079> to<00:01:33.439> spin<00:01:33.799> off 00:01:34.069 --> 00:01:34.079 align:start position:0% use grid Computing actually to spin off 00:01:34.079 --> 00:01:36.670 align:start position:0% use grid Computing actually to spin off a<00:01:34.439> project<00:01:34.799> on<00:01:35.040> lobus<00:01:36.000> probably<00:01:36.320> would<00:01:36.479> take 00:01:36.670 --> 00:01:36.680 align:start position:0% a project on lobus probably would take 00:01:36.680 --> 00:01:41.310 align:start position:0% a project on lobus probably would take you<00:01:37.399> maybe<00:01:38.399> several<00:01:38.840> days<00:01:39.320> M<00:01:40.000> so<00:01:40.479> Nikita<00:01:40.880> and<00:01:41.000> I 00:01:41.310 --> 00:01:41.320 align:start position:0% you maybe several days M so Nikita and I 00:01:41.320 --> 00:01:43.830 align:start position:0% you maybe several days M so Nikita and I we<00:01:41.560> had<00:01:41.759> this<00:01:41.960> idea<00:01:42.320> of<00:01:42.840> grid<00:01:43.159> Computing<00:01:43.600> Made 00:01:43.830 --> 00:01:43.840 align:start position:0% we had this idea of grid Computing Made 00:01:43.840 --> 00:01:47.310 align:start position:0% we had this idea of grid Computing Made Simple<00:01:44.840> and<00:01:45.280> that's<00:01:45.520> when<00:01:46.399> we<00:01:46.600> started<00:01:47.040> grid 00:01:47.310 --> 00:01:47.320 align:start position:0% Simple and that's when we started grid 00:01:47.320 --> 00:01:49.910 align:start position:0% Simple and that's when we started grid gain<00:01:47.520> as<00:01:47.640> an<00:01:47.759> open<00:01:48.040> source<00:01:48.399> project<00:01:49.119> and<00:01:49.799> the 00:01:49.910 --> 00:01:49.920 align:start position:0% gain as an open source project and the 00:01:49.920 --> 00:01:51.830 align:start position:0% gain as an open source project and the whole<00:01:50.159> idea<00:01:50.520> was<00:01:50.880> that<00:01:51.119> you<00:01:51.399> you<00:01:51.479> should<00:01:51.719> be 00:01:51.830 --> 00:01:51.840 align:start position:0% whole idea was that you you should be 00:01:51.840 --> 00:01:53.670 align:start position:0% whole idea was that you you should be able<00:01:52.040> to<00:01:52.200> start<00:01:52.520> Computing<00:01:52.960> on<00:01:53.079> a<00:01:53.200> clustered 00:01:53.670 --> 00:01:53.680 align:start position:0% able to start Computing on a clustered 00:01:53.680 --> 00:01:55.990 align:start position:0% able to start Computing on a clustered environment<00:01:54.159> in<00:01:54.240> a<00:01:54.320> full<00:01:54.560> hor<00:01:54.960> fashion<00:01:55.680> within 00:01:55.990 --> 00:01:56.000 align:start position:0% environment in a full hor fashion within 00:01:56.000 --> 00:01:58.190 align:start position:0% environment in a full hor fashion within 5<00:01:56.159> minutes<00:01:56.560> what<00:01:56.719> year<00:01:56.920> was 00:01:58.190 --> 00:01:58.200 align:start position:0% 5 minutes what year was 00:01:58.200 --> 00:02:00.950 align:start position:0% 5 minutes what year was that<00:01:59.200> I'm<00:01:59.360> not<00:01:59.560> going<00:01:59.640> to<00:02:00.320> give<00:02:00.439> you<00:02:00.759> it's 00:02:00.950 --> 00:02:00.960 align:start position:0% that I'm not going to give you it's 00:02:00.960 --> 00:02:02.990 align:start position:0% that I'm not going to give you it's probably<00:02:01.200> 7even<00:02:01.439> eight<00:02:01.680> years<00:02:01.880> ago<00:02:02.479> okay<00:02:02.840> so 00:02:02.990 --> 00:02:03.000 align:start position:0% probably 7even eight years ago okay so 00:02:03.000 --> 00:02:05.350 align:start position:0% probably 7even eight years ago okay so that's<00:02:03.200> before<00:02:03.560> spark<00:02:04.200> yeah<00:02:04.399> but<00:02:04.920> uh<00:02:05.200> yeah 00:02:05.350 --> 00:02:05.360 align:start position:0% that's before spark yeah but uh yeah 00:02:05.360 --> 00:02:07.029 align:start position:0% that's before spark yeah but uh yeah that's<00:02:05.560> before<00:02:05.960> spark<00:02:06.280> and<00:02:06.399> we<00:02:06.520> started<00:02:06.840> out 00:02:07.029 --> 00:02:07.039 align:start position:0% that's before spark and we started out 00:02:07.039 --> 00:02:09.710 align:start position:0% that's before spark and we started out in<00:02:07.159> a<00:02:07.320> garage<00:02:07.840> kind<00:02:08.039> of<00:02:08.200> mode<00:02:08.720> and<00:02:09.080> uh<00:02:09.440> we're 00:02:09.710 --> 00:02:09.720 align:start position:0% in a garage kind of mode and uh we're 00:02:09.720 --> 00:02:13.270 align:start position:0% in a garage kind of mode and uh we're working<00:02:10.479> uh<00:02:10.720> after<00:02:11.360> after<00:02:11.640> working<00:02:12.080> hours<00:02:13.080> and 00:02:13.270 --> 00:02:13.280 align:start position:0% working uh after after working hours and 00:02:13.280 --> 00:02:15.430 align:start position:0% working uh after after working hours and then<00:02:13.520> at<00:02:14.200> certain<00:02:14.560> point<00:02:14.760> we<00:02:14.920> land<00:02:15.160> at<00:02:15.280> a 00:02:15.430 --> 00:02:15.440 align:start position:0% then at certain point we land at a 00:02:15.440 --> 00:02:18.070 align:start position:0% then at certain point we land at a Consulting<00:02:15.959> project<00:02:16.400> which<00:02:16.519> we<00:02:16.720> used<00:02:17.280> for 00:02:18.070 --> 00:02:18.080 align:start position:0% Consulting project which we used for 00:02:18.080 --> 00:02:20.830 align:start position:0% Consulting project which we used for sponsoring<00:02:19.080> a<00:02:19.200> team<00:02:19.800> in<00:02:20.040> Russia<00:02:20.400> that<00:02:20.560> helped 00:02:20.830 --> 00:02:20.840 align:start position:0% sponsoring a team in Russia that helped 00:02:20.840 --> 00:02:23.190 align:start position:0% sponsoring a team in Russia that helped us<00:02:21.040> develop<00:02:21.760> grid<00:02:22.080> game<00:02:22.360> so<00:02:22.560> that's<00:02:22.760> how<00:02:22.920> grid 00:02:23.190 --> 00:02:23.200 align:start position:0% us develop grid game so that's how grid 00:02:23.200 --> 00:02:25.589 align:start position:0% us develop grid game so that's how grid game<00:02:23.879> came<00:02:24.040> out<00:02:24.239> to<00:02:24.560> to<00:02:24.680> be<00:02:24.879> it<00:02:25.000> started<00:02:25.319> out<00:02:25.480> as 00:02:25.589 --> 00:02:25.599 align:start position:0% game came out to to be it started out as 00:02:25.599 --> 00:02:28.830 align:start position:0% game came out to to be it started out as a<00:02:25.720> computer<00:02:26.120> grid<00:02:26.560> mhm<00:02:27.280> and<00:02:27.760> uh<00:02:27.920> it<00:02:28.120> actually 00:02:28.830 --> 00:02:28.840 align:start position:0% a computer grid mhm and uh it actually 00:02:28.840 --> 00:02:32.030 align:start position:0% a computer grid mhm and uh it actually uh<00:02:29.239> became<00:02:29.519> pretty<00:02:30.040> popular<00:02:30.760> from<00:02:30.920> the<00:02:31.120> GetGo 00:02:32.030 --> 00:02:32.040 align:start position:0% uh became pretty popular from the GetGo 00:02:32.040 --> 00:02:35.509 align:start position:0% uh became pretty popular from the GetGo and<00:02:32.840> as<00:02:33.239> we<00:02:33.480> progress<00:02:33.959> we<00:02:34.120> figured<00:02:34.599> that<00:02:35.160> jazz 00:02:35.509 --> 00:02:35.519 align:start position:0% and as we progress we figured that jazz 00:02:35.519 --> 00:02:36.910 align:start position:0% and as we progress we figured that jazz computer<00:02:35.879> is<00:02:35.959> not<00:02:36.120> going<00:02:36.200> to<00:02:36.319> be<00:02:36.480> enough<00:02:36.680> so<00:02:36.800> we 00:02:36.910 --> 00:02:36.920 align:start position:0% computer is not going to be enough so we 00:02:36.920 --> 00:02:40.670 align:start position:0% computer is not going to be enough so we added<00:02:37.160> the<00:02:37.360> data<00:02:37.599> site<00:02:38.000> MH<00:02:38.760> and<00:02:39.280> then<00:02:40.280> we<00:02:40.440> had<00:02:40.599> a 00:02:40.670 --> 00:02:40.680 align:start position:0% added the data site MH and then we had a 00:02:40.680 --> 00:02:42.790 align:start position:0% added the data site MH and then we had a few<00:02:40.840> changes<00:02:41.159> in<00:02:41.239> the<00:02:41.400> company<00:02:41.800> and<00:02:42.040> then<00:02:42.519> we 00:02:42.790 --> 00:02:42.800 align:start position:0% few changes in the company and then we 00:02:42.800 --> 00:02:45.830 align:start position:0% few changes in the company and then we donated<00:02:43.760> our<00:02:44.080> code<00:02:44.319> to<00:02:44.519> Apache<00:02:44.920> ignite<00:02:45.440> and 00:02:45.830 --> 00:02:45.840 align:start position:0% donated our code to Apache ignite and 00:02:45.840 --> 00:02:48.710 align:start position:0% donated our code to Apache ignite and here<00:02:46.200> where<00:02:47.120> Co<00:02:47.480> so<00:02:47.680> so<00:02:48.239> you<00:02:48.360> take<00:02:48.519> GRE 00:02:48.710 --> 00:02:48.720 align:start position:0% here where Co so so you take GRE 00:02:48.720 --> 00:02:50.190 align:start position:0% here where Co so so you take GRE Computing<00:02:49.120> and<00:02:49.280> so<00:02:49.400> you<00:02:49.519> mentioned<00:02:49.959> sub 00:02:50.190 --> 00:02:50.200 align:start position:0% Computing and so you mentioned sub 00:02:50.200 --> 00:02:52.149 align:start position:0% Computing and so you mentioned sub systems<00:02:50.519> I<00:02:50.599> think<00:02:50.760> this<00:02:50.879> is<00:02:51.040> not<00:02:51.280> kind<00:02:51.400> of<00:02:51.599> the 00:02:52.149 --> 00:02:52.159 align:start position:0% systems I think this is not kind of the 00:02:52.159 --> 00:02:54.869 align:start position:0% systems I think this is not kind of the traditional<00:02:53.000> distributed<00:02:53.640> systems<00:02:54.640> kind<00:02:54.760> of 00:02:54.869 --> 00:02:54.879 align:start position:0% traditional distributed systems kind of 00:02:54.879 --> 00:02:57.229 align:start position:0% traditional distributed systems kind of in<00:02:55.040> the<00:02:56.040> uh<00:02:56.239> area<00:02:56.560> right<00:02:56.680> so<00:02:56.800> can<00:02:56.920> you<00:02:57.040> talk<00:02:57.159> a 00:02:57.229 --> 00:02:57.239 align:start position:0% in the uh area right so can you talk a 00:02:57.239 --> 00:02:59.229 align:start position:0% in the uh area right so can you talk a little<00:02:57.360> bit<00:02:57.480> about<00:02:57.680> grid<00:02:57.879> Computing<00:02:58.519> area<00:02:59.040> as 00:02:59.229 --> 00:02:59.239 align:start position:0% little bit about grid Computing area as 00:02:59.239 --> 00:03:02.270 align:start position:0% little bit about grid Computing area as kind<00:02:59.360> of<00:02:59.480> preced<00:02:59.959> in<00:03:00.519> uh<00:03:00.720> Hadoop<00:03:01.519> and<00:03:01.879> what 00:03:02.270 --> 00:03:02.280 align:start position:0% kind of preced in uh Hadoop and what 00:03:02.280 --> 00:03:04.110 align:start position:0% kind of preced in uh Hadoop and what what<00:03:02.400> is<00:03:02.560> specific<00:03:03.280> what<00:03:03.440> are<00:03:03.599> the<00:03:03.720> customers 00:03:04.110 --> 00:03:04.120 align:start position:0% what is specific what are the customers 00:03:04.120 --> 00:03:06.949 align:start position:0% what is specific what are the customers of<00:03:04.360> this<00:03:05.159> uh<00:03:05.280> you<00:03:05.360> know<00:03:05.519> what<00:03:05.640> is<00:03:05.760> mostly<00:03:06.040> used 00:03:06.949 --> 00:03:06.959 align:start position:0% of this uh you know what is mostly used 00:03:06.959 --> 00:03:11.030 align:start position:0% of this uh you know what is mostly used well<00:03:07.680> U<00:03:08.680> from<00:03:08.959> the<00:03:09.360> uh<00:03:10.120> generally<00:03:10.560> speaking<00:03:11.000> I 00:03:11.030 --> 00:03:11.040 align:start position:0% well U from the uh generally speaking I 00:03:11.040 --> 00:03:13.430 align:start position:0% well U from the uh generally speaking I mean<00:03:11.400> Hadoop<00:03:11.799> and<00:03:11.920> grid<00:03:12.159> gain<00:03:13.000> are<00:03:13.159> designed 00:03:13.430 --> 00:03:13.440 align:start position:0% mean Hadoop and grid gain are designed 00:03:13.440 --> 00:03:15.390 align:start position:0% mean Hadoop and grid gain are designed to<00:03:13.560> solve<00:03:13.840> different<00:03:14.080> types<00:03:14.280> of<00:03:14.480> problems 00:03:15.390 --> 00:03:15.400 align:start position:0% to solve different types of problems 00:03:15.400 --> 00:03:18.990 align:start position:0% to solve different types of problems Hadoop<00:03:16.280> initially<00:03:17.280> uh<00:03:17.519> was<00:03:17.720> created<00:03:18.120> to<00:03:18.440> take 00:03:18.990 --> 00:03:19.000 align:start position:0% Hadoop initially uh was created to take 00:03:19.000 --> 00:03:21.789 align:start position:0% Hadoop initially uh was created to take uh<00:03:19.879> it's<00:03:19.959> a<00:03:20.120> batch<00:03:20.360> oriented<00:03:21.080> system<00:03:21.480> so 00:03:21.789 --> 00:03:21.799 align:start position:0% uh it's a batch oriented system so 00:03:21.799 --> 00:03:24.470 align:start position:0% uh it's a batch oriented system so there's<00:03:22.159> it's<00:03:22.319> very<00:03:22.519> batchy<00:03:23.280> and<00:03:24.280> uh 00:03:24.470 --> 00:03:24.480 align:start position:0% there's it's very batchy and uh 00:03:24.480 --> 00:03:26.190 align:start position:0% there's it's very batchy and uh essentially<00:03:25.080> if<00:03:25.200> you<00:03:25.360> have<00:03:25.480> a<00:03:25.720> problem<00:03:26.040> that 00:03:26.190 --> 00:03:26.200 align:start position:0% essentially if you have a problem that 00:03:26.200 --> 00:03:28.390 align:start position:0% essentially if you have a problem that takes<00:03:26.400> an<00:03:26.519> hour<00:03:26.840> maybe<00:03:27.040> a<00:03:27.120> couple<00:03:27.400> hours<00:03:28.239> and 00:03:28.390 --> 00:03:28.400 align:start position:0% takes an hour maybe a couple hours and 00:03:28.400 --> 00:03:31.550 align:start position:0% takes an hour maybe a couple hours and you<00:03:28.519> use<00:03:28.720> map<00:03:28.959> Ru<00:03:29.280> you<00:03:29.400> may<00:03:29.879> be<00:03:30.000> able<00:03:30.560> to 00:03:31.550 --> 00:03:31.560 align:start position:0% you use map Ru you may be able to 00:03:31.560 --> 00:03:34.030 align:start position:0% you use map Ru you may be able to complete<00:03:31.879> it<00:03:32.080> in<00:03:32.239> maybe<00:03:32.560> 30<00:03:33.120> 30<00:03:33.439> minutes<00:03:33.720> or<00:03:33.840> so 00:03:34.030 --> 00:03:34.040 align:start position:0% complete it in maybe 30 30 minutes or so 00:03:34.040 --> 00:03:35.309 align:start position:0% complete it in maybe 30 30 minutes or so so<00:03:34.200> it<00:03:34.360> actually<00:03:34.760> provides<00:03:35.159> good 00:03:35.309 --> 00:03:35.319 align:start position:0% so it actually provides good 00:03:35.319 --> 00:03:37.509 align:start position:0% so it actually provides good acceleration<00:03:35.879> for<00:03:36.480> those<00:03:36.680> batch<00:03:37.000> oriented 00:03:37.509 --> 00:03:37.519 align:start position:0% acceleration for those batch oriented 00:03:37.519 --> 00:03:40.390 align:start position:0% acceleration for those batch oriented offline<00:03:38.040> systems<00:03:38.599> that<00:03:39.159> need<00:03:39.720> to<00:03:39.920> Crunch<00:03:40.200> on<00:03:40.319> a 00:03:40.390 --> 00:03:40.400 align:start position:0% offline systems that need to Crunch on a 00:03:40.400 --> 00:03:43.670 align:start position:0% offline systems that need to Crunch on a lot<00:03:40.560> of<00:03:40.720> data<00:03:41.439> our<00:03:41.680> Focus<00:03:42.120> was<00:03:42.319> to<00:03:42.560> take<00:03:43.080> a<00:03:43.280> job 00:03:43.670 --> 00:03:43.680 align:start position:0% lot of data our Focus was to take a job 00:03:43.680 --> 00:03:45.830 align:start position:0% lot of data our Focus was to take a job that<00:03:43.879> maybe<00:03:44.159> takes<00:03:44.360> a<00:03:44.480> few<00:03:44.760> seconds<00:03:45.480> and 00:03:45.830 --> 00:03:45.840 align:start position:0% that maybe takes a few seconds and 00:03:45.840 --> 00:03:49.110 align:start position:0% that maybe takes a few seconds and execute<00:03:46.200> it<00:03:46.400> in<00:03:46.680> milliseconds<00:03:47.560> MH<00:03:48.159> so<00:03:48.680> it's<00:03:48.840> a 00:03:49.110 --> 00:03:49.120 align:start position:0% execute it in milliseconds MH so it's a 00:03:49.120 --> 00:03:50.949 align:start position:0% execute it in milliseconds MH so it's a real<00:03:49.439> time<00:03:49.720> from<00:03:49.920> the<00:03:50.080> GetGo<00:03:50.439> we<00:03:50.560> designed<00:03:50.799> it 00:03:50.949 --> 00:03:50.959 align:start position:0% real time from the GetGo we designed it 00:03:50.959 --> 00:03:53.750 align:start position:0% real time from the GetGo we designed it as<00:03:51.040> a<00:03:51.200> real<00:03:51.480> time<00:03:51.760> very<00:03:52.040> responsive<00:03:52.599> system<00:03:53.120> M 00:03:53.750 --> 00:03:53.760 align:start position:0% as a real time very responsive system M 00:03:53.760 --> 00:03:55.309 align:start position:0% as a real time very responsive system M uh<00:03:54.079> that 00:03:55.309 --> 00:03:55.319 align:start position:0% uh that 00:03:55.319 --> 00:03:59.110 align:start position:0% uh that uh<00:03:56.319> uh<00:03:56.920> was<00:03:57.120> meant<00:03:57.439> to<00:03:57.599> perform<00:03:58.439> and<00:03:58.680> was<00:03:58.879> meant 00:03:59.110 --> 00:03:59.120 align:start position:0% uh uh was meant to perform and was meant 00:03:59.120 --> 00:04:01.190 align:start position:0% uh uh was meant to perform and was meant to<00:03:59.239> scale<00:04:00.000> so<00:04:00.319> that's<00:04:00.519> where<00:04:00.720> would<00:04:00.879> be<00:04:01.040> the 00:04:01.190 --> 00:04:01.200 align:start position:0% to scale so that's where would be the 00:04:01.200 --> 00:04:03.990 align:start position:0% to scale so that's where would be the difference<00:04:01.560> so<00:04:02.120> and<00:04:02.720> all<00:04:02.840> the<00:04:03.000> use<00:04:03.280> cases<00:04:03.680> that 00:04:03.990 --> 00:04:04.000 align:start position:0% difference so and all the use cases that 00:04:04.000 --> 00:04:06.750 align:start position:0% difference so and all the use cases that I'm<00:04:04.159> seeing<00:04:04.480> today<00:04:05.239> in<00:04:05.400> Apache<00:04:05.799> ignite<00:04:06.640> there 00:04:06.750 --> 00:04:06.760 align:start position:0% I'm seeing today in Apache ignite there 00:04:06.760 --> 00:04:09.750 align:start position:0% I'm seeing today in Apache ignite there is<00:04:06.879> a<00:04:07.040> lot<00:04:07.159> of<00:04:07.280> use<00:04:07.560> cases<00:04:08.120> that<00:04:08.920> are<00:04:09.439> that<00:04:09.519> are 00:04:09.750 --> 00:04:09.760 align:start position:0% is a lot of use cases that are that are 00:04:09.760 --> 00:04:11.869 align:start position:0% is a lot of use cases that are that are transactional<00:04:10.560> and<00:04:10.760> that<00:04:10.920> require<00:04:11.400> those 00:04:11.869 --> 00:04:11.879 align:start position:0% transactional and that require those 00:04:11.879 --> 00:04:13.990 align:start position:0% transactional and that require those hundreds<00:04:12.239> of<00:04:12.400> thousands<00:04:12.799> of<00:04:13.280> uh<00:04:13.439> transactions 00:04:13.990 --> 00:04:14.000 align:start position:0% hundreds of thousands of uh transactions 00:04:14.000 --> 00:04:16.069 align:start position:0% hundreds of thousands of uh transactions per<00:04:14.159> second<00:04:14.640> MH<00:04:15.120> not<00:04:15.280> to<00:04:15.400> say<00:04:15.640> that<00:04:15.760> we're<00:04:15.920> not 00:04:16.069 --> 00:04:16.079 align:start position:0% per second MH not to say that we're not 00:04:16.079 --> 00:04:17.870 align:start position:0% per second MH not to say that we're not doing<00:04:16.280> the<00:04:16.400> analytical<00:04:16.959> part<00:04:17.280> but<00:04:17.560> there's<00:04:17.759> a 00:04:17.870 --> 00:04:17.880 align:start position:0% doing the analytical part but there's a 00:04:17.880 --> 00:04:20.670 align:start position:0% doing the analytical part but there's a lot<00:04:18.079> of<00:04:18.759> a<00:04:18.880> lot<00:04:19.040> of<00:04:19.359> that<00:04:19.680> idea<00:04:20.280> I'm<00:04:20.400> seeing 00:04:20.670 --> 00:04:20.680 align:start position:0% lot of a lot of that idea I'm seeing 00:04:20.680 --> 00:04:24.510 align:start position:0% lot of a lot of that idea I'm seeing today<00:04:21.079> when<00:04:21.479> I'm<00:04:21.600> seeing<00:04:22.120> you<00:04:22.400> our<00:04:22.720> users<00:04:23.720> R 00:04:24.510 --> 00:04:24.520 align:start position:0% today when I'm seeing you our users R 00:04:24.520 --> 00:04:26.550 align:start position:0% today when I'm seeing you our users R transactions<00:04:25.080> under<00:04:25.639> huge 00:04:26.550 --> 00:04:26.560 align:start position:0% transactions under huge 00:04:26.560 --> 00:04:30.390 align:start position:0% transactions under huge loads<00:04:27.560> so<00:04:27.800> I<00:04:28.120> I<00:04:28.400> I<00:04:28.560> I<00:04:28.639> think<00:04:28.800> I've<00:04:28.919> read<00:04:29.479> uh<00:04:29.840> agre 00:04:30.390 --> 00:04:30.400 align:start position:0% loads so I I I I think I've read uh agre 00:04:30.400 --> 00:04:32.710 align:start position:0% loads so I I I I think I've read uh agre used<00:04:30.639> on<00:04:30.800> Wall<00:04:31.000> Street<00:04:31.240> and<00:04:31.440> by<00:04:31.680> for<00:04:31.800> trading 00:04:32.710 --> 00:04:32.720 align:start position:0% used on Wall Street and by for trading 00:04:32.720 --> 00:04:34.870 align:start position:0% used on Wall Street and by for trading uh<00:04:33.199> so<00:04:33.479> this<00:04:33.600> is<00:04:33.680> not<00:04:33.919> typical<00:04:34.240> application<00:04:34.720> of 00:04:34.870 --> 00:04:34.880 align:start position:0% uh so this is not typical application of 00:04:34.880 --> 00:04:36.270 align:start position:0% uh so this is not typical application of kind<00:04:35.000> of<00:04:35.120> traditional<00:04:35.440> open<00:04:35.639> source<00:04:35.880> we<00:04:36.000> see 00:04:36.270 --> 00:04:36.280 align:start position:0% kind of traditional open source we see 00:04:36.280 --> 00:04:39.310 align:start position:0% kind of traditional open source we see around<00:04:37.280> directly<00:04:37.880> right<00:04:38.039> so<00:04:38.520> how<00:04:39.039> you<00:04:39.120> know 00:04:39.310 --> 00:04:39.320 align:start position:0% around directly right so how you know 00:04:39.320 --> 00:04:40.990 align:start position:0% around directly right so how you know how<00:04:39.479> does<00:04:39.680> that<00:04:39.919> work<00:04:40.199> you<00:04:40.320> know<00:04:40.560> how<00:04:40.800> these 00:04:40.990 --> 00:04:41.000 align:start position:0% how does that work you know how these 00:04:41.000 --> 00:04:43.749 align:start position:0% how does that work you know how these customers<00:04:41.680> you<00:04:41.800> know<00:04:42.759> use<00:04:43.000> it<00:04:43.440> if<00:04:43.520> you<00:04:43.639> can 00:04:43.749 --> 00:04:43.759 align:start position:0% customers you know use it if you can 00:04:43.759 --> 00:04:45.870 align:start position:0% customers you know use it if you can talk<00:04:43.919> a<00:04:44.000> little<00:04:44.160> bit<00:04:44.320> about<00:04:44.520> it<00:04:45.240> so<00:04:45.600> yeah<00:04:45.800> if 00:04:45.870 --> 00:04:45.880 align:start position:0% talk a little bit about it so yeah if 00:04:45.880 --> 00:04:47.909 align:start position:0% talk a little bit about it so yeah if you<00:04:46.400> mention<00:04:46.759> Wall<00:04:47.000> Street<00:04:47.320> then<00:04:47.520> let's<00:04:47.720> talk 00:04:47.909 --> 00:04:47.919 align:start position:0% you mention Wall Street then let's talk 00:04:47.919 --> 00:04:49.870 align:start position:0% you mention Wall Street then let's talk about<00:04:48.160> Wall<00:04:48.360> Street<00:04:48.639> a<00:04:48.720> little<00:04:48.919> bit<00:04:49.400> so<00:04:49.800> what 00:04:49.870 --> 00:04:49.880 align:start position:0% about Wall Street a little bit so what 00:04:49.880 --> 00:04:52.310 align:start position:0% about Wall Street a little bit so what is<00:04:50.080> important<00:04:50.600> in<00:04:50.800> financials<00:04:51.520> right<00:04:51.720> I<00:04:51.800> mean 00:04:52.310 --> 00:04:52.320 align:start position:0% is important in financials right I mean 00:04:52.320 --> 00:04:53.909 align:start position:0% is important in financials right I mean Financial<00:04:53.120> uh<00:04:53.240> if<00:04:53.320> you<00:04:53.479> think<00:04:53.720> about 00:04:53.909 --> 00:04:53.919 align:start position:0% Financial uh if you think about 00:04:53.919 --> 00:04:56.390 align:start position:0% Financial uh if you think about financial<00:04:54.400> companies<00:04:54.840> they<00:04:55.000> move<00:04:55.280> money<00:04:55.840> yes 00:04:56.390 --> 00:04:56.400 align:start position:0% financial companies they move money yes 00:04:56.400 --> 00:04:57.909 align:start position:0% financial companies they move money yes uh<00:04:56.520> they<00:04:56.639> don't<00:04:56.800> like<00:04:57.000> mistakes<00:04:57.680> they<00:04:57.759> don't 00:04:57.909 --> 00:04:57.919 align:start position:0% uh they don't like mistakes they don't 00:04:57.919 --> 00:05:02.950 align:start position:0% uh they don't like mistakes they don't like<00:04:58.080> down<00:04:58.400> times<00:04:59.400> uh<00:04:59.960> so<00:05:00.960> for<00:05:01.280> them<00:05:02.000> uh<00:05:02.800> to 00:05:02.950 --> 00:05:02.960 align:start position:0% like down times uh so for them uh to 00:05:02.960 --> 00:05:05.230 align:start position:0% like down times uh so for them uh to move<00:05:03.199> to<00:05:03.320> a<00:05:03.440> new<00:05:03.639> system<00:05:04.000> would<00:05:04.160> be<00:05:04.479> a<00:05:04.680> huge 00:05:05.230 --> 00:05:05.240 align:start position:0% move to a new system would be a huge 00:05:05.240 --> 00:05:07.870 align:start position:0% move to a new system would be a huge decision<00:05:06.240> and<00:05:06.919> they<00:05:07.160> and<00:05:07.280> that's<00:05:07.520> why<00:05:07.680> they 00:05:07.870 --> 00:05:07.880 align:start position:0% decision and they and that's why they 00:05:07.880 --> 00:05:11.150 align:start position:0% decision and they and that's why they make<00:05:08.120> moves<00:05:08.520> very<00:05:09.039> rarely<00:05:10.039> and<00:05:10.680> and<00:05:10.880> that's 00:05:11.150 --> 00:05:11.160 align:start position:0% make moves very rarely and and that's 00:05:11.160 --> 00:05:13.430 align:start position:0% make moves very rarely and and that's why<00:05:11.479> I<00:05:11.520> mean<00:05:11.919> they<00:05:12.560> a<00:05:12.639> lot<00:05:12.759> of<00:05:12.880> times<00:05:13.080> when<00:05:13.199> you 00:05:13.430 --> 00:05:13.440 align:start position:0% why I mean they a lot of times when you 00:05:13.440 --> 00:05:15.550 align:start position:0% why I mean they a lot of times when you walk<00:05:13.680> into<00:05:13.880> a<00:05:14.000> large<00:05:14.360> Wall<00:05:14.560> Street<00:05:14.800> firm 00:05:15.550 --> 00:05:15.560 align:start position:0% walk into a large Wall Street firm 00:05:15.560 --> 00:05:17.830 align:start position:0% walk into a large Wall Street firm you'll<00:05:15.759> see<00:05:15.960> a<00:05:16.120> traditional<00:05:16.960> two<00:05:17.280> three<00:05:17.520> tier 00:05:17.830 --> 00:05:17.840 align:start position:0% you'll see a traditional two three tier 00:05:17.840 --> 00:05:19.790 align:start position:0% you'll see a traditional two three tier architecture<00:05:18.520> where<00:05:18.720> there's<00:05:19.000> one<00:05:19.280> database 00:05:19.790 --> 00:05:19.800 align:start position:0% architecture where there's one database 00:05:19.800 --> 00:05:22.270 align:start position:0% architecture where there's one database maybe<00:05:20.080> with<00:05:20.199> some<00:05:20.479> replication<00:05:21.479> that<00:05:21.720> gets<00:05:22.199> uh 00:05:22.270 --> 00:05:22.280 align:start position:0% maybe with some replication that gets uh 00:05:22.280 --> 00:05:24.150 align:start position:0% maybe with some replication that gets uh loaded<00:05:22.759> but<00:05:22.960> it's<00:05:23.160> transactional<00:05:23.840> and<00:05:23.960> it 00:05:24.150 --> 00:05:24.160 align:start position:0% loaded but it's transactional and it 00:05:24.160 --> 00:05:26.870 align:start position:0% loaded but it's transactional and it performs<00:05:24.720> under<00:05:25.039> high<00:05:25.280> Lo<00:05:25.639> and<00:05:25.800> generally<00:05:26.720> the 00:05:26.870 --> 00:05:26.880 align:start position:0% performs under high Lo and generally the 00:05:26.880 --> 00:05:29.790 align:start position:0% performs under high Lo and generally the main<00:05:27.160> goal<00:05:27.520> the<00:05:27.680> main<00:05:28.319> um<00:05:28.840> goal<00:05:29.080> there<00:05:29.680> to 00:05:29.790 --> 00:05:29.800 align:start position:0% main goal the main um goal there to 00:05:29.800 --> 00:05:31.990 align:start position:0% main goal the main um goal there to achieve<00:05:30.080> when<00:05:30.280> they<00:05:30.560> start<00:05:30.840> migrating<00:05:31.360> to<00:05:31.840> an 00:05:31.990 --> 00:05:32.000 align:start position:0% achieve when they start migrating to an 00:05:32.000 --> 00:05:34.790 align:start position:0% achieve when they start migrating to an in<00:05:32.160> memory<00:05:32.639> architecture<00:05:33.639> is<00:05:34.360> performance 00:05:34.790 --> 00:05:34.800 align:start position:0% in memory architecture is performance 00:05:34.800 --> 00:05:37.510 align:start position:0% in memory architecture is performance and<00:05:35.000> scale<00:05:35.479> so<00:05:36.400> at<00:05:36.560> certain<00:05:36.919> point<00:05:37.160> buying 00:05:37.510 --> 00:05:37.520 align:start position:0% and scale so at certain point buying 00:05:37.520 --> 00:05:39.950 align:start position:0% and scale so at certain point buying more<00:05:37.759> Hardware<00:05:38.240> stops<00:05:38.600> working<00:05:38.880> for<00:05:39.080> them<00:05:39.600> and 00:05:39.950 --> 00:05:39.960 align:start position:0% more Hardware stops working for them and 00:05:39.960 --> 00:05:42.550 align:start position:0% more Hardware stops working for them and uh<00:05:40.639> from<00:05:41.240> skillability<00:05:41.759> standpoint<00:05:42.360> and 00:05:42.550 --> 00:05:42.560 align:start position:0% uh from skillability standpoint and 00:05:42.560 --> 00:05:46.510 align:start position:0% uh from skillability standpoint and probably<00:05:42.880> from<00:05:43.319> uh<00:05:44.080> economics<00:05:44.960> uh<00:05:45.120> from<00:05:45.520> um 00:05:46.510 --> 00:05:46.520 align:start position:0% probably from uh economics uh from um 00:05:46.520 --> 00:05:50.189 align:start position:0% probably from uh economics uh from um simply<00:05:47.319> it<00:05:47.400> just<00:05:47.600> gets<00:05:47.800> too<00:05:48.080> pricey<00:05:49.080> and<00:05:49.600> uh 00:05:50.189 --> 00:05:50.199 align:start position:0% simply it just gets too pricey and uh 00:05:50.199 --> 00:05:52.670 align:start position:0% simply it just gets too pricey and uh the<00:05:50.440> there<00:05:50.639> comes<00:05:51.240> two<00:05:51.400> features<00:05:51.919> in<00:05:52.120> aide 00:05:52.670 --> 00:05:52.680 align:start position:0% the there comes two features in aide 00:05:52.680 --> 00:05:55.270 align:start position:0% the there comes two features in aide that<00:05:52.919> actually<00:05:53.600> differentiated<00:05:54.600> from<00:05:55.000> uh<00:05:55.120> the 00:05:55.270 --> 00:05:55.280 align:start position:0% that actually differentiated from uh the 00:05:55.280 --> 00:05:57.670 align:start position:0% that actually differentiated from uh the rest<00:05:55.440> of<00:05:55.639> the<00:05:56.639> products<00:05:56.960> on<00:05:57.080> the<00:05:57.199> market<00:05:57.520> and 00:05:57.670 --> 00:05:57.680 align:start position:0% rest of the products on the market and 00:05:57.680 --> 00:05:59.950 align:start position:0% rest of the products on the market and one<00:05:57.840> is<00:05:58.080> full<00:05:58.440> asset<00:05:58.759> compliance<00:05:59.520> we're<00:05:59.759> not 00:05:59.950 --> 00:05:59.960 align:start position:0% one is full asset compliance we're not 00:05:59.960 --> 00:06:01.629 align:start position:0% one is full asset compliance we're not eventually<00:06:00.479> consistent<00:06:00.960> we're<00:06:01.160> fully 00:06:01.629 --> 00:06:01.639 align:start position:0% eventually consistent we're fully 00:06:01.639 --> 00:06:04.110 align:start position:0% eventually consistent we're fully consistent<00:06:02.639> so<00:06:03.199> you<00:06:03.280> can<00:06:03.440> take<00:06:03.600> an<00:06:03.720> oral 00:06:04.110 --> 00:06:04.120 align:start position:0% consistent so you can take an oral 00:06:04.120 --> 00:06:07.469 align:start position:0% consistent so you can take an oral transaction<00:06:04.560> or<00:06:04.759> my<00:06:05.319> transaction<00:06:06.319> and<00:06:07.000> uh<00:06:07.240> run 00:06:07.469 --> 00:06:07.479 align:start position:0% transaction or my transaction and uh run 00:06:07.479 --> 00:06:10.710 align:start position:0% transaction or my transaction and uh run it<00:06:07.599> an<00:06:07.759> ignite<00:06:08.160> or<00:06:08.319> G<00:06:08.639> gain<00:06:09.520> and<00:06:09.800> not<00:06:10.000> only<00:06:10.520> we 00:06:10.710 --> 00:06:10.720 align:start position:0% it an ignite or G gain and not only we 00:06:10.720 --> 00:06:15.469 align:start position:0% it an ignite or G gain and not only we will<00:06:11.680> execute<00:06:12.080> it<00:06:12.800> uh<00:06:13.800> in<00:06:14.080> with<00:06:14.240> full<00:06:14.639> asset 00:06:15.469 --> 00:06:15.479 align:start position:0% will execute it uh in with full asset 00:06:15.479 --> 00:06:18.070 align:start position:0% will execute it uh in with full asset guarantees<00:06:16.479> uh<00:06:16.840> regardless<00:06:17.319> of<00:06:17.800> whatever 00:06:18.070 --> 00:06:18.080 align:start position:0% guarantees uh regardless of whatever 00:06:18.080 --> 00:06:20.390 align:start position:0% guarantees uh regardless of whatever failures<00:06:18.479> happen<00:06:18.720> on<00:06:18.800> the<00:06:18.919> cluster<00:06:19.639> we<00:06:20.120> will 00:06:20.390 --> 00:06:20.400 align:start position:0% failures happen on the cluster we will 00:06:20.400 --> 00:06:23.150 align:start position:0% failures happen on the cluster we will not<00:06:21.120> we<00:06:21.280> will<00:06:21.599> actually<00:06:22.240> make<00:06:22.520> your<00:06:22.720> database 00:06:23.150 --> 00:06:23.160 align:start position:0% not we will actually make your database 00:06:23.160 --> 00:06:24.589 align:start position:0% not we will actually make your database part<00:06:23.280> of<00:06:23.440> the<00:06:23.599> transaction<00:06:24.080> as<00:06:24.199> well<00:06:24.360> so<00:06:24.520> if 00:06:24.589 --> 00:06:24.599 align:start position:0% part of the transaction as well so if 00:06:24.599 --> 00:06:27.469 align:start position:0% part of the transaction as well so if you<00:06:24.720> still<00:06:24.960> want<00:06:25.120> to<00:06:25.360> write<00:06:25.599> to<00:06:26.120> database<00:06:27.120> uh 00:06:27.469 --> 00:06:27.479 align:start position:0% you still want to write to database uh 00:06:27.479 --> 00:06:28.870 align:start position:0% you still want to write to database uh then<00:06:27.720> database<00:06:28.120> transaction<00:06:28.479> will<00:06:28.639> become 00:06:28.870 --> 00:06:28.880 align:start position:0% then database transaction will become 00:06:28.880 --> 00:06:31.309 align:start position:0% then database transaction will become part<00:06:29.039> of<00:06:29.720> transaction<00:06:30.520> and<00:06:30.720> another<00:06:31.000> side<00:06:31.160> is 00:06:31.309 --> 00:06:31.319 align:start position:0% part of transaction and another side is 00:06:31.319 --> 00:06:33.870 align:start position:0% part of transaction and another side is SQL<00:06:32.039> so<00:06:32.280> because<00:06:32.759> all<00:06:32.919> these<00:06:33.120> companies<00:06:33.759> are 00:06:33.870 --> 00:06:33.880 align:start position:0% SQL so because all these companies are 00:06:33.880 --> 00:06:37.990 align:start position:0% SQL so because all these companies are so<00:06:34.160> database<00:06:34.720> Centric<00:06:35.720> uh<00:06:36.599> they<00:06:37.599> the<00:06:37.759> main 00:06:37.990 --> 00:06:38.000 align:start position:0% so database Centric uh they the main 00:06:38.000 --> 00:06:39.749 align:start position:0% so database Centric uh they the main language<00:06:38.400> they<00:06:38.560> talk<00:06:38.840> used<00:06:39.120> to<00:06:39.280> talk<00:06:39.400> to<00:06:39.560> their 00:06:39.749 --> 00:06:39.759 align:start position:0% language they talk used to talk to their 00:06:39.759 --> 00:06:43.350 align:start position:0% language they talk used to talk to their data<00:06:40.039> is<00:06:40.199> SQL<00:06:41.000> so<00:06:41.240> our<00:06:41.440> support<00:06:41.800> for<00:06:42.120> SQL<00:06:42.759> with 00:06:43.350 --> 00:06:43.360 align:start position:0% data is SQL so our support for SQL with 00:06:43.360 --> 00:06:45.309 align:start position:0% data is SQL so our support for SQL with strong<00:06:43.639> indexing<00:06:44.639> so<00:06:44.840> we<00:06:44.960> care<00:06:45.120> about 00:06:45.309 --> 00:06:45.319 align:start position:0% strong indexing so we care about 00:06:45.319 --> 00:06:47.550 align:start position:0% strong indexing so we care about performance<00:06:45.720> wi<00:06:45.880> index<00:06:46.199> a<00:06:46.360> lot<00:06:46.960> makes<00:06:47.160> it<00:06:47.440> a 00:06:47.550 --> 00:06:47.560 align:start position:0% performance wi index a lot makes it a 00:06:47.560 --> 00:06:50.430 align:start position:0% performance wi index a lot makes it a lucrative<00:06:48.360> solution<00:06:49.360> stre<00:06:49.680> interesting<00:06:50.240> this 00:06:50.430 --> 00:06:50.440 align:start position:0% lucrative solution stre interesting this 00:06:50.440 --> 00:06:52.909 align:start position:0% lucrative solution stre interesting this actually<00:06:50.720> very<00:06:50.919> interesting<00:06:51.400> because<00:06:52.400> uh<00:06:52.599> SP 00:06:52.909 --> 00:06:52.919 align:start position:0% actually very interesting because uh SP 00:06:52.919 --> 00:06:55.830 align:start position:0% actually very interesting because uh SP machine<00:06:53.199> itself<00:06:53.840> is<00:06:54.039> actually<00:06:54.440> doing<00:06:54.840> rgbm 00:06:55.830 --> 00:06:55.840 align:start position:0% machine itself is actually doing rgbm 00:06:55.840 --> 00:06:59.070 align:start position:0% machine itself is actually doing rgbm which<00:06:56.000> works<00:06:56.280> on<00:06:56.840> app<00:06:57.000> and<00:06:57.120> LP<00:06:58.000> so<00:06:58.520> uh<00:06:58.639> I<00:06:58.759> just 00:06:59.070 --> 00:06:59.080 align:start position:0% which works on app and LP so uh I just 00:06:59.080 --> 00:07:00.629 align:start position:0% which works on app and LP so uh I just talk<00:06:59.240> about<00:06:59.440> M<00:06:59.599> as<00:06:59.840> been<00:06:59.960> the<00:07:00.039> C<00:07:00.360> so<00:07:00.440> this<00:07:00.520> is 00:07:00.629 --> 00:07:00.639 align:start position:0% talk about M as been the C so this is 00:07:00.639 --> 00:07:02.550 align:start position:0% talk about M as been the C so this is very<00:07:01.039> I<00:07:01.120> think<00:07:01.520> like<00:07:01.800> what<00:07:01.879> I<00:07:02.000> realized<00:07:02.440> when 00:07:02.550 --> 00:07:02.560 align:start position:0% very I think like what I realized when 00:07:02.560 --> 00:07:05.469 align:start position:0% very I think like what I realized when we're<00:07:02.720> hosting<00:07:03.520> you<00:07:03.639> know<00:07:04.240> uh<00:07:04.680> g<00:07:04.919> game<00:07:05.199> up<00:07:05.360> at 00:07:05.469 --> 00:07:05.479 align:start position:0% we're hosting you know uh g game up at 00:07:05.479 --> 00:07:07.589 align:start position:0% we're hosting you know uh g game up at splice<00:07:05.759> machine<00:07:06.440> actually<00:07:06.960> we<00:07:07.120> fin<00:07:07.280> a<00:07:07.440> lot<00:07:07.520> of 00:07:07.589 --> 00:07:07.599 align:start position:0% splice machine actually we fin a lot of 00:07:07.599 --> 00:07:09.710 align:start position:0% splice machine actually we fin a lot of synergies<00:07:08.120> so<00:07:08.240> I<00:07:08.360> think<00:07:08.560> you<00:07:08.680> know<00:07:09.479> what<00:07:09.560> would 00:07:09.710 --> 00:07:09.720 align:start position:0% synergies so I think you know what would 00:07:09.720 --> 00:07:12.189 align:start position:0% synergies so I think you know what would be<00:07:09.800> interesting<00:07:10.199> tonight<00:07:11.039> uh<00:07:11.160> is<00:07:11.319> kind<00:07:11.479> of<00:07:12.039> uh 00:07:12.189 --> 00:07:12.199 align:start position:0% be interesting tonight uh is kind of uh 00:07:12.199 --> 00:07:13.869 align:start position:0% be interesting tonight uh is kind of uh I<00:07:12.280> think<00:07:12.520> we'll<00:07:12.800> kind<00:07:12.919> of<00:07:13.319> these<00:07:13.479> topics<00:07:13.720> will 00:07:13.869 --> 00:07:13.879 align:start position:0% I think we'll kind of these topics will 00:07:13.879 --> 00:07:15.869 align:start position:0% I think we'll kind of these topics will be<00:07:14.000> raised<00:07:14.879> right<00:07:15.039> and<00:07:15.199> maybe<00:07:15.599> kind<00:07:15.759> of 00:07:15.869 --> 00:07:15.879 align:start position:0% be raised right and maybe kind of 00:07:15.879 --> 00:07:17.510 align:start position:0% be raised right and maybe kind of questions<00:07:16.360> kind<00:07:16.479> of<00:07:16.599> can<00:07:16.840> come<00:07:17.000> up<00:07:17.160> which<00:07:17.360> will 00:07:17.510 --> 00:07:17.520 align:start position:0% questions kind of can come up which will 00:07:17.520 --> 00:07:20.350 align:start position:0% questions kind of can come up which will not<00:07:17.960> come<00:07:18.199> up<00:07:18.720> by<00:07:18.879> itself<00:07:19.599> but<00:07:19.759> basically<00:07:20.199> have 00:07:20.350 --> 00:07:20.360 align:start position:0% not come up by itself but basically have 00:07:20.360 --> 00:07:22.150 align:start position:0% not come up by itself but basically have two<00:07:20.560> different<00:07:21.120> companies<00:07:21.759> probably 00:07:22.150 --> 00:07:22.160 align:start position:0% two different companies probably 00:07:22.160 --> 00:07:24.029 align:start position:0% two different companies probably addressing<00:07:22.479> two<00:07:22.639> different<00:07:22.879> markets<00:07:23.800> but 00:07:24.029 --> 00:07:24.039 align:start position:0% addressing two different markets but 00:07:24.039 --> 00:07:26.710 align:start position:0% addressing two different markets but kind<00:07:24.199> of<00:07:24.440> talking<00:07:24.759> about<00:07:25.080> you<00:07:25.199> know<00:07:25.360> SQL<00:07:25.840> asset 00:07:26.710 --> 00:07:26.720 align:start position:0% kind of talking about you know SQL asset 00:07:26.720 --> 00:07:28.510 align:start position:0% kind of talking about you know SQL asset right<00:07:27.000> and<00:07:27.440> you<00:07:27.520> know<00:07:27.720> Essen<00:07:28.080> going<00:07:28.280> after 00:07:28.510 --> 00:07:28.520 align:start position:0% right and you know Essen going after 00:07:28.520 --> 00:07:30.150 align:start position:0% right and you know Essen going after Oracle<00:07:28.879> from<00:07:29.039> different<00:07:29.440> angles<00:07:30.000> from 00:07:30.150 --> 00:07:30.160 align:start position:0% Oracle from different angles from 00:07:30.160 --> 00:07:31.350 align:start position:0% Oracle from different angles from different<00:07:30.400> from<00:07:30.680> different<00:07:30.919> performance 00:07:31.350 --> 00:07:31.360 align:start position:0% different from different performance 00:07:31.360 --> 00:07:33.230 align:start position:0% different from different performance angles<00:07:32.120> different<00:07:32.319> use<00:07:32.599> case<00:07:32.720> angles<00:07:33.080> yes 00:07:33.230 --> 00:07:33.240 align:start position:0% angles different use case angles yes 00:07:33.240 --> 00:07:34.950 align:start position:0% angles different use case angles yes yeah<00:07:33.440> yeah<00:07:33.720> yeah<00:07:34.000> yeah<00:07:34.240> this<00:07:34.400> exciting<00:07:34.800> so 00:07:34.950 --> 00:07:34.960 align:start position:0% yeah yeah yeah yeah this exciting so 00:07:34.960 --> 00:07:38.029 align:start position:0% yeah yeah yeah yeah this exciting so tell<00:07:35.080> me<00:07:35.319> how<00:07:35.759> so<00:07:35.960> I<00:07:36.120> think<00:07:36.360> Apachi<00:07:37.160> U<00:07:37.479> ignite 00:07:38.029 --> 00:07:38.039 align:start position:0% tell me how so I think Apachi U ignite 00:07:38.039 --> 00:07:41.510 align:start position:0% tell me how so I think Apachi U ignite started<00:07:38.800> a<00:07:38.919> year<00:07:39.080> ago<00:07:39.360> so<00:07:40.039> not<00:07:40.680> or<00:07:41.120> two<00:07:41.280> years 00:07:41.510 --> 00:07:41.520 align:start position:0% started a year ago so not or two years 00:07:41.520 --> 00:07:43.950 align:start position:0% started a year ago so not or two years ago<00:07:42.160> kind<00:07:42.280> of<00:07:42.720> putting<00:07:43.080> to<00:07:43.199> a<00:07:43.319> test<00:07:43.520> with<00:07:43.720> this 00:07:43.950 --> 00:07:43.960 align:start position:0% ago kind of putting to a test with this 00:07:43.960 --> 00:07:46.909 align:start position:0% ago kind of putting to a test with this dates<00:07:44.479> not<00:07:44.639> too<00:07:44.960> not<00:07:45.039> too<00:07:45.159> long<00:07:45.520> I<00:07:45.599> think<00:07:45.919> uh 00:07:46.909 --> 00:07:46.919 align:start position:0% dates not too not too long I think uh 00:07:46.919 --> 00:07:49.110 align:start position:0% dates not too not too long I think uh year<00:07:47.280> over<00:07:47.479> a<00:07:47.599> year<00:07:47.759> so<00:07:48.000> over<00:07:48.199> year<00:07:48.319> ago<00:07:48.560> so<00:07:48.960> uh 00:07:49.110 --> 00:07:49.120 align:start position:0% year over a year so over year ago so uh 00:07:49.120 --> 00:07:50.950 align:start position:0% year over a year so over year ago so uh there<00:07:49.199> are<00:07:49.360> two<00:07:49.560> parts<00:07:50.000> right<00:07:50.400> there's 00:07:50.950 --> 00:07:50.960 align:start position:0% there are two parts right there's 00:07:50.960 --> 00:07:53.149 align:start position:0% there are two parts right there's incubation<00:07:51.720> and<00:07:51.919> then<00:07:52.080> there<00:07:52.199> is<00:07:52.400> graduation 00:07:53.149 --> 00:07:53.159 align:start position:0% incubation and then there is graduation 00:07:53.159 --> 00:07:56.670 align:start position:0% incubation and then there is graduation yes<00:07:53.440> so<00:07:53.919> if<00:07:54.039> you<00:07:54.240> start<00:07:54.639> from<00:07:54.879> when<00:07:55.120> we<00:07:55.840> donated 00:07:56.670 --> 00:07:56.680 align:start position:0% yes so if you start from when we donated 00:07:56.680 --> 00:07:58.749 align:start position:0% yes so if you start from when we donated uh<00:07:56.800> the<00:07:56.919> code<00:07:57.159> to<00:07:57.360> Apache<00:07:57.800> it<00:07:57.919> was<00:07:58.080> 2<00:07:58.240> years<00:07:58.440> ago 00:07:58.749 --> 00:07:58.759 align:start position:0% uh the code to Apache it was 2 years ago 00:07:58.759 --> 00:08:01.149 align:start position:0% uh the code to Apache it was 2 years ago yep<00:07:59.159> and<00:07:59.319> and<00:07:59.400> we<00:07:59.599> graduated<00:08:00.120> within<00:08:00.400> 9<00:08:00.800> months 00:08:01.149 --> 00:08:01.159 align:start position:0% yep and and we graduated within 9 months 00:08:01.159 --> 00:08:04.230 align:start position:0% yep and and we graduated within 9 months so<00:08:01.360> we<00:08:01.520> graduated<00:08:02.000> pretty<00:08:02.319> fast<00:08:02.879> and<00:08:03.879> uh<00:08:04.080> the 00:08:04.230 --> 00:08:04.240 align:start position:0% so we graduated pretty fast and uh the 00:08:04.240 --> 00:08:06.990 align:start position:0% so we graduated pretty fast and uh the reason<00:08:04.479> for<00:08:04.720> that<00:08:04.960> was<00:08:05.400> the<00:08:06.280> very<00:08:06.599> rapidly 00:08:06.990 --> 00:08:07.000 align:start position:0% reason for that was the very rapidly 00:08:07.000 --> 00:08:11.430 align:start position:0% reason for that was the very rapidly growing<00:08:07.400> Community<00:08:08.159> oh<00:08:08.639> so<00:08:09.080> it's<00:08:09.479> uh<00:08:10.240> we're<00:08:11.159> I 00:08:11.430 --> 00:08:11.440 align:start position:0% growing Community oh so it's uh we're I 00:08:11.440 --> 00:08:13.790 align:start position:0% growing Community oh so it's uh we're I I<00:08:11.479> mean<00:08:12.319> if<00:08:12.400> you<00:08:12.520> put<00:08:12.720> spark<00:08:13.080> outside<00:08:13.560> I<00:08:13.639> think 00:08:13.790 --> 00:08:13.800 align:start position:0% I mean if you put spark outside I think 00:08:13.800 --> 00:08:16.869 align:start position:0% I mean if you put spark outside I think we're<00:08:14.080> one<00:08:14.199> of<00:08:14.400> the<00:08:14.960> fastest<00:08:15.879> uh<00:08:16.479> growing 00:08:16.869 --> 00:08:16.879 align:start position:0% we're one of the fastest uh growing 00:08:16.879 --> 00:08:17.869 align:start position:0% we're one of the fastest uh growing projects<00:08:17.199> in 00:08:17.869 --> 00:08:17.879 align:start position:0% projects in 00:08:17.879 --> 00:08:21.110 align:start position:0% projects in Apache<00:08:18.879> and<00:08:19.280> uh<00:08:20.000> uh<00:08:20.120> the<00:08:20.240> community<00:08:20.639> is<00:08:20.800> very 00:08:21.110 --> 00:08:21.120 align:start position:0% Apache and uh uh the community is very 00:08:21.120 --> 00:08:23.189 align:start position:0% Apache and uh uh the community is very responsive<00:08:21.680> the<00:08:21.800> community<00:08:22.159> is<00:08:22.360> very<00:08:22.800> willing 00:08:23.189 --> 00:08:23.199 align:start position:0% responsive the community is very willing 00:08:23.199 --> 00:08:26.790 align:start position:0% responsive the community is very willing to<00:08:24.199> uh<00:08:24.720> engage<00:08:25.720> and<00:08:26.080> uh<00:08:26.240> the<00:08:26.400> stuff<00:08:26.639> we're 00:08:26.790 --> 00:08:26.800 align:start position:0% to uh engage and uh the stuff we're 00:08:26.800 --> 00:08:28.749 align:start position:0% to uh engage and uh the stuff we're working<00:08:27.039> on<00:08:27.199> is<00:08:27.400> very<00:08:27.599> interesting<00:08:28.080> I<00:08:28.159> me<00:08:28.319> it's 00:08:28.749 --> 00:08:28.759 align:start position:0% working on is very interesting I me it's 00:08:28.759 --> 00:08:30.430 align:start position:0% working on is very interesting I me it's all<00:08:29.319> a<00:08:29.400> lot<00:08:29.560> of<00:08:29.680> distributed<00:08:30.159> stuff 00:08:30.430 --> 00:08:30.440 align:start position:0% all a lot of distributed stuff 00:08:30.440 --> 00:08:31.950 align:start position:0% all a lot of distributed stuff distributed<00:08:30.879> locks<00:08:31.280> transactions 00:08:31.950 --> 00:08:31.960 align:start position:0% distributed locks transactions 00:08:31.960 --> 00:08:33.949 align:start position:0% distributed locks transactions distributed<00:08:32.519> data<00:08:32.839> consistency<00:08:33.680> so<00:08:33.800> all 00:08:33.949 --> 00:08:33.959 align:start position:0% distributed data consistency so all 00:08:33.959 --> 00:08:36.469 align:start position:0% distributed data consistency so all these<00:08:34.360> problems<00:08:35.360> uh<00:08:35.800> create<00:08:36.159> like<00:08:36.320> this 00:08:36.469 --> 00:08:36.479 align:start position:0% these problems uh create like this 00:08:36.479 --> 00:08:38.110 align:start position:0% these problems uh create like this unique<00:08:36.800> environment<00:08:37.279> where<00:08:37.440> you<00:08:37.519> can<00:08:37.680> get<00:08:37.839> one 00:08:38.110 --> 00:08:38.120 align:start position:0% unique environment where you can get one 00:08:38.120 --> 00:08:39.550 align:start position:0% unique environment where you can get one of<00:08:38.360> experience<00:08:38.839> that<00:08:38.959> you<00:08:39.080> wouldn't<00:08:39.360> get 00:08:39.550 --> 00:08:39.560 align:start position:0% of experience that you wouldn't get 00:08:39.560 --> 00:08:42.670 align:start position:0% of experience that you wouldn't get anywhere<00:08:40.360> else<00:08:41.000> and<00:08:41.200> that<00:08:41.360> attracts<00:08:41.760> a<00:08:41.880> lot<00:08:42.000> of 00:08:42.670 --> 00:08:42.680 align:start position:0% anywhere else and that attracts a lot of 00:08:42.680 --> 00:08:44.350 align:start position:0% anywhere else and that attracts a lot of commuters<00:08:43.240> and<00:08:43.360> a<00:08:43.479> lot<00:08:43.599> of<00:08:43.719> contributors<00:08:44.200> to 00:08:44.350 --> 00:08:44.360 align:start position:0% commuters and a lot of contributors to 00:08:44.360 --> 00:08:45.870 align:start position:0% commuters and a lot of contributors to the<00:08:44.519> project<00:08:44.800> so<00:08:44.959> we've<00:08:45.120> been<00:08:45.320> growing<00:08:45.680> ever 00:08:45.870 --> 00:08:45.880 align:start position:0% the project so we've been growing ever 00:08:45.880 --> 00:08:47.470 align:start position:0% the project so we've been growing ever since<00:08:46.240> cool<00:08:46.600> yeah<00:08:46.720> that<00:08:46.839> was<00:08:47.040> actually<00:08:47.320> my 00:08:47.470 --> 00:08:47.480 align:start position:0% since cool yeah that was actually my 00:08:47.480 --> 00:08:49.430 align:start position:0% since cool yeah that was actually my question<00:08:47.880> and<00:08:48.080> how<00:08:48.240> how<00:08:48.360> it<00:08:48.519> affected<00:08:49.279> you 00:08:49.430 --> 00:08:49.440 align:start position:0% question and how how it affected you 00:08:49.440 --> 00:08:51.269 align:start position:0% question and how how it affected you guys<00:08:49.640> but<00:08:49.839> how<00:08:49.959> did<00:08:50.120> it<00:08:50.240> affect<00:08:50.480> the<00:08:50.560> company 00:08:51.269 --> 00:08:51.279 align:start position:0% guys but how did it affect the company 00:08:51.279 --> 00:08:52.470 align:start position:0% guys but how did it affect the company right<00:08:51.399> so<00:08:51.600> basically<00:08:52.000> you<00:08:52.120> know<00:08:52.240> you<00:08:52.320> have 00:08:52.470 --> 00:08:52.480 align:start position:0% right so basically you know you have 00:08:52.480 --> 00:08:55.030 align:start position:0% right so basically you know you have dual<00:08:52.839> roles<00:08:53.839> uh<00:08:54.240> does<00:08:54.360> it<00:08:54.519> mean<00:08:54.680> you<00:08:54.800> spend 00:08:55.030 --> 00:08:55.040 align:start position:0% dual roles uh does it mean you spend 00:08:55.040 --> 00:08:57.430 align:start position:0% dual roles uh does it mean you spend more<00:08:55.200> time<00:08:55.399> in<00:08:55.519> the<00:08:55.640> open<00:08:55.880> source<00:08:56.519> or<00:08:57.080> does<00:08:57.240> it 00:08:57.430 --> 00:08:57.440 align:start position:0% more time in the open source or does it 00:08:57.440 --> 00:08:58.630 align:start position:0% more time in the open source or does it kind<00:08:57.560> of<00:08:58.040> like<00:08:58.160> do<00:08:58.200> you<00:08:58.320> have<00:08:58.399> a<00:08:58.440> lot<00:08:58.560> of 00:08:58.630 --> 00:08:58.640 align:start position:0% kind of like do you have a lot of 00:08:58.640 --> 00:09:00.030 align:start position:0% kind of like do you have a lot of synergies<00:08:59.200> so<00:08:59.279> it<00:08:59.360> kind<00:08:59.480> of<00:08:59.560> feeds<00:08:59.880> the 00:09:00.030 --> 00:09:00.040 align:start position:0% synergies so it kind of feeds the 00:09:00.040 --> 00:09:02.310 align:start position:0% synergies so it kind of feeds the business<00:09:00.880> how<00:09:01.000> do<00:09:01.120> you<00:09:01.320> kind<00:09:01.440> of<00:09:01.680> connect<00:09:02.160> this 00:09:02.310 --> 00:09:02.320 align:start position:0% business how do you kind of connect this 00:09:02.320 --> 00:09:05.550 align:start position:0% business how do you kind of connect this to<00:09:02.560> the<00:09:02.720> two<00:09:03.120> two<00:09:03.519> things<00:09:04.519> well<00:09:04.720> I<00:09:04.800> mean<00:09:05.120> one 00:09:05.550 --> 00:09:05.560 align:start position:0% to the two two things well I mean one 00:09:05.560 --> 00:09:07.470 align:start position:0% to the two two things well I mean one first<00:09:05.760> and<00:09:05.959> foremost<00:09:06.640> I<00:09:06.720> mean<00:09:07.079> it's<00:09:07.320> very 00:09:07.470 --> 00:09:07.480 align:start position:0% first and foremost I mean it's very 00:09:07.480 --> 00:09:09.910 align:start position:0% first and foremost I mean it's very important<00:09:08.000> that<00:09:08.240> as<00:09:08.360> a<00:09:08.480> grid<00:09:08.760> gain<00:09:09.079> as<00:09:09.200> a<00:09:09.800> the 00:09:09.910 --> 00:09:09.920 align:start position:0% important that as a grid gain as a the 00:09:09.920 --> 00:09:11.470 align:start position:0% important that as a grid gain as a the all<00:09:10.079> the<00:09:10.160> features<00:09:10.519> we<00:09:10.680> provide<00:09:10.959> on<00:09:11.120> top<00:09:11.240> of<00:09:11.360> a 00:09:11.470 --> 00:09:11.480 align:start position:0% all the features we provide on top of a 00:09:11.480 --> 00:09:13.470 align:start position:0% all the features we provide on top of a Patrick<00:09:11.800> Knight<00:09:12.040> so<00:09:12.279> we<00:09:13.000> first<00:09:13.160> of<00:09:13.240> all<00:09:13.360> the 00:09:13.470 --> 00:09:13.480 align:start position:0% Patrick Knight so we first of all the 00:09:13.480 --> 00:09:14.870 align:start position:0% Patrick Knight so we first of all the difference<00:09:13.800> between<00:09:14.079> grid<00:09:14.279> G<00:09:14.440> and<00:09:14.600> Patrick 00:09:14.870 --> 00:09:14.880 align:start position:0% difference between grid G and Patrick 00:09:14.880 --> 00:09:16.590 align:start position:0% difference between grid G and Patrick Knight<00:09:15.040> is<00:09:15.160> g<00:09:15.360> game<00:09:15.560> provides<00:09:16.120> Enterprise 00:09:16.590 --> 00:09:16.600 align:start position:0% Knight is g game provides Enterprise 00:09:16.600 --> 00:09:18.230 align:start position:0% Knight is g game provides Enterprise certain<00:09:16.920> Enterprise<00:09:17.399> level<00:09:17.640> features<00:09:18.040> like 00:09:18.230 --> 00:09:18.240 align:start position:0% certain Enterprise level features like 00:09:18.240 --> 00:09:20.069 align:start position:0% certain Enterprise level features like data<00:09:18.440> center<00:09:18.760> application<00:09:19.680> production 00:09:20.069 --> 00:09:20.079 align:start position:0% data center application production 00:09:20.079 --> 00:09:23.590 align:start position:0% data center application production upgrade<00:09:20.640> or<00:09:21.079> rolling<00:09:21.600> upgrades<00:09:22.480> uh<00:09:22.720> security 00:09:23.590 --> 00:09:23.600 align:start position:0% upgrade or rolling upgrades uh security 00:09:23.600 --> 00:09:26.350 align:start position:0% upgrade or rolling upgrades uh security so<00:09:23.839> things<00:09:24.160> that<00:09:24.320> you<00:09:24.440> would<00:09:24.680> need<00:09:25.120> in<00:09:26.000> serious 00:09:26.350 --> 00:09:26.360 align:start position:0% so things that you would need in serious 00:09:26.360 --> 00:09:27.949 align:start position:0% so things that you would need in serious Enterprise<00:09:26.800> deployment<00:09:27.360> but<00:09:27.519> you<00:09:27.680> probably 00:09:27.949 --> 00:09:27.959 align:start position:0% Enterprise deployment but you probably 00:09:27.959 --> 00:09:29.949 align:start position:0% Enterprise deployment but you probably could<00:09:28.200> be<00:09:28.399> get<00:09:28.600> by<00:09:28.839> in 00:09:29.949 --> 00:09:29.959 align:start position:0% could be get by in 00:09:29.959 --> 00:09:32.430 align:start position:0% could be get by in simpler<00:09:30.519> open<00:09:30.800> source<00:09:31.120> type<00:09:31.360> of<00:09:32.079> project 00:09:32.430 --> 00:09:32.440 align:start position:0% simpler open source type of project 00:09:32.440 --> 00:09:36.190 align:start position:0% simpler open source type of project deployments<00:09:33.360> MH<00:09:34.360> and<00:09:34.720> the<00:09:35.000> uh<00:09:35.200> the<00:09:35.360> main<00:09:35.959> uh 00:09:36.190 --> 00:09:36.200 align:start position:0% deployments MH and the uh the main uh 00:09:36.200 --> 00:09:39.670 align:start position:0% deployments MH and the uh the main uh goal<00:09:36.560> that<00:09:36.800> we<00:09:37.360> we're<00:09:38.279> trying<00:09:38.600> to<00:09:38.839> pursue<00:09:39.320> here 00:09:39.670 --> 00:09:39.680 align:start position:0% goal that we we're trying to pursue here 00:09:39.680 --> 00:09:42.110 align:start position:0% goal that we we're trying to pursue here is<00:09:39.920> that<00:09:40.320> you<00:09:40.399> should<00:09:40.680> not<00:09:40.959> be<00:09:41.240> worried<00:09:41.959> when 00:09:42.110 --> 00:09:42.120 align:start position:0% is that you should not be worried when 00:09:42.120 --> 00:09:44.230 align:start position:0% is that you should not be worried when you<00:09:42.279> write<00:09:42.880> a<00:09:43.040> code<00:09:43.399> with<00:09:43.600> when<00:09:43.720> you<00:09:43.839> code<00:09:44.040> to<00:09:44.160> a 00:09:44.230 --> 00:09:44.240 align:start position:0% you write a code with when you code to a 00:09:44.240 --> 00:09:46.389 align:start position:0% you write a code with when you code to a pach<00:09:44.720> you<00:09:44.800> should<00:09:44.920> not<00:09:45.040> be<00:09:45.200> wor<00:09:45.519> which<00:09:45.720> Edition 00:09:46.389 --> 00:09:46.399 align:start position:0% pach you should not be wor which Edition 00:09:46.399 --> 00:09:48.870 align:start position:0% pach you should not be wor which Edition whether<00:09:46.560> it's<00:09:46.680> a<00:09:46.839> patch<00:09:47.079> ignite<00:09:47.959> or<00:09:48.440> GD<00:09:48.680> G 00:09:48.870 --> 00:09:48.880 align:start position:0% whether it's a patch ignite or GD G 00:09:48.880 --> 00:09:50.710 align:start position:0% whether it's a patch ignite or GD G Enterprise<00:09:49.320> Edition<00:09:49.680> use<00:09:50.120> so<00:09:50.279> GD<00:09:50.480> gain 00:09:50.710 --> 00:09:50.720 align:start position:0% Enterprise Edition use so GD gain 00:09:50.720 --> 00:09:52.949 align:start position:0% Enterprise Edition use so GD gain actually<00:09:50.959> does<00:09:51.120> not<00:09:51.320> introduce<00:09:51.720> any<00:09:51.920> new<00:09:52.079> API 00:09:52.949 --> 00:09:52.959 align:start position:0% actually does not introduce any new API 00:09:52.959 --> 00:09:56.030 align:start position:0% actually does not introduce any new API most<00:09:53.240> of<00:09:53.440> the<00:09:53.920> uh<00:09:54.760> uh<00:09:55.480> most<00:09:55.640> of<00:09:55.800> the 00:09:56.030 --> 00:09:56.040 align:start position:0% most of the uh uh most of the 00:09:56.040 --> 00:09:57.990 align:start position:0% most of the uh uh most of the functionality<00:09:56.720> that<00:09:56.880> grid<00:09:57.120> game<00:09:57.360> adds<00:09:57.720> is<00:09:57.800> a 00:09:57.990 --> 00:09:58.000 align:start position:0% functionality that grid game adds is a 00:09:58.000 --> 00:10:00.230 align:start position:0% functionality that grid game adds is a configuration<00:09:58.720> okay<00:09:59.200> so<00:09:59.480> you<00:09:59.600> want<00:09:59.839> security 00:10:00.230 --> 00:10:00.240 align:start position:0% configuration okay so you want security 00:10:00.240 --> 00:10:02.670 align:start position:0% configuration okay so you want security it's<00:10:00.360> a<00:10:00.519> configuration<00:10:01.160> you<00:10:01.320> want<00:10:01.880> uh<00:10:02.240> rolling 00:10:02.670 --> 00:10:02.680 align:start position:0% it's a configuration you want uh rolling 00:10:02.680 --> 00:10:04.150 align:start position:0% it's a configuration you want uh rolling production<00:10:03.079> upgrades<00:10:03.480> it's<00:10:03.600> a<00:10:03.720> flack<00:10:04.000> you 00:10:04.150 --> 00:10:04.160 align:start position:0% production upgrades it's a flack you 00:10:04.160 --> 00:10:06.710 align:start position:0% production upgrades it's a flack you enable<00:10:04.440> on<00:10:04.560> a<00:10:04.720> configuration<00:10:05.279> you<00:10:05.440> want<00:10:06.440> uh 00:10:06.710 --> 00:10:06.720 align:start position:0% enable on a configuration you want uh 00:10:06.720 --> 00:10:08.110 align:start position:0% enable on a configuration you want uh data<00:10:07.000> center<00:10:07.240> application<00:10:07.680> again<00:10:07.880> it's 00:10:08.110 --> 00:10:08.120 align:start position:0% data center application again it's 00:10:08.120 --> 00:10:09.829 align:start position:0% data center application again it's configuration<00:10:08.880> if<00:10:09.000> you<00:10:09.079> want<00:10:09.240> to<00:10:09.399> get<00:10:09.560> some 00:10:09.829 --> 00:10:09.839 align:start position:0% configuration if you want to get some 00:10:09.839 --> 00:10:11.750 align:start position:0% configuration if you want to get some metrics<00:10:10.640> specific<00:10:11.079> to<00:10:11.279> Data<00:10:11.480> Center 00:10:11.750 --> 00:10:11.760 align:start position:0% metrics specific to Data Center 00:10:11.760 --> 00:10:13.550 align:start position:0% metrics specific to Data Center application<00:10:12.320> then<00:10:12.519> yeah<00:10:12.680> there's<00:10:12.880> some<00:10:13.079> API 00:10:13.550 --> 00:10:13.560 align:start position:0% application then yeah there's some API 00:10:13.560 --> 00:10:15.829 align:start position:0% application then yeah there's some API there<00:10:13.800> but<00:10:14.480> generally<00:10:14.839> if<00:10:14.959> you<00:10:15.120> use<00:10:15.519> just 00:10:15.829 --> 00:10:15.839 align:start position:0% there but generally if you use just 00:10:15.839 --> 00:10:17.230 align:start position:0% there but generally if you use just plain<00:10:16.120> vanilla<00:10:16.519> patch<00:10:16.839> that<00:10:17.000> you<00:10:17.079> can 00:10:17.230 --> 00:10:17.240 align:start position:0% plain vanilla patch that you can 00:10:17.240 --> 00:10:20.630 align:start position:0% plain vanilla patch that you can continue<00:10:17.560> using<00:10:17.839> it<00:10:18.200> in<00:10:18.560> G<00:10:19.560> cool<00:10:19.880> cool<00:10:20.120> cool<00:10:20.440> so 00:10:20.630 --> 00:10:20.640 align:start position:0% continue using it in G cool cool cool so 00:10:20.640 --> 00:10:22.509 align:start position:0% continue using it in G cool cool cool so this<00:10:20.760> is<00:10:20.959> this<00:10:21.079> is<00:10:21.320> really<00:10:21.560> exciting<00:10:22.200> uh<00:10:22.320> we're 00:10:22.509 --> 00:10:22.519 align:start position:0% this is this is really exciting uh we're 00:10:22.519 --> 00:10:23.790 align:start position:0% this is this is really exciting uh we're looking<00:10:22.720> forward<00:10:23.000> to<00:10:23.160> your<00:10:23.279> technical<00:10:23.640> talk 00:10:23.790 --> 00:10:23.800 align:start position:0% looking forward to your technical talk 00:10:23.800 --> 00:10:25.110 align:start position:0% looking forward to your technical talk and<00:10:23.959> thanks<00:10:24.279> you<00:10:24.399> know<00:10:24.519> thanks<00:10:24.720> very<00:10:24.839> much<00:10:24.959> for 00:10:25.110 --> 00:10:25.120 align:start position:0% and thanks you know thanks very much for 00:10:25.120 --> 00:10:28.030 align:start position:0% and thanks you know thanks very much for coming<00:10:25.600> all<00:10:25.720> right<00:10:25.920> thank<00:10:26.079> you<00:10:26.279> good<00:10:26.399> to<00:10:26.519> be 00:10:28.030 --> 00:10:28.040 align:start position:0% coming all right thank you good to be 00:10:28.040 --> 00:10:35.400 align:start position:0% coming all right thank you good to be here 00:10:35.400 --> 00:10:35.410 align:start position:0% 00:10:35.410 --> 00:10:38.610 align:start position:0% [Music]