WEBVTT Kind: captions Language: en 00:00:04.680 --> 00:00:14.950 align:start position:0% foreign 00:00:14.950 --> 00:00:14.960 align:start position:0% 00:00:14.960 --> 00:00:17.210 align:start position:0% developer<00:00:15.960> series<00:00:16.139> and<00:00:16.560> we<00:00:16.740> are<00:00:16.859> on<00:00:16.980> location 00:00:17.210 --> 00:00:17.220 align:start position:0% developer series and we are on location 00:00:17.220 --> 00:00:20.029 align:start position:0% developer series and we are on location in<00:00:18.119> Oakland<00:00:18.300> at<00:00:18.779> sungevity 00:00:20.029 --> 00:00:20.039 align:start position:0% in Oakland at sungevity 00:00:20.039 --> 00:00:24.170 align:start position:0% in Oakland at sungevity for<00:00:20.460> a<00:00:20.580> meet-up<00:00:20.960> with<00:00:22.160> folks<00:00:23.160> including<00:00:23.939> Chris 00:00:24.170 --> 00:00:24.180 align:start position:0% for a meet-up with folks including Chris 00:00:24.180 --> 00:00:27.410 align:start position:0% for a meet-up with folks including Chris Richardson<00:00:24.779> and<00:00:25.619> he<00:00:25.800> is<00:00:25.980> here<00:00:26.160> with<00:00:26.400> us<00:00:26.580> hi 00:00:27.410 --> 00:00:27.420 align:start position:0% Richardson and he is here with us hi 00:00:27.420 --> 00:00:30.650 align:start position:0% Richardson and he is here with us hi Chris<00:00:27.660> hi<00:00:28.439> how's<00:00:28.920> it<00:00:29.099> going<00:00:29.279> good<00:00:29.880> good<00:00:29.939> to 00:00:30.650 --> 00:00:30.660 align:start position:0% Chris hi how's it going good good to 00:00:30.660 --> 00:00:32.510 align:start position:0% Chris hi how's it going good good to have<00:00:30.720> you<00:00:30.840> with<00:00:31.019> us<00:00:31.140> so<00:00:31.679> Chris<00:00:31.920> is<00:00:32.220> going<00:00:32.460> to 00:00:32.510 --> 00:00:32.520 align:start position:0% have you with us so Chris is going to 00:00:32.520 --> 00:00:34.250 align:start position:0% have you with us so Chris is going to talk<00:00:32.640> about<00:00:32.759> microservices<00:00:33.600> and<00:00:33.960> even 00:00:34.250 --> 00:00:34.260 align:start position:0% talk about microservices and even 00:00:34.260 --> 00:00:36.950 align:start position:0% talk about microservices and even sourcing<00:00:34.800> but<00:00:35.219> Chris<00:00:35.820> is<00:00:36.000> known<00:00:36.239> as<00:00:36.540> the<00:00:36.719> one 00:00:36.950 --> 00:00:36.960 align:start position:0% sourcing but Chris is known as the one 00:00:36.960 --> 00:00:39.410 align:start position:0% sourcing but Chris is known as the one of<00:00:37.079> the<00:00:37.140> founders<00:00:37.440> of<00:00:37.620> cloud<00:00:37.860> Foundry<00:00:38.820> and<00:00:39.300> I 00:00:39.410 --> 00:00:39.420 align:start position:0% of the founders of cloud Foundry and I 00:00:39.420 --> 00:00:41.510 align:start position:0% of the founders of cloud Foundry and I wanted<00:00:39.540> to<00:00:39.780> ask<00:00:39.960> you<00:00:40.140> about<00:00:40.379> about<00:00:41.219> the 00:00:41.510 --> 00:00:41.520 align:start position:0% wanted to ask you about about the 00:00:41.520 --> 00:00:44.750 align:start position:0% wanted to ask you about about the history<00:00:41.760> and<00:00:42.800> where<00:00:43.800> is<00:00:43.980> cloud<00:00:44.160> Foundry<00:00:44.579> now 00:00:44.750 --> 00:00:44.760 align:start position:0% history and where is cloud Foundry now 00:00:44.760 --> 00:00:46.790 align:start position:0% history and where is cloud Foundry now and<00:00:45.059> basically<00:00:45.480> maybe<00:00:46.020> you<00:00:46.200> can<00:00:46.379> give<00:00:46.559> us<00:00:46.680> a 00:00:46.790 --> 00:00:46.800 align:start position:0% and basically maybe you can give us a 00:00:46.800 --> 00:00:48.770 align:start position:0% and basically maybe you can give us a little<00:00:46.860> background<00:00:47.280> for<00:00:47.760> uh<00:00:48.300> to<00:00:48.660> understand 00:00:48.770 --> 00:00:48.780 align:start position:0% little background for uh to understand 00:00:48.780 --> 00:00:51.170 align:start position:0% little background for uh to understand Canfield<00:00:49.440> trajectory<00:00:49.980> in<00:00:50.160> technology<00:00:50.399> sure 00:00:51.170 --> 00:00:51.180 align:start position:0% Canfield trajectory in technology sure 00:00:51.180 --> 00:00:53.270 align:start position:0% Canfield trajectory in technology sure well<00:00:51.480> I<00:00:51.719> should<00:00:51.840> begin<00:00:52.140> by<00:00:52.500> clarifying<00:00:53.100> it's 00:00:53.270 --> 00:00:53.280 align:start position:0% well I should begin by clarifying it's 00:00:53.280 --> 00:00:54.830 align:start position:0% well I should begin by clarifying it's actually<00:00:53.520> the<00:00:53.879> I<00:00:54.120> created<00:00:54.420> the<00:00:54.660> original 00:00:54.830 --> 00:00:54.840 align:start position:0% actually the I created the original 00:00:54.840 --> 00:00:57.049 align:start position:0% actually the I created the original cloud<00:00:55.379> Foundry<00:00:56.039> which<00:00:56.460> is<00:00:56.640> different 00:00:57.049 --> 00:00:57.059 align:start position:0% cloud Foundry which is different 00:00:57.059 --> 00:00:59.930 align:start position:0% cloud Foundry which is different technology<00:00:57.660> to<00:00:58.020> the<00:00:58.199> one<00:00:58.320> that<00:00:58.500> exists<00:00:58.920> today 00:00:59.930 --> 00:00:59.940 align:start position:0% technology to the one that exists today 00:00:59.940 --> 00:01:02.510 align:start position:0% technology to the one that exists today but<00:01:00.480> you<00:01:00.899> know<00:01:01.020> the<00:01:01.320> history<00:01:01.559> goes<00:01:02.280> all<00:01:02.399> the 00:01:02.510 --> 00:01:02.520 align:start position:0% but you know the history goes all the 00:01:02.520 --> 00:01:06.109 align:start position:0% but you know the history goes all the way<00:01:02.579> back<00:01:03.000> to<00:01:03.539> I<00:01:04.080> think<00:01:04.199> it<00:01:04.320> was<00:01:04.440> October<00:01:05.119> 2006 00:01:06.109 --> 00:01:06.119 align:start position:0% way back to I think it was October 2006 00:01:06.119 --> 00:01:09.530 align:start position:0% way back to I think it was October 2006 and<00:01:06.960> an<00:01:07.380> Amazon<00:01:07.680> evangelist<00:01:08.640> came<00:01:09.060> to<00:01:09.299> speak 00:01:09.530 --> 00:01:09.540 align:start position:0% and an Amazon evangelist came to speak 00:01:09.540 --> 00:01:11.870 align:start position:0% and an Amazon evangelist came to speak at<00:01:09.780> the<00:01:09.960> Oakland<00:01:10.140> Java<00:01:10.740> users<00:01:11.100> group 00:01:11.870 --> 00:01:11.880 align:start position:0% at the Oakland Java users group 00:01:11.880 --> 00:01:14.149 align:start position:0% at the Oakland Java users group and<00:01:12.780> we<00:01:13.080> thought<00:01:13.260> he<00:01:13.560> was<00:01:13.740> going<00:01:13.920> to<00:01:14.040> talk 00:01:14.149 --> 00:01:14.159 align:start position:0% and we thought he was going to talk 00:01:14.159 --> 00:01:16.670 align:start position:0% and we thought he was going to talk about<00:01:14.340> apis<00:01:15.060> for<00:01:15.420> buying<00:01:15.780> books<00:01:16.080> because<00:01:16.260> this 00:01:16.670 --> 00:01:16.680 align:start position:0% about apis for buying books because this 00:01:16.680 --> 00:01:19.130 align:start position:0% about apis for buying books because this was<00:01:16.860> like<00:01:17.100> part<00:01:17.520> of<00:01:17.700> a<00:01:17.880> series<00:01:18.060> of<00:01:18.479> talks<00:01:18.960> on 00:01:19.130 --> 00:01:19.140 align:start position:0% was like part of a series of talks on 00:01:19.140 --> 00:01:21.410 align:start position:0% was like part of a series of talks on while<00:01:19.740> web<00:01:20.220> services 00:01:21.410 --> 00:01:21.420 align:start position:0% while web services 00:01:21.420 --> 00:01:25.490 align:start position:0% while web services but<00:01:21.900> instead<00:01:22.200> of<00:01:22.380> a<00:01:22.680> book<00:01:23.240> apis<00:01:24.240> it<00:01:24.659> was<00:01:24.840> Amazon 00:01:25.490 --> 00:01:25.500 align:start position:0% but instead of a book apis it was Amazon 00:01:25.500 --> 00:01:27.170 align:start position:0% but instead of a book apis it was Amazon ec2 00:01:27.170 --> 00:01:27.180 align:start position:0% ec2 00:01:27.180 --> 00:01:30.469 align:start position:0% ec2 and<00:01:27.780> I<00:01:27.960> think<00:01:28.080> sqs<00:01:28.799> and<00:01:29.100> S3<00:01:29.520> and<00:01:29.820> it<00:01:30.060> was<00:01:30.240> like 00:01:30.469 --> 00:01:30.479 align:start position:0% and I think sqs and S3 and it was like 00:01:30.479 --> 00:01:33.770 align:start position:0% and I think sqs and S3 and it was like wow<00:01:31.020> you<00:01:31.380> can<00:01:31.560> rent<00:01:31.979> servers<00:01:32.700> by<00:01:32.939> the<00:01:33.180> hour<00:01:33.360> for 00:01:33.770 --> 00:01:33.780 align:start position:0% wow you can rent servers by the hour for 00:01:33.780 --> 00:01:36.710 align:start position:0% wow you can rent servers by the hour for and<00:01:34.080> pay<00:01:34.320> 10<00:01:34.619> cents<00:01:34.979> an<00:01:35.159> hour<00:01:35.340> mine<00:01:36.240> was<00:01:36.420> blown 00:01:36.710 --> 00:01:36.720 align:start position:0% and pay 10 cents an hour mine was blown 00:01:36.720 --> 00:01:38.450 align:start position:0% and pay 10 cents an hour mine was blown so<00:01:37.140> I<00:01:37.259> signed<00:01:37.560> up<00:01:37.619> for<00:01:37.799> the<00:01:37.920> beta<00:01:38.280> program 00:01:38.450 --> 00:01:38.460 align:start position:0% so I signed up for the beta program 00:01:38.460 --> 00:01:41.749 align:start position:0% so I signed up for the beta program which<00:01:38.759> I<00:01:38.939> got<00:01:39.060> access<00:01:39.299> to<00:01:39.720> 2007. 00:01:41.749 --> 00:01:41.759 align:start position:0% which I got access to 2007. 00:01:41.759 --> 00:01:44.149 align:start position:0% which I got access to 2007. and<00:01:42.600> that<00:01:42.900> turned<00:01:43.200> into<00:01:43.320> an<00:01:43.560> open<00:01:43.680> source 00:01:44.149 --> 00:01:44.159 align:start position:0% and that turned into an open source 00:01:44.159 --> 00:01:47.690 align:start position:0% and that turned into an open source project<00:01:44.340> Cloud<00:01:44.820> tools<00:01:45.420> which<00:01:45.979> evolved<00:01:46.979> into 00:01:47.690 --> 00:01:47.700 align:start position:0% project Cloud tools which evolved into 00:01:47.700 --> 00:01:50.450 align:start position:0% project Cloud tools which evolved into the<00:01:48.540> original<00:01:48.659> cloud<00:01:49.140> Foundry<00:01:49.740> which<00:01:50.040> was<00:01:50.220> a 00:01:50.450 --> 00:01:50.460 align:start position:0% the original cloud Foundry which was a 00:01:50.460 --> 00:01:53.270 align:start position:0% the original cloud Foundry which was a Java<00:01:50.939> paths<00:01:51.540> for<00:01:52.259> deploying<00:01:52.680> Java 00:01:53.270 --> 00:01:53.280 align:start position:0% Java paths for deploying Java 00:01:53.280 --> 00:01:56.569 align:start position:0% Java paths for deploying Java applications<00:01:53.880> on<00:01:54.540> Amazon<00:01:54.899> ec2<00:01:55.619> so<00:01:56.220> pretty 00:01:56.569 --> 00:01:56.579 align:start position:0% applications on Amazon ec2 so pretty 00:01:56.579 --> 00:01:59.210 align:start position:0% applications on Amazon ec2 so pretty much<00:01:56.700> it<00:01:57.060> just<00:01:57.299> automated<00:01:57.840> how<00:01:58.320> I<00:01:58.439> was<00:01:58.680> used<00:01:58.979> to 00:01:59.210 --> 00:01:59.220 align:start position:0% much it just automated how I was used to 00:01:59.220 --> 00:02:02.530 align:start position:0% much it just automated how I was used to deploying<00:01:59.759> apps<00:02:00.299> for<00:02:00.899> for<00:02:00.899> clients 00:02:02.530 --> 00:02:02.540 align:start position:0% deploying apps for for clients 00:02:02.540 --> 00:02:06.109 align:start position:0% deploying apps for for clients so<00:02:03.540> with<00:02:03.840> just<00:02:04.140> like<00:02:04.740> 11<00:02:05.159> clicks<00:02:05.700> of<00:02:05.880> the<00:02:06.000> mouse 00:02:06.109 --> 00:02:06.119 align:start position:0% so with just like 11 clicks of the mouse 00:02:06.119 --> 00:02:09.469 align:start position:0% so with just like 11 clicks of the mouse it<00:02:06.479> would<00:02:06.600> upload<00:02:07.020> your<00:02:07.320> War<00:02:07.619> file<00:02:08.119> and<00:02:09.119> spin 00:02:09.469 --> 00:02:09.479 align:start position:0% it would upload your War file and spin 00:02:09.479 --> 00:02:11.990 align:start position:0% it would upload your War file and spin up<00:02:09.599> a<00:02:09.840> bunch<00:02:10.020> of<00:02:10.200> ec2<00:02:10.739> instances<00:02:11.280> configure 00:02:11.990 --> 00:02:12.000 align:start position:0% up a bunch of ec2 instances configure 00:02:12.000 --> 00:02:15.650 align:start position:0% up a bunch of ec2 instances configure Apache<00:02:12.660> as<00:02:12.780> a<00:02:12.959> load<00:02:13.260> balancer<00:02:13.800> launch<00:02:14.760> one<00:02:15.540> or 00:02:15.650 --> 00:02:15.660 align:start position:0% Apache as a load balancer launch one or 00:02:15.660 --> 00:02:18.530 align:start position:0% Apache as a load balancer launch one or more<00:02:15.840> Tomcat<00:02:16.560> instances<00:02:17.099> and<00:02:17.819> also<00:02:18.120> set<00:02:18.360> up 00:02:18.530 --> 00:02:18.540 align:start position:0% more Tomcat instances and also set up 00:02:18.540 --> 00:02:22.550 align:start position:0% more Tomcat instances and also set up MySQL<00:02:19.700> with<00:02:20.700> Master<00:02:21.060> slaver<00:02:21.599> application<00:02:22.200> as 00:02:22.550 --> 00:02:22.560 align:start position:0% MySQL with Master slaver application as 00:02:22.560 --> 00:02:25.430 align:start position:0% MySQL with Master slaver application as well<00:02:22.739> so<00:02:23.400> it's<00:02:23.520> just<00:02:23.640> automating<00:02:24.180> what<00:02:24.720> what<00:02:24.959> I 00:02:25.430 --> 00:02:25.440 align:start position:0% well so it's just automating what what I 00:02:25.440 --> 00:02:28.490 align:start position:0% well so it's just automating what what I was<00:02:25.560> what<00:02:25.860> I'd<00:02:26.099> done<00:02:26.400> many<00:02:26.760> times<00:02:27.060> before 00:02:28.490 --> 00:02:28.500 align:start position:0% was what I'd done many times before 00:02:28.500 --> 00:02:30.890 align:start position:0% was what I'd done many times before why<00:02:28.980> 11<00:02:29.220> clicks 00:02:30.890 --> 00:02:30.900 align:start position:0% why 11 clicks 00:02:30.900 --> 00:02:33.830 align:start position:0% why 11 clicks why<00:02:31.560> why<00:02:31.620> not<00:02:32.160> one<00:02:32.400> click<00:02:32.640> well<00:02:33.480> you<00:02:33.599> had<00:02:33.720> to 00:02:33.830 --> 00:02:33.840 align:start position:0% why why not one click well you had to 00:02:33.840 --> 00:02:36.650 align:start position:0% why why not one click well you had to make<00:02:34.020> you 00:02:36.650 --> 00:02:36.660 align:start position:0% 00:02:36.660 --> 00:02:39.890 align:start position:0% yeah<00:02:37.040> I<00:02:38.040> think<00:02:38.099> yeah<00:02:38.400> I<00:02:38.879> mean<00:02:39.000> basically<00:02:39.420> you 00:02:39.890 --> 00:02:39.900 align:start position:0% yeah I think yeah I mean basically you 00:02:39.900 --> 00:02:41.809 align:start position:0% yeah I think yeah I mean basically you there<00:02:40.200> were<00:02:40.319> choices<00:02:40.739> you<00:02:41.040> had<00:02:41.220> to<00:02:41.400> make<00:02:41.519> one 00:02:41.809 --> 00:02:41.819 align:start position:0% there were choices you had to make one 00:02:41.819 --> 00:02:43.270 align:start position:0% there were choices you had to make one click<00:02:42.000> was<00:02:42.180> pattern<00:02:42.420> by<00:02:42.599> Amazon 00:02:43.270 --> 00:02:43.280 align:start position:0% click was pattern by Amazon 00:02:43.280 --> 00:02:46.729 align:start position:0% click was pattern by Amazon so<00:02:44.280> instead<00:02:45.120> of<00:02:45.180> one<00:02:45.360> it<00:02:45.660> was<00:02:45.780> one<00:02:46.019> one<00:02:46.319> right 00:02:46.729 --> 00:02:46.739 align:start position:0% so instead of one it was one one right 00:02:46.739 --> 00:02:49.729 align:start position:0% so instead of one it was one one right right 00:02:49.729 --> 00:02:49.739 align:start position:0% 00:02:49.739 --> 00:02:51.410 align:start position:0% so<00:02:49.920> this<00:02:50.220> is<00:02:50.400> actually<00:02:50.519> that's<00:02:51.180> very 00:02:51.410 --> 00:02:51.420 align:start position:0% so this is actually that's very 00:02:51.420 --> 00:02:53.150 align:start position:0% so this is actually that's very interesting<00:02:51.720> because<00:02:51.900> it's<00:02:52.140> early<00:02:52.319> days<00:02:52.620> I 00:02:53.150 --> 00:02:53.160 align:start position:0% interesting because it's early days I 00:02:53.160 --> 00:02:55.070 align:start position:0% interesting because it's early days I was<00:02:53.280> actually<00:02:53.400> at<00:02:53.580> Amazon<00:02:53.760> when<00:02:54.239> Amazon<00:02:54.660> was 00:02:55.070 --> 00:02:55.080 align:start position:0% was actually at Amazon when Amazon was 00:02:55.080 --> 00:02:58.070 align:start position:0% was actually at Amazon when Amazon was started<00:02:55.800> and<00:02:56.160> it<00:02:56.400> was<00:02:56.640> not<00:02:57.180> yet<00:02:57.420> clear<00:02:57.720> how 00:02:58.070 --> 00:02:58.080 align:start position:0% started and it was not yet clear how 00:02:58.080 --> 00:02:59.390 align:start position:0% started and it was not yet clear how people<00:02:58.260> can<00:02:58.500> use<00:02:58.620> it<00:02:58.739> so<00:02:58.860> you're<00:02:59.040> actually<00:02:59.160> one 00:02:59.390 --> 00:02:59.400 align:start position:0% people can use it so you're actually one 00:02:59.400 --> 00:03:02.270 align:start position:0% people can use it so you're actually one of<00:02:59.580> the<00:02:59.700> early<00:02:59.879> uh<00:03:00.660> yeah<00:03:01.140> I<00:03:01.500> mean<00:03:01.620> it's<00:03:01.920> sort<00:03:02.160> of 00:03:02.270 --> 00:03:02.280 align:start position:0% of the early uh yeah I mean it's sort of 00:03:02.280 --> 00:03:04.610 align:start position:0% of the early uh yeah I mean it's sort of you<00:03:02.400> look<00:03:02.580> back<00:03:02.879> and<00:03:03.120> it<00:03:03.480> was<00:03:03.599> this<00:03:03.959> obscure 00:03:04.610 --> 00:03:04.620 align:start position:0% you look back and it was this obscure 00:03:04.620 --> 00:03:08.390 align:start position:0% you look back and it was this obscure thing<00:03:05.220> right<00:03:05.819> you<00:03:06.360> know<00:03:06.480> ec2<00:03:07.319> what<00:03:08.040> the<00:03:08.160> heck 00:03:08.390 --> 00:03:08.400 align:start position:0% thing right you know ec2 what the heck 00:03:08.400 --> 00:03:11.210 align:start position:0% thing right you know ec2 what the heck is<00:03:08.580> that<00:03:08.819> right<00:03:09.360> and<00:03:10.080> I<00:03:10.379> don't<00:03:10.739> even<00:03:10.860> know<00:03:11.099> if 00:03:11.210 --> 00:03:11.220 align:start position:0% is that right and I don't even know if 00:03:11.220 --> 00:03:13.610 align:start position:0% is that right and I don't even know if the<00:03:11.340> term<00:03:11.519> cloud<00:03:11.879> computing<00:03:12.659> existed<00:03:13.319> back 00:03:13.610 --> 00:03:13.620 align:start position:0% the term cloud computing existed back 00:03:13.620 --> 00:03:16.550 align:start position:0% the term cloud computing existed back then<00:03:13.860> and<00:03:14.099> right<00:03:14.459> suddenly<00:03:15.180> womp<00:03:16.019> and<00:03:16.379> then 00:03:16.550 --> 00:03:16.560 align:start position:0% then and right suddenly womp and then 00:03:16.560 --> 00:03:18.589 align:start position:0% then and right suddenly womp and then you<00:03:16.739> know<00:03:16.860> then<00:03:17.040> there<00:03:17.159> was<00:03:17.340> all<00:03:17.519> these<00:03:17.819> like 00:03:18.589 --> 00:03:18.599 align:start position:0% you know then there was all these like 00:03:18.599 --> 00:03:21.290 align:start position:0% you know then there was all these like Cloud<00:03:18.959> camps<00:03:19.620> where<00:03:19.860> people<00:03:20.159> sat<00:03:20.519> around<00:03:20.819> and 00:03:21.290 --> 00:03:21.300 align:start position:0% Cloud camps where people sat around and 00:03:21.300 --> 00:03:23.030 align:start position:0% Cloud camps where people sat around and discussed<00:03:21.780> what's<00:03:22.080> the<00:03:22.260> meaning<00:03:22.440> of<00:03:22.800> cloud 00:03:23.030 --> 00:03:23.040 align:start position:0% discussed what's the meaning of cloud 00:03:23.040 --> 00:03:25.610 align:start position:0% discussed what's the meaning of cloud computing<00:03:23.760> right<00:03:24.000> that's<00:03:24.599> right<00:03:24.840> in<00:03:25.379> the<00:03:25.500> end 00:03:25.610 --> 00:03:25.620 align:start position:0% computing right that's right in the end 00:03:25.620 --> 00:03:27.290 align:start position:0% computing right that's right in the end I<00:03:25.800> just<00:03:25.920> got<00:03:26.040> fed<00:03:26.280> up<00:03:26.459> with<00:03:26.580> that<00:03:26.760> and<00:03:26.940> I<00:03:27.120> just 00:03:27.290 --> 00:03:27.300 align:start position:0% I just got fed up with that and I just 00:03:27.300 --> 00:03:31.190 align:start position:0% I just got fed up with that and I just decided<00:03:27.780> I<00:03:28.319> like<00:03:28.500> AWS<00:03:29.400> I<00:03:30.000> don't<00:03:30.120> care<00:03:30.360> what<00:03:31.019> you 00:03:31.190 --> 00:03:31.200 align:start position:0% decided I like AWS I don't care what you 00:03:31.200 --> 00:03:33.649 align:start position:0% decided I like AWS I don't care what you label<00:03:31.560> it<00:03:31.739> but<00:03:32.040> it's<00:03:32.280> useful<00:03:32.760> and 00:03:33.649 --> 00:03:33.659 align:start position:0% label it but it's useful and 00:03:33.659 --> 00:03:36.350 align:start position:0% label it but it's useful and yeah<00:03:34.200> so<00:03:35.099> now<00:03:35.220> you<00:03:35.519> know<00:03:35.640> given<00:03:36.000> this<00:03:36.120> history 00:03:36.350 --> 00:03:36.360 align:start position:0% yeah so now you know given this history 00:03:36.360 --> 00:03:38.830 align:start position:0% yeah so now you know given this history the<00:03:36.840> microservices<00:03:37.680> interest<00:03:38.040> actually 00:03:38.830 --> 00:03:38.840 align:start position:0% the microservices interest actually 00:03:38.840 --> 00:03:41.390 align:start position:0% the microservices interest actually Focus<00:03:39.840> right<00:03:40.080> because<00:03:40.200> it's<00:03:40.379> kind<00:03:40.560> of<00:03:40.680> it<00:03:40.920> to 00:03:41.390 --> 00:03:41.400 align:start position:0% Focus right because it's kind of it to 00:03:41.400 --> 00:03:42.949 align:start position:0% Focus right because it's kind of it to me<00:03:41.519> it<00:03:41.580> seems<00:03:41.879> very<00:03:42.060> logical 00:03:42.949 --> 00:03:42.959 align:start position:0% me it seems very logical 00:03:42.959 --> 00:03:46.070 align:start position:0% me it seems very logical stemming<00:03:43.680> from<00:03:43.860> from<00:03:44.099> that<00:03:44.340> but<00:03:44.640> maybe<00:03:45.080> you 00:03:46.070 --> 00:03:46.080 align:start position:0% stemming from from that but maybe you 00:03:46.080 --> 00:03:47.110 align:start position:0% stemming from from that but maybe you can<00:03:46.140> kind<00:03:46.379> of 00:03:47.110 --> 00:03:47.120 align:start position:0% can kind of 00:03:47.120 --> 00:03:49.850 align:start position:0% can kind of say<00:03:48.120> for<00:03:48.299> yourself<00:03:48.480> how<00:03:48.840> how<00:03:49.200> did<00:03:49.440> you<00:03:49.560> arrive 00:03:49.850 --> 00:03:49.860 align:start position:0% say for yourself how how did you arrive 00:03:49.860 --> 00:03:51.289 align:start position:0% say for yourself how how did you arrive at<00:03:49.980> this<00:03:50.099> interest<00:03:50.220> in<00:03:50.459> microservices<00:03:51.000> you 00:03:51.289 --> 00:03:51.299 align:start position:0% at this interest in microservices you 00:03:51.299 --> 00:03:54.050 align:start position:0% at this interest in microservices you presented<00:03:51.720> that<00:03:51.959> last<00:03:52.200> year<00:03:52.500> uh<00:03:53.340> scholar<00:03:53.879> by 00:03:54.050 --> 00:03:54.060 align:start position:0% presented that last year uh scholar by 00:03:54.060 --> 00:03:55.369 align:start position:0% presented that last year uh scholar by the<00:03:54.180> Bay 00:03:55.369 --> 00:03:55.379 align:start position:0% the Bay 00:03:55.379 --> 00:03:58.009 align:start position:0% the Bay well<00:03:56.040> I<00:03:56.879> think<00:03:57.060> that<00:03:57.420> there's<00:03:57.720> a<00:03:57.900> certain 00:03:58.009 --> 00:03:58.019 align:start position:0% well I think that there's a certain 00:03:58.019 --> 00:04:02.229 align:start position:0% well I think that there's a certain inevitability<00:03:58.920> that<00:03:59.400> if<00:03:59.580> you<00:03:59.879> build<00:04:00.299> a 00:04:02.229 --> 00:04:02.239 align:start position:0% inevitability that if you build a 00:04:02.239 --> 00:04:05.470 align:start position:0% inevitability that if you build a cartilage<00:04:03.239> complex<00:04:04.080> enough<00:04:04.440> application 00:04:05.470 --> 00:04:05.480 align:start position:0% cartilage complex enough application 00:04:05.480 --> 00:04:08.410 align:start position:0% cartilage complex enough application you're<00:04:06.480> going<00:04:06.659> to<00:04:06.780> want<00:04:06.959> to<00:04:07.200> adopt<00:04:07.739> a<00:04:08.040> service 00:04:08.410 --> 00:04:08.420 align:start position:0% you're going to want to adopt a service 00:04:08.420 --> 00:04:11.830 align:start position:0% you're going to want to adopt a service quote<00:04:09.420> a<00:04:09.659> service<00:04:10.019> oriented<00:04:10.799> lowercase 00:04:11.830 --> 00:04:11.840 align:start position:0% quote a service oriented lowercase 00:04:11.840 --> 00:04:14.170 align:start position:0% quote a service oriented lowercase architecture<00:04:12.840> right<00:04:13.140> and<00:04:13.500> in<00:04:13.680> other<00:04:13.860> words 00:04:14.170 --> 00:04:14.180 align:start position:0% architecture right and in other words 00:04:14.180 --> 00:04:17.349 align:start position:0% architecture right and in other words microservices<00:04:15.180> because<00:04:16.139> a<00:04:16.620> complex 00:04:17.349 --> 00:04:17.359 align:start position:0% microservices because a complex 00:04:17.359 --> 00:04:20.210 align:start position:0% microservices because a complex monolithic<00:04:18.359> application<00:04:18.959> is<00:04:19.500> just<00:04:19.799> too<00:04:20.040> much 00:04:20.210 --> 00:04:20.220 align:start position:0% monolithic application is just too much 00:04:20.220 --> 00:04:23.510 align:start position:0% monolithic application is just too much of<00:04:20.400> a<00:04:20.519> headache<00:04:21.260> and<00:04:22.260> you<00:04:22.620> know<00:04:22.680> I<00:04:22.800> think<00:04:22.979> when 00:04:23.510 --> 00:04:23.520 align:start position:0% of a headache and you know I think when 00:04:23.520 --> 00:04:25.430 align:start position:0% of a headache and you know I think when I<00:04:23.699> give<00:04:23.880> talks<00:04:24.360> there's<00:04:24.660> always<00:04:24.840> people<00:04:25.139> in 00:04:25.430 --> 00:04:25.440 align:start position:0% I give talks there's always people in 00:04:25.440 --> 00:04:28.670 align:start position:0% I give talks there's always people in the<00:04:25.620> crowd<00:04:25.979> who<00:04:26.520> have<00:04:27.419> to<00:04:27.600> deal<00:04:27.900> with<00:04:28.259> large 00:04:28.670 --> 00:04:28.680 align:start position:0% the crowd who have to deal with large 00:04:28.680 --> 00:04:31.370 align:start position:0% the crowd who have to deal with large complex<00:04:29.220> monolithic<00:04:30.120> applications<00:04:30.720> and<00:04:31.139> it's 00:04:31.370 --> 00:04:31.380 align:start position:0% complex monolithic applications and it's 00:04:31.380 --> 00:04:34.189 align:start position:0% complex monolithic applications and it's incredibly<00:04:31.860> painful<00:04:32.460> for<00:04:32.820> them<00:04:33.000> right<00:04:33.300> so<00:04:33.780> so 00:04:34.189 --> 00:04:34.199 align:start position:0% incredibly painful for them right so so 00:04:34.199 --> 00:04:36.770 align:start position:0% incredibly painful for them right so so it's<00:04:34.440> just<00:04:34.680> sort<00:04:34.860> of<00:04:34.979> a<00:04:35.220> natural<00:04:35.780> evolutionary 00:04:36.770 --> 00:04:36.780 align:start position:0% it's just sort of a natural evolutionary 00:04:36.780 --> 00:04:39.050 align:start position:0% it's just sort of a natural evolutionary step<00:04:37.139> that<00:04:37.560> you<00:04:37.740> want<00:04:37.860> to<00:04:37.979> have<00:04:38.280> in<00:04:38.520> what's 00:04:39.050 --> 00:04:39.060 align:start position:0% step that you want to have in what's 00:04:39.060 --> 00:04:40.790 align:start position:0% step that you want to have in what's what's<00:04:39.300> now<00:04:39.600> called<00:04:39.900> a<00:04:40.199> microservice 00:04:40.790 --> 00:04:40.800 align:start position:0% what's now called a microservice 00:04:40.800 --> 00:04:43.550 align:start position:0% what's now called a microservice architecture<00:04:42.120> when<00:04:42.540> I<00:04:42.780> think<00:04:42.900> that<00:04:43.139> and 00:04:43.550 --> 00:04:43.560 align:start position:0% architecture when I think that and 00:04:43.560 --> 00:04:45.710 align:start position:0% architecture when I think that and unfortunately<00:04:44.100> I'd<00:04:44.520> much<00:04:44.940> rather<00:04:45.240> it<00:04:45.479> be 00:04:45.710 --> 00:04:45.720 align:start position:0% unfortunately I'd much rather it be 00:04:45.720 --> 00:04:49.430 align:start position:0% unfortunately I'd much rather it be called<00:04:45.960> a<00:04:46.259> service<00:04:46.560> oriented<00:04:47.340> architecture 00:04:49.430 --> 00:04:49.440 align:start position:0% called a service oriented architecture 00:04:49.440 --> 00:04:50.270 align:start position:0% called a service oriented architecture um 00:04:50.270 --> 00:04:50.280 align:start position:0% um 00:04:50.280 --> 00:04:52.790 align:start position:0% um because<00:04:50.660> microservices<00:04:51.660> places<00:04:52.139> too<00:04:52.620> much 00:04:52.790 --> 00:04:52.800 align:start position:0% because microservices places too much 00:04:52.800 --> 00:04:55.430 align:start position:0% because microservices places too much emphasis<00:04:53.340> on<00:04:53.699> micro<00:04:54.120> and<00:04:54.780> not<00:04:54.960> enough<00:04:55.139> on 00:04:55.430 --> 00:04:55.440 align:start position:0% emphasis on micro and not enough on 00:04:55.440 --> 00:04:56.990 align:start position:0% emphasis on micro and not enough on services<00:04:55.680> but<00:04:56.100> the<00:04:56.220> trouble<00:04:56.400> with<00:04:56.699> service 00:04:56.990 --> 00:04:57.000 align:start position:0% services but the trouble with service 00:04:57.000 --> 00:04:58.969 align:start position:0% services but the trouble with service oriented<00:04:57.600> architecture<00:04:58.259> is<00:04:58.440> that<00:04:58.620> it<00:04:58.800> just 00:04:58.969 --> 00:04:58.979 align:start position:0% oriented architecture is that it just 00:04:58.979 --> 00:05:01.249 align:start position:0% oriented architecture is that it just has<00:04:59.160> way<00:04:59.400> too<00:04:59.580> much<00:04:59.759> baggage<00:05:00.240> associated<00:05:00.900> with 00:05:01.249 --> 00:05:01.259 align:start position:0% has way too much baggage associated with 00:05:01.259 --> 00:05:05.210 align:start position:0% has way too much baggage associated with it<00:05:01.440> right<00:05:01.560> yeah<00:05:02.000> like<00:05:03.000> will<00:05:03.600> the<00:05:03.840> Ws<00:05:04.380> star<00:05:04.860> and 00:05:05.210 --> 00:05:05.220 align:start position:0% it right yeah like will the Ws star and 00:05:05.220 --> 00:05:09.110 align:start position:0% it right yeah like will the Ws star and esbs<00:05:06.060> and<00:05:06.360> all<00:05:06.479> that<00:05:06.780> kind<00:05:07.139> of<00:05:07.320> kind<00:05:08.160> well<00:05:08.520> crap 00:05:09.110 --> 00:05:09.120 align:start position:0% esbs and all that kind of kind well crap 00:05:09.120 --> 00:05:10.670 align:start position:0% esbs and all that kind of kind well crap basically 00:05:10.670 --> 00:05:10.680 align:start position:0% basically 00:05:10.680 --> 00:05:12.050 align:start position:0% basically so<00:05:11.160> why<00:05:11.340> are<00:05:11.460> we<00:05:11.520> going<00:05:11.639> to<00:05:11.699> go<00:05:11.880> from 00:05:12.050 --> 00:05:12.060 align:start position:0% so why are we going to go from 00:05:12.060 --> 00:05:15.550 align:start position:0% so why are we going to go from microservices<00:05:12.540> to<00:05:12.780> melee<00:05:13.139> services 00:05:15.550 --> 00:05:15.560 align:start position:0% 00:05:15.560 --> 00:05:18.290 align:start position:0% like<00:05:16.560> how<00:05:16.740> much<00:05:16.860> weight<00:05:17.400> should<00:05:17.880> we<00:05:18.000> put<00:05:18.120> on 00:05:18.290 --> 00:05:18.300 align:start position:0% like how much weight should we put on 00:05:18.300 --> 00:05:19.850 align:start position:0% like how much weight should we put on micro<00:05:18.479> and<00:05:19.020> how<00:05:19.199> do<00:05:19.320> we<00:05:19.380> Define<00:05:19.500> that<00:05:19.740> because 00:05:19.850 --> 00:05:19.860 align:start position:0% micro and how do we Define that because 00:05:19.860 --> 00:05:21.230 align:start position:0% micro and how do we Define that because different<00:05:20.100> people<00:05:20.400> mean<00:05:20.759> different<00:05:21.000> things 00:05:21.230 --> 00:05:21.240 align:start position:0% different people mean different things 00:05:21.240 --> 00:05:23.629 align:start position:0% different people mean different things yeah<00:05:21.419> one<00:05:22.259> source<00:05:22.620> of<00:05:22.740> inspiration<00:05:23.220> for<00:05:23.520> me 00:05:23.629 --> 00:05:23.639 align:start position:0% yeah one source of inspiration for me 00:05:23.639 --> 00:05:25.010 align:start position:0% yeah one source of inspiration for me that<00:05:24.000> was<00:05:24.180> this<00:05:24.300> book<00:05:24.479> The<00:05:24.720> Art<00:05:24.840> of 00:05:25.010 --> 00:05:25.020 align:start position:0% that was this book The Art of 00:05:25.020 --> 00:05:26.930 align:start position:0% that was this book The Art of scalability<00:05:25.620> and<00:05:25.919> in<00:05:26.100> the<00:05:26.280> book<00:05:26.400> they<00:05:26.759> have 00:05:26.930 --> 00:05:26.940 align:start position:0% scalability and in the book they have 00:05:26.940 --> 00:05:28.610 align:start position:0% scalability and in the book they have the<00:05:27.240> scale<00:05:27.539> queue 00:05:28.610 --> 00:05:28.620 align:start position:0% the scale queue 00:05:28.620 --> 00:05:30.350 align:start position:0% the scale queue um<00:05:28.680> with<00:05:28.919> three-dimensional<00:05:29.699> model<00:05:30.000> for 00:05:30.350 --> 00:05:30.360 align:start position:0% um with three-dimensional model for 00:05:30.360 --> 00:05:32.990 align:start position:0% um with three-dimensional model for scaling<00:05:30.900> applications<00:05:31.440> and<00:05:32.039> and<00:05:32.340> what<00:05:32.759> what 00:05:32.990 --> 00:05:33.000 align:start position:0% scaling applications and and what what 00:05:33.000 --> 00:05:35.510 align:start position:0% scaling applications and and what what they<00:05:33.240> call<00:05:33.419> y-axis<00:05:34.259> scaling<00:05:34.800> goes<00:05:35.160> by<00:05:35.280> the 00:05:35.510 --> 00:05:35.520 align:start position:0% they call y-axis scaling goes by the 00:05:35.520 --> 00:05:38.330 align:start position:0% they call y-axis scaling goes by the name<00:05:35.639> of<00:05:35.820> functional<00:05:36.360> decomposition<00:05:37.340> which 00:05:38.330 --> 00:05:38.340 align:start position:0% name of functional decomposition which 00:05:38.340 --> 00:05:40.670 align:start position:0% name of functional decomposition which is<00:05:38.520> basically<00:05:38.940> just<00:05:39.419> breaking<00:05:39.900> up<00:05:40.080> your<00:05:40.380> app 00:05:40.670 --> 00:05:40.680 align:start position:0% is basically just breaking up your app 00:05:40.680 --> 00:05:42.770 align:start position:0% is basically just breaking up your app by<00:05:41.400> function 00:05:42.770 --> 00:05:42.780 align:start position:0% by function 00:05:42.780 --> 00:05:45.129 align:start position:0% by function um in<00:05:43.080> some<00:05:43.259> sort<00:05:43.500> of<00:05:43.560> meaningful<00:05:44.039> way 00:05:45.129 --> 00:05:45.139 align:start position:0% um in some sort of meaningful way 00:05:45.139 --> 00:05:47.510 align:start position:0% um in some sort of meaningful way and<00:05:46.139> that<00:05:46.259> that<00:05:46.440> to<00:05:46.740> me<00:05:46.860> is<00:05:47.160> what 00:05:47.510 --> 00:05:47.520 align:start position:0% and that that to me is what 00:05:47.520 --> 00:05:49.969 align:start position:0% and that that to me is what microservices<00:05:48.419> is<00:05:48.660> all<00:05:49.139> about<00:05:49.259> functional 00:05:49.969 --> 00:05:49.979 align:start position:0% microservices is all about functional 00:05:49.979 --> 00:05:52.790 align:start position:0% microservices is all about functional decomposition<00:05:50.820> of<00:05:51.060> your<00:05:51.180> app<00:05:51.479> and<00:05:52.259> you<00:05:52.440> do<00:05:52.620> it 00:05:52.790 --> 00:05:52.800 align:start position:0% decomposition of your app and you do it 00:05:52.800 --> 00:05:55.330 align:start position:0% decomposition of your app and you do it in<00:05:52.979> order<00:05:53.160> to<00:05:53.580> solve<00:05:54.060> problems 00:05:55.330 --> 00:05:55.340 align:start position:0% in order to solve problems 00:05:55.340 --> 00:05:58.550 align:start position:0% in order to solve problems around<00:05:56.340> development<00:05:57.180> and<00:05:57.479> deployment<00:05:58.080> and 00:05:58.550 --> 00:05:58.560 align:start position:0% around development and deployment and 00:05:58.560 --> 00:06:02.510 align:start position:0% around development and deployment and scaling<00:05:59.419> and<00:06:00.419> as<00:06:00.840> opposed<00:06:01.259> to<00:06:01.320> just<00:06:01.800> doing<00:06:02.280> it 00:06:02.510 --> 00:06:02.520 align:start position:0% scaling and as opposed to just doing it 00:06:02.520 --> 00:06:04.430 align:start position:0% scaling and as opposed to just doing it for<00:06:02.759> the<00:06:02.940> sake<00:06:03.060> of<00:06:03.360> having<00:06:03.539> lots<00:06:04.020> of<00:06:04.139> small 00:06:04.430 --> 00:06:04.440 align:start position:0% for the sake of having lots of small 00:06:04.440 --> 00:06:07.189 align:start position:0% for the sake of having lots of small services<00:06:04.800> so<00:06:05.580> basically<00:06:05.940> I<00:06:06.240> see<00:06:06.360> so<00:06:06.539> micro<00:06:06.780> in 00:06:07.189 --> 00:06:07.199 align:start position:0% services so basically I see so micro in 00:06:07.199 --> 00:06:10.249 align:start position:0% services so basically I see so micro in your<00:06:07.380> uh<00:06:08.240> sounds<00:06:09.240> would<00:06:09.600> mean<00:06:09.780> kind<00:06:10.139> of 00:06:10.249 --> 00:06:10.259 align:start position:0% your uh sounds would mean kind of 00:06:10.259 --> 00:06:12.790 align:start position:0% your uh sounds would mean kind of logical<00:06:10.680> logically<00:06:11.520> separate<00:06:12.000> orthogonal 00:06:12.790 --> 00:06:12.800 align:start position:0% logical logically separate orthogonal 00:06:12.800 --> 00:06:15.110 align:start position:0% logical logically separate orthogonal service<00:06:13.800> which<00:06:14.100> can<00:06:14.280> be<00:06:14.400> composed<00:06:14.820> with<00:06:14.940> other 00:06:15.110 --> 00:06:15.120 align:start position:0% service which can be composed with other 00:06:15.120 --> 00:06:17.930 align:start position:0% service which can be composed with other services<00:06:15.419> yeah<00:06:15.840> but<00:06:16.440> but<00:06:16.740> only<00:06:17.100> break<00:06:17.639> things 00:06:17.930 --> 00:06:17.940 align:start position:0% services yeah but but only break things 00:06:17.940 --> 00:06:21.110 align:start position:0% services yeah but but only break things up<00:06:18.240> enough<00:06:18.479> to<00:06:19.020> solve<00:06:19.380> problems<00:06:19.860> not<00:06:20.280> not<00:06:20.580> just 00:06:21.110 --> 00:06:21.120 align:start position:0% up enough to solve problems not not just 00:06:21.120 --> 00:06:23.210 align:start position:0% up enough to solve problems not not just because<00:06:21.600> you've<00:06:22.080> got<00:06:22.319> the<00:06:22.620> micro<00:06:22.800> service 00:06:23.210 --> 00:06:23.220 align:start position:0% because you've got the micro service 00:06:23.220 --> 00:06:26.029 align:start position:0% because you've got the micro service religion<00:06:24.000> okay<00:06:24.780> so<00:06:25.199> another<00:06:25.319> thing<00:06:25.620> you<00:06:25.740> do<00:06:25.919> is 00:06:26.029 --> 00:06:26.039 align:start position:0% religion okay so another thing you do is 00:06:26.039 --> 00:06:27.890 align:start position:0% religion okay so another thing you do is spring<00:06:26.280> and<00:06:26.520> so<00:06:26.699> I<00:06:26.819> want<00:06:26.940> to<00:06:27.000> crawl<00:06:27.360> spring<00:06:27.539> and 00:06:27.890 --> 00:06:27.900 align:start position:0% spring and so I want to crawl spring and 00:06:27.900 --> 00:06:30.350 align:start position:0% spring and so I want to crawl spring and call<00:06:28.080> Foundry<00:06:28.620> fit<00:06:29.220> together<00:06:29.400> and<00:06:30.060> basically 00:06:30.350 --> 00:06:30.360 align:start position:0% call Foundry fit together and basically 00:06:30.360 --> 00:06:32.510 align:start position:0% call Foundry fit together and basically what's<00:06:30.720> the<00:06:30.960> relationship<00:06:31.380> of<00:06:31.740> all<00:06:31.979> of<00:06:32.160> those 00:06:32.510 --> 00:06:32.520 align:start position:0% what's the relationship of all of those 00:06:32.520 --> 00:06:34.909 align:start position:0% what's the relationship of all of those to<00:06:32.759> the<00:06:32.940> cloud<00:06:33.180> Foundry<00:06:33.720> exists<00:06:34.380> today<00:06:34.560> with 00:06:34.909 --> 00:06:34.919 align:start position:0% to the cloud Foundry exists today with 00:06:34.919 --> 00:06:36.350 align:start position:0% to the cloud Foundry exists today with with<00:06:35.160> pivotal 00:06:36.350 --> 00:06:36.360 align:start position:0% with pivotal 00:06:36.360 --> 00:06:40.129 align:start position:0% with pivotal oh<00:06:37.160> well<00:06:38.360> so<00:06:39.360> if<00:06:39.479> you<00:06:39.600> think<00:06:39.780> about<00:06:39.840> a 00:06:40.129 --> 00:06:40.139 align:start position:0% oh well so if you think about a 00:06:40.139 --> 00:06:42.890 align:start position:0% oh well so if you think about a microservice<00:06:40.940> application<00:06:41.940> there's<00:06:42.600> a<00:06:42.780> lot 00:06:42.890 --> 00:06:42.900 align:start position:0% microservice application there's a lot 00:06:42.900 --> 00:06:46.790 align:start position:0% microservice application there's a lot of<00:06:43.020> moving<00:06:43.500> Parts<00:06:44.240> whereas<00:06:45.240> before<00:06:45.680> you<00:06:46.680> could 00:06:46.790 --> 00:06:46.800 align:start position:0% of moving Parts whereas before you could 00:06:46.800 --> 00:06:49.610 align:start position:0% of moving Parts whereas before you could just<00:06:47.100> take<00:06:47.460> your<00:06:47.759> one<00:06:48.000> large<00:06:48.240> War<00:06:48.660> file<00:06:49.020> copy 00:06:49.610 --> 00:06:49.620 align:start position:0% just take your one large War file copy 00:06:49.620 --> 00:06:52.790 align:start position:0% just take your one large War file copy it<00:06:49.740> onto<00:06:50.039> tomcat<00:06:50.580> and<00:06:51.120> and<00:06:51.419> maybe<00:06:52.020> multiple 00:06:52.790 --> 00:06:52.800 align:start position:0% it onto tomcat and and maybe multiple 00:06:52.800 --> 00:06:54.529 align:start position:0% it onto tomcat and and maybe multiple Tomcats<00:06:53.520> And<00:06:53.639> you<00:06:53.759> had<00:06:53.940> a<00:06:54.120> running<00:06:54.240> app 00:06:54.529 --> 00:06:54.539 align:start position:0% Tomcats And you had a running app 00:06:54.539 --> 00:06:56.809 align:start position:0% Tomcats And you had a running app whereas<00:06:55.380> now<00:06:55.560> if<00:06:55.800> we've<00:06:56.039> got<00:06:56.160> multiple 00:06:56.809 --> 00:06:56.819 align:start position:0% whereas now if we've got multiple 00:06:56.819 --> 00:06:58.969 align:start position:0% whereas now if we've got multiple services<00:06:57.180> in<00:06:57.660> each<00:06:57.840> of<00:06:58.020> those<00:06:58.139> Services<00:06:58.440> need 00:06:58.969 --> 00:06:58.979 align:start position:0% services in each of those Services need 00:06:58.979 --> 00:07:01.249 align:start position:0% services in each of those Services need to<00:06:59.160> be<00:06:59.280> replicated<00:06:59.880> for<00:07:00.300> availability<00:07:00.840> and 00:07:01.249 --> 00:07:01.259 align:start position:0% to be replicated for availability and 00:07:01.259 --> 00:07:03.350 align:start position:0% to be replicated for availability and throughput<00:07:01.800> you've<00:07:02.460> got<00:07:02.520> an<00:07:02.759> awful<00:07:03.000> lot<00:07:03.180> of 00:07:03.350 --> 00:07:03.360 align:start position:0% throughput you've got an awful lot of 00:07:03.360 --> 00:07:05.210 align:start position:0% throughput you've got an awful lot of moving<00:07:03.720> parts 00:07:05.210 --> 00:07:05.220 align:start position:0% moving parts 00:07:05.220 --> 00:07:08.689 align:start position:0% moving parts and<00:07:05.940> so<00:07:06.120> you<00:07:06.539> need<00:07:07.080> some<00:07:07.500> level<00:07:07.740> of<00:07:08.100> Automation 00:07:08.689 --> 00:07:08.699 align:start position:0% and so you need some level of Automation 00:07:08.699 --> 00:07:12.290 align:start position:0% and so you need some level of Automation in<00:07:09.660> order<00:07:09.840> to<00:07:10.380> make<00:07:10.919> your<00:07:11.220> make<00:07:11.580> deployment 00:07:12.290 --> 00:07:12.300 align:start position:0% in order to make your make deployment 00:07:12.300 --> 00:07:14.290 align:start position:0% in order to make your make deployment sort<00:07:12.840> of<00:07:12.960> practical 00:07:14.290 --> 00:07:14.300 align:start position:0% sort of practical 00:07:14.300 --> 00:07:17.930 align:start position:0% sort of practical and<00:07:15.300> so<00:07:15.419> one<00:07:15.720> answer<00:07:15.960> to<00:07:16.199> that<00:07:16.380> is<00:07:16.620> obviously<00:07:17.100> a 00:07:17.930 --> 00:07:17.940 align:start position:0% and so one answer to that is obviously a 00:07:17.940 --> 00:07:20.570 align:start position:0% and so one answer to that is obviously a path<00:07:18.600> such<00:07:18.840> as<00:07:19.020> Cloud<00:07:19.199> Foundry<00:07:19.800> another 00:07:20.570 --> 00:07:20.580 align:start position:0% path such as Cloud Foundry another 00:07:20.580 --> 00:07:23.029 align:start position:0% path such as Cloud Foundry another answer<00:07:21.000> actually<00:07:21.360> is<00:07:21.720> some<00:07:22.080> of<00:07:22.199> the<00:07:22.560> docker 00:07:23.029 --> 00:07:23.039 align:start position:0% answer actually is some of the docker 00:07:23.039 --> 00:07:25.089 align:start position:0% answer actually is some of the docker clustering<00:07:23.759> technology 00:07:25.089 --> 00:07:25.099 align:start position:0% clustering technology 00:07:25.099 --> 00:07:28.550 align:start position:0% clustering technology like<00:07:26.099> kubernetes 00:07:28.550 --> 00:07:28.560 align:start position:0% like kubernetes 00:07:28.560 --> 00:07:31.490 align:start position:0% like kubernetes or<00:07:29.160> Marathon<00:07:30.000> or<00:07:30.300> you<00:07:30.660> know<00:07:30.780> anything<00:07:31.139> that 00:07:31.490 --> 00:07:31.500 align:start position:0% or Marathon or you know anything that 00:07:31.500 --> 00:07:33.830 align:start position:0% or Marathon or you know anything that sort<00:07:31.680> of<00:07:31.800> automates<00:07:32.340> clustering<00:07:33.060> of<00:07:33.240> things 00:07:33.830 --> 00:07:33.840 align:start position:0% sort of automates clustering of things 00:07:33.840 --> 00:07:35.809 align:start position:0% sort of automates clustering of things and<00:07:34.139> has<00:07:34.440> built-in<00:07:35.039> support<00:07:35.280> for<00:07:35.580> dark 00:07:35.809 --> 00:07:35.819 align:start position:0% and has built-in support for dark 00:07:35.819 --> 00:07:38.150 align:start position:0% and has built-in support for dark ratings<00:07:36.300> kind<00:07:36.780> of<00:07:36.960> quite<00:07:37.680> a<00:07:37.800> powerful 00:07:38.150 --> 00:07:38.160 align:start position:0% ratings kind of quite a powerful 00:07:38.160 --> 00:07:40.010 align:start position:0% ratings kind of quite a powerful deployment<00:07:38.639> option<00:07:39.000> but<00:07:39.180> the<00:07:39.360> key<00:07:39.840> is 00:07:40.010 --> 00:07:40.020 align:start position:0% deployment option but the key is 00:07:40.020 --> 00:07:42.589 align:start position:0% deployment option but the key is automation<00:07:40.740> yes 00:07:42.589 --> 00:07:42.599 align:start position:0% automation yes 00:07:42.599 --> 00:07:45.409 align:start position:0% automation yes um<00:07:42.720> and<00:07:43.080> then<00:07:43.259> you're<00:07:43.319> asking<00:07:43.620> about<00:07:43.800> spring 00:07:45.409 --> 00:07:45.419 align:start position:0% um and then you're asking about spring 00:07:45.419 --> 00:07:47.330 align:start position:0% um and then you're asking about spring um<00:07:45.539> yeah<00:07:46.020> it's<00:07:46.259> funny<00:07:46.380> right<00:07:46.620> I've<00:07:46.860> been<00:07:47.039> using 00:07:47.330 --> 00:07:47.340 align:start position:0% um yeah it's funny right I've been using 00:07:47.340 --> 00:07:51.710 align:start position:0% um yeah it's funny right I've been using spring<00:07:48.139> for<00:07:49.139> a<00:07:49.919> really<00:07:50.039> long<00:07:50.460> time<00:07:50.880> like<00:07:51.360> I 00:07:51.710 --> 00:07:51.720 align:start position:0% spring for a really long time like I 00:07:51.720 --> 00:07:55.550 align:start position:0% spring for a really long time like I guess<00:07:51.840> since<00:07:52.340> 2004<00:07:53.419> and<00:07:54.419> what's<00:07:54.539> remarkable<00:07:55.139> I 00:07:55.550 --> 00:07:55.560 align:start position:0% guess since 2004 and what's remarkable I 00:07:55.560 --> 00:07:57.350 align:start position:0% guess since 2004 and what's remarkable I mean<00:07:55.680> it's<00:07:55.800> kind<00:07:56.039> of<00:07:56.099> weird<00:07:56.280> this<00:07:56.580> is<00:07:56.759> a<00:07:56.940> Scala 00:07:57.350 --> 00:07:57.360 align:start position:0% mean it's kind of weird this is a Scala 00:07:57.360 --> 00:07:59.930 align:start position:0% mean it's kind of weird this is a Scala Meetup<00:07:57.720> where<00:07:57.960> you're<00:07:58.220> obligated<00:07:59.220> to<00:07:59.520> sort<00:07:59.880> of 00:07:59.930 --> 00:07:59.940 align:start position:0% Meetup where you're obligated to sort of 00:07:59.940 --> 00:08:02.870 align:start position:0% Meetup where you're obligated to sort of hate<00:08:00.180> Spring<00:08:00.599> right<00:08:01.080> absolutely<00:08:01.639> yeah<00:08:02.639> you 00:08:02.870 --> 00:08:02.880 align:start position:0% hate Spring right absolutely yeah you 00:08:02.880 --> 00:08:06.170 align:start position:0% hate Spring right absolutely yeah you can<00:08:03.060> really<00:08:03.240> dislike<00:08:03.780> it 00:08:06.170 --> 00:08:06.180 align:start position:0% 00:08:06.180 --> 00:08:08.809 align:start position:0% um<00:08:06.300> but<00:08:06.900> to<00:08:07.199> me<00:08:07.319> spring<00:08:07.620> has<00:08:08.099> just<00:08:08.340> continued 00:08:08.809 --> 00:08:08.819 align:start position:0% um but to me spring has just continued 00:08:08.819 --> 00:08:11.390 align:start position:0% um but to me spring has just continued to<00:08:09.000> remain<00:08:09.360> incredibly<00:08:09.960> relevant<00:08:10.500> and<00:08:10.979> in 00:08:11.390 --> 00:08:11.400 align:start position:0% to remain incredibly relevant and in 00:08:11.400 --> 00:08:13.010 align:start position:0% to remain incredibly relevant and in particular<00:08:11.699> there's<00:08:12.360> this<00:08:12.599> technology 00:08:13.010 --> 00:08:13.020 align:start position:0% particular there's this technology 00:08:13.020 --> 00:08:15.890 align:start position:0% particular there's this technology spring<00:08:13.560> boot<00:08:14.099> that<00:08:14.520> provides<00:08:15.240> sort<00:08:15.539> of<00:08:15.660> a 00:08:15.890 --> 00:08:15.900 align:start position:0% spring boot that provides sort of a 00:08:15.900 --> 00:08:18.529 align:start position:0% spring boot that provides sort of a framework<00:08:16.440> for<00:08:16.860> building<00:08:17.099> or<00:08:17.580> opinionated 00:08:18.529 --> 00:08:18.539 align:start position:0% framework for building or opinionated 00:08:18.539 --> 00:08:21.589 align:start position:0% framework for building or opinionated framework<00:08:19.199> that<00:08:19.680> lets<00:08:19.979> you<00:08:20.039> very<00:08:20.400> quickly<00:08:20.879> get 00:08:21.589 --> 00:08:21.599 align:start position:0% framework that lets you very quickly get 00:08:21.599 --> 00:08:25.029 align:start position:0% framework that lets you very quickly get a<00:08:22.080> spring<00:08:22.259> application<00:08:23.039> off<00:08:23.460> up<00:08:24.240> and<00:08:24.419> running 00:08:25.029 --> 00:08:25.039 align:start position:0% a spring application off up and running 00:08:25.039 --> 00:08:27.290 align:start position:0% a spring application off up and running and<00:08:26.039> it's<00:08:26.160> such<00:08:26.400> a<00:08:26.580> great<00:08:26.699> fit<00:08:27.060> for 00:08:27.290 --> 00:08:27.300 align:start position:0% and it's such a great fit for 00:08:27.300 --> 00:08:29.270 align:start position:0% and it's such a great fit for microservices<00:08:28.080> where<00:08:28.500> because<00:08:28.860> you're 00:08:29.270 --> 00:08:29.280 align:start position:0% microservices where because you're 00:08:29.280 --> 00:08:32.029 align:start position:0% microservices where because you're constantly<00:08:29.879> building<00:08:30.360> new<00:08:30.840> applications<00:08:31.379> and 00:08:32.029 --> 00:08:32.039 align:start position:0% constantly building new applications and 00:08:32.039 --> 00:08:34.730 align:start position:0% constantly building new applications and with<00:08:32.279> spring<00:08:32.640> Boot<00:08:33.539> and<00:08:33.719> its<00:08:34.080> convention<00:08:34.380> over 00:08:34.730 --> 00:08:34.740 align:start position:0% with spring Boot and its convention over 00:08:34.740 --> 00:08:37.969 align:start position:0% with spring Boot and its convention over configuration<00:08:35.839> approach<00:08:36.839> you<00:08:37.560> can<00:08:37.680> very 00:08:37.969 --> 00:08:37.979 align:start position:0% configuration approach you can very 00:08:37.979 --> 00:08:40.430 align:start position:0% configuration approach you can very quickly<00:08:38.339> get<00:08:39.000> a<00:08:39.300> spin<00:08:39.599> up<00:08:39.719> an<00:08:39.959> application 00:08:40.430 --> 00:08:40.440 align:start position:0% quickly get a spin up an application 00:08:40.440 --> 00:08:43.490 align:start position:0% quickly get a spin up an application that's<00:08:40.919> got<00:08:41.159> health<00:08:41.520> checks 00:08:43.490 --> 00:08:43.500 align:start position:0% that's got health checks 00:08:43.500 --> 00:08:44.029 align:start position:0% that's got health checks um 00:08:44.029 --> 00:08:44.039 align:start position:0% um 00:08:44.039 --> 00:08:45.949 align:start position:0% um and<00:08:44.700> you<00:08:44.880> know<00:08:44.940> a<00:08:45.120> whole<00:08:45.240> bunch<00:08:45.420> of<00:08:45.660> sort<00:08:45.839> of 00:08:45.949 --> 00:08:45.959 align:start position:0% and you know a whole bunch of sort of 00:08:45.959 --> 00:08:49.009 align:start position:0% and you know a whole bunch of sort of production-ready<00:08:46.620> features<00:08:47.220> at<00:08:47.459> that<00:08:47.640> point 00:08:49.009 --> 00:08:49.019 align:start position:0% production-ready features at that point 00:08:49.019 --> 00:08:51.230 align:start position:0% production-ready features at that point okay<00:08:49.320> let's<00:08:49.500> go<00:08:49.680> to<00:08:49.740> know<00:08:49.860> and<00:08:50.040> so<00:08:50.160> in<00:08:50.279> both<00:08:50.880> the 00:08:51.230 --> 00:08:51.240 align:start position:0% okay let's go to know and so in both the 00:08:51.240 --> 00:08:53.750 align:start position:0% okay let's go to know and so in both the call<00:08:51.839> Foundry<00:08:52.260> as<00:08:52.500> it<00:08:52.680> exists<00:08:52.980> today<00:08:53.160> what<00:08:53.519> is 00:08:53.750 --> 00:08:53.760 align:start position:0% call Foundry as it exists today what is 00:08:53.760 --> 00:08:56.269 align:start position:0% call Foundry as it exists today what is the<00:08:54.080> uh<00:08:55.080> kind<00:08:55.320> of<00:08:55.440> relation<00:08:55.800> to<00:08:55.980> the<00:08:56.100> original 00:08:56.269 --> 00:08:56.279 align:start position:0% the uh kind of relation to the original 00:08:56.279 --> 00:08:58.730 align:start position:0% the uh kind of relation to the original cloud<00:08:56.700> Foundry<00:08:57.120> you<00:08:57.360> created 00:08:58.730 --> 00:08:58.740 align:start position:0% cloud Foundry you created 00:08:58.740 --> 00:09:00.829 align:start position:0% cloud Foundry you created oh<00:08:59.160> I<00:08:59.339> mean<00:08:59.519> those<00:09:00.000> two<00:09:00.180> things<00:09:00.360> I<00:09:00.660> mean 00:09:00.829 --> 00:09:00.839 align:start position:0% oh I mean those two things I mean 00:09:00.839 --> 00:09:03.230 align:start position:0% oh I mean those two things I mean they're<00:09:01.140> very<00:09:01.500> very<00:09:01.740> different<00:09:02.100> I<00:09:02.880> mean<00:09:03.060> in 00:09:03.230 --> 00:09:03.240 align:start position:0% they're very very different I mean in 00:09:03.240 --> 00:09:05.570 align:start position:0% they're very very different I mean in the<00:09:03.360> past<00:09:03.540> that<00:09:04.019> I<00:09:04.200> built<00:09:04.500> was<00:09:04.800> specifically 00:09:05.570 --> 00:09:05.580 align:start position:0% the past that I built was specifically 00:09:05.580 --> 00:09:08.030 align:start position:0% the past that I built was specifically it<00:09:06.300> was<00:09:06.480> very<00:09:06.779> simple<00:09:07.019> right<00:09:07.440> it<00:09:07.740> was<00:09:07.860> just 00:09:08.030 --> 00:09:08.040 align:start position:0% it was very simple right it was just 00:09:08.040 --> 00:09:12.170 align:start position:0% it was very simple right it was just Java<00:09:08.640> apps<00:09:09.120> on<00:09:09.839> ec2<00:09:10.560> whereas<00:09:11.100> Cloud<00:09:11.519> Foundry 00:09:12.170 --> 00:09:12.180 align:start position:0% Java apps on ec2 whereas Cloud Foundry 00:09:12.180 --> 00:09:14.210 align:start position:0% Java apps on ec2 whereas Cloud Foundry is<00:09:12.480> much<00:09:12.839> more<00:09:13.140> elaborate<00:09:13.620> multiple 00:09:14.210 --> 00:09:14.220 align:start position:0% is much more elaborate multiple 00:09:14.220 --> 00:09:16.570 align:start position:0% is much more elaborate multiple languages<00:09:14.459> many<00:09:15.060> services 00:09:16.570 --> 00:09:16.580 align:start position:0% languages many services 00:09:16.580 --> 00:09:19.670 align:start position:0% languages many services gigantic<00:09:17.580> open<00:09:17.820> source<00:09:18.420> Community 00:09:19.670 --> 00:09:19.680 align:start position:0% gigantic open source Community 00:09:19.680 --> 00:09:22.370 align:start position:0% gigantic open source Community um<00:09:19.740> so<00:09:20.279> the<00:09:20.519> only<00:09:20.640> connection<00:09:21.120> effectively<00:09:22.080> is 00:09:22.370 --> 00:09:22.380 align:start position:0% um so the only connection effectively is 00:09:22.380 --> 00:09:25.250 align:start position:0% um so the only connection effectively is the<00:09:22.680> name<00:09:22.860> at<00:09:23.399> this<00:09:23.580> point<00:09:23.760> okay<00:09:24.360> which<00:09:24.839> which 00:09:25.250 --> 00:09:25.260 align:start position:0% the name at this point okay which which 00:09:25.260 --> 00:09:27.470 align:start position:0% the name at this point okay which which makes<00:09:25.500> my<00:09:25.800> wife<00:09:25.980> very<00:09:26.279> excited<00:09:26.820> because<00:09:27.120> she's 00:09:27.470 --> 00:09:27.480 align:start position:0% makes my wife very excited because she's 00:09:27.480 --> 00:09:29.990 align:start position:0% makes my wife very excited because she's the<00:09:27.660> one<00:09:27.779> who<00:09:28.019> came<00:09:28.260> up<00:09:28.440> with<00:09:28.740> the<00:09:28.920> name<00:09:29.220> no 00:09:29.990 --> 00:09:30.000 align:start position:0% the one who came up with the name no 00:09:30.000 --> 00:09:31.430 align:start position:0% the one who came up with the name no this<00:09:30.180> is<00:09:30.360> a<00:09:30.420> great<00:09:30.540> thing<00:09:30.720> right<00:09:30.959> like<00:09:31.140> name 00:09:31.430 --> 00:09:31.440 align:start position:0% this is a great thing right like name 00:09:31.440 --> 00:09:33.110 align:start position:0% this is a great thing right like name you<00:09:31.740> know<00:09:31.860> as<00:09:31.920> Pro<00:09:32.220> commercial<00:09:32.339> all<00:09:32.760> names<00:09:32.940> are 00:09:33.110 --> 00:09:33.120 align:start position:0% you know as Pro commercial all names are 00:09:33.120 --> 00:09:35.990 align:start position:0% you know as Pro commercial all names are important<00:09:33.420> yeah<00:09:33.720> so<00:09:34.320> that's<00:09:34.500> absolutely<00:09:35.040> so 00:09:35.990 --> 00:09:36.000 align:start position:0% important yeah so that's absolutely so 00:09:36.000 --> 00:09:39.110 align:start position:0% important yeah so that's absolutely so she<00:09:36.240> constantly<00:09:36.779> reminds<00:09:37.380> me<00:09:37.500> that<00:09:37.980> it<00:09:38.580> hadn't 00:09:39.110 --> 00:09:39.120 align:start position:0% she constantly reminds me that it hadn't 00:09:39.120 --> 00:09:43.550 align:start position:0% she constantly reminds me that it hadn't you<00:09:39.240> know<00:09:39.360> her<00:09:39.779> her<00:09:40.500> naming<00:09:41.100> lives<00:09:42.060> on<00:09:42.240> yes<00:09:42.779> but 00:09:43.550 --> 00:09:43.560 align:start position:0% you know her her naming lives on yes but 00:09:43.560 --> 00:09:45.710 align:start position:0% you know her her naming lives on yes but also<00:09:43.800> I<00:09:43.860> think<00:09:43.980> the<00:09:44.100> open<00:09:44.220> source<00:09:44.700> approach<00:09:45.240> is 00:09:45.710 --> 00:09:45.720 align:start position:0% also I think the open source approach is 00:09:45.720 --> 00:09:48.290 align:start position:0% also I think the open source approach is similar<00:09:46.140> right<00:09:46.380> the<00:09:46.740> the<00:09:47.060> focus<00:09:48.060> on<00:09:48.180> open 00:09:48.290 --> 00:09:48.300 align:start position:0% similar right the the focus on open 00:09:48.300 --> 00:09:50.050 align:start position:0% similar right the the focus on open source<00:09:48.779> well 00:09:50.050 --> 00:09:50.060 align:start position:0% source well 00:09:50.060 --> 00:09:52.790 align:start position:0% source well my<00:09:51.060> part<00:09:51.420> of<00:09:51.600> what<00:09:51.959> I<00:09:52.140> did<00:09:52.320> with<00:09:52.500> the<00:09:52.680> original 00:09:52.790 --> 00:09:52.800 align:start position:0% my part of what I did with the original 00:09:52.800 --> 00:09:54.769 align:start position:0% my part of what I did with the original cloud<00:09:53.160> Foundry<00:09:53.760> the<00:09:53.940> cloud<00:09:54.180> tools 00:09:54.769 --> 00:09:54.779 align:start position:0% cloud Foundry the cloud tools 00:09:54.779 --> 00:09:57.470 align:start position:0% cloud Foundry the cloud tools provisioning<00:09:55.580> layer<00:09:56.580> which<00:09:56.820> was<00:09:57.000> sort<00:09:57.180> of<00:09:57.300> a 00:09:57.470 --> 00:09:57.480 align:start position:0% provisioning layer which was sort of a 00:09:57.480 --> 00:09:59.329 align:start position:0% provisioning layer which was sort of a CLI<00:09:58.080> based<00:09:58.500> approach<00:09:58.680> approach<00:09:59.100> the 00:09:59.329 --> 00:09:59.339 align:start position:0% CLI based approach approach the 00:09:59.339 --> 00:10:01.730 align:start position:0% CLI based approach approach the deployment<00:09:59.760> was<00:10:00.120> open<00:10:00.360> source<00:10:00.899> but<00:10:01.200> all<00:10:01.560> of 00:10:01.730 --> 00:10:01.740 align:start position:0% deployment was open source but all of 00:10:01.740 --> 00:10:05.030 align:start position:0% deployment was open source but all of the<00:10:02.100> higher<00:10:02.580> level<00:10:02.700> stuff<00:10:03.380> was<00:10:04.380> not<00:10:04.620> actually 00:10:05.030 --> 00:10:05.040 align:start position:0% the higher level stuff was not actually 00:10:05.040 --> 00:10:07.190 align:start position:0% the higher level stuff was not actually open<00:10:05.940> source 00:10:07.190 --> 00:10:07.200 align:start position:0% open source 00:10:07.200 --> 00:10:11.210 align:start position:0% open source okay<00:10:08.160> so<00:10:09.120> but<00:10:09.300> I<00:10:09.480> mean<00:10:09.660> definitely<00:10:10.500> we<00:10:10.860> you 00:10:11.210 --> 00:10:11.220 align:start position:0% okay so but I mean definitely we you 00:10:11.220 --> 00:10:12.829 align:start position:0% okay so but I mean definitely we you know<00:10:11.399> now<00:10:11.640> with<00:10:11.820> the<00:10:12.000> open<00:10:12.300> source<00:10:12.600> approach 00:10:12.829 --> 00:10:12.839 align:start position:0% know now with the open source approach 00:10:12.839 --> 00:10:14.990 align:start position:0% know now with the open source approach pivotal<00:10:13.440> just<00:10:13.680> announced 00:10:14.990 --> 00:10:15.000 align:start position:0% pivotal just announced 00:10:15.000 --> 00:10:17.810 align:start position:0% pivotal just announced a<00:10:15.899> strata<00:10:16.560> I<00:10:16.680> think<00:10:16.800> you<00:10:17.040> know<00:10:17.160> it's<00:10:17.339> great<00:10:17.580> to 00:10:17.810 --> 00:10:17.820 align:start position:0% a strata I think you know it's great to 00:10:17.820 --> 00:10:20.090 align:start position:0% a strata I think you know it's great to see<00:10:17.940> this<00:10:18.180> open<00:10:18.779> source<00:10:19.260> platform<00:10:19.620> right<00:10:19.860> yeah 00:10:20.090 --> 00:10:20.100 align:start position:0% see this open source platform right yeah 00:10:20.100 --> 00:10:22.030 align:start position:0% see this open source platform right yeah for<00:10:20.339> applications<00:10:20.760> yeah 00:10:22.030 --> 00:10:22.040 align:start position:0% for applications yeah 00:10:22.040 --> 00:10:24.290 align:start position:0% for applications yeah interesting<00:10:23.040> so<00:10:23.160> and<00:10:23.399> I<00:10:23.820> know<00:10:23.940> that<00:10:24.120> you 00:10:24.290 --> 00:10:24.300 align:start position:0% interesting so and I know that you 00:10:24.300 --> 00:10:26.329 align:start position:0% interesting so and I know that you recently<00:10:24.660> got<00:10:25.320> interested<00:10:25.740> in<00:10:26.160> event 00:10:26.329 --> 00:10:26.339 align:start position:0% recently got interested in event 00:10:26.339 --> 00:10:29.269 align:start position:0% recently got interested in event sourcing<00:10:26.880> architectures<00:10:27.560> and<00:10:28.560> I'm<00:10:29.100> really 00:10:29.269 --> 00:10:29.279 align:start position:0% sourcing architectures and I'm really 00:10:29.279 --> 00:10:30.650 align:start position:0% sourcing architectures and I'm really curious<00:10:29.519> about<00:10:29.640> the<00:10:29.880> connection<00:10:30.060> you<00:10:30.540> see 00:10:30.650 --> 00:10:30.660 align:start position:0% curious about the connection you see 00:10:30.660 --> 00:10:33.050 align:start position:0% curious about the connection you see between<00:10:30.899> event<00:10:31.200> sourcing<00:10:31.800> and<00:10:32.339> microservices 00:10:33.050 --> 00:10:33.060 align:start position:0% between event sourcing and microservices 00:10:33.060 --> 00:10:36.410 align:start position:0% between event sourcing and microservices oh<00:10:34.019> yeah<00:10:34.440> so<00:10:35.220> I<00:10:35.279> think 00:10:36.410 --> 00:10:36.420 align:start position:0% oh yeah so I think 00:10:36.420 --> 00:10:38.990 align:start position:0% oh yeah so I think so<00:10:36.899> if<00:10:37.019> you<00:10:37.140> look<00:10:37.320> at<00:10:37.500> modern<00:10:37.860> Trends<00:10:38.820> in 00:10:38.990 --> 00:10:39.000 align:start position:0% so if you look at modern Trends in 00:10:39.000 --> 00:10:40.970 align:start position:0% so if you look at modern Trends in application<00:10:39.540> development<00:10:40.200> so<00:10:40.620> obviously 00:10:40.970 --> 00:10:40.980 align:start position:0% application development so obviously 00:10:40.980 --> 00:10:44.810 align:start position:0% application development so obviously microservices<00:10:41.940> is<00:10:42.300> one<00:10:42.600> part<00:10:42.839> of<00:10:43.019> it<00:10:43.399> and<00:10:44.399> so 00:10:44.810 --> 00:10:44.820 align:start position:0% microservices is one part of it and so 00:10:44.820 --> 00:10:46.490 align:start position:0% microservices is one part of it and so what<00:10:45.000> you<00:10:45.120> end<00:10:45.300> up<00:10:45.480> with<00:10:45.660> when<00:10:45.959> you<00:10:46.200> use 00:10:46.490 --> 00:10:46.500 align:start position:0% what you end up with when you use 00:10:46.500 --> 00:10:48.470 align:start position:0% what you end up with when you use microservices<00:10:47.339> is<00:10:47.640> a<00:10:47.880> bunch<00:10:48.000> of<00:10:48.180> services 00:10:48.470 --> 00:10:48.480 align:start position:0% microservices is a bunch of services 00:10:48.480 --> 00:10:50.630 align:start position:0% microservices is a bunch of services each<00:10:49.200> one<00:10:49.380> with<00:10:49.620> their<00:10:49.800> own<00:10:49.980> independent 00:10:50.630 --> 00:10:50.640 align:start position:0% each one with their own independent 00:10:50.640 --> 00:10:52.190 align:start position:0% each one with their own independent database 00:10:52.190 --> 00:10:52.200 align:start position:0% database 00:10:52.200 --> 00:10:54.350 align:start position:0% database and<00:10:52.620> then<00:10:52.680> also<00:10:52.980> if<00:10:53.220> you<00:10:53.339> look<00:10:53.579> at<00:10:53.820> the<00:10:54.060> I<00:10:54.180> mean 00:10:54.350 --> 00:10:54.360 align:start position:0% and then also if you look at the I mean 00:10:54.360 --> 00:10:55.850 align:start position:0% and then also if you look at the I mean another<00:10:54.480> big<00:10:54.839> Trend<00:10:55.200> in<00:10:55.500> that<00:10:55.740> app 00:10:55.850 --> 00:10:55.860 align:start position:0% another big Trend in that app 00:10:55.860 --> 00:10:59.090 align:start position:0% another big Trend in that app development<00:10:56.579> is<00:10:56.820> no<00:10:57.120> SQL<00:10:57.600> right<00:10:57.959> and<00:10:58.740> once 00:10:59.090 --> 00:10:59.100 align:start position:0% development is no SQL right and once 00:10:59.100 --> 00:11:02.569 align:start position:0% development is no SQL right and once again<00:10:59.660> you<00:11:00.660> end<00:11:00.899> up<00:11:01.160> where<00:11:02.160> you<00:11:02.279> sort<00:11:02.399> of<00:11:02.459> at 00:11:02.569 --> 00:11:02.579 align:start position:0% again you end up where you sort of at 00:11:02.579 --> 00:11:04.550 align:start position:0% again you end up where you sort of at your<00:11:02.820> polyglot<00:11:03.600> persistence<00:11:04.140> in<00:11:04.380> general 00:11:04.550 --> 00:11:04.560 align:start position:0% your polyglot persistence in general 00:11:04.560 --> 00:11:06.710 align:start position:0% your polyglot persistence in general where<00:11:04.860> you<00:11:05.040> end<00:11:05.220> up<00:11:05.339> with<00:11:05.519> multiple<00:11:05.940> databases 00:11:06.710 --> 00:11:06.720 align:start position:0% where you end up with multiple databases 00:11:06.720 --> 00:11:10.190 align:start position:0% where you end up with multiple databases most<00:11:07.440> of<00:11:07.620> which<00:11:07.880> have<00:11:08.880> very<00:11:09.180> sort<00:11:09.540> of<00:11:09.660> limited 00:11:10.190 --> 00:11:10.200 align:start position:0% most of which have very sort of limited 00:11:10.200 --> 00:11:13.670 align:start position:0% most of which have very sort of limited transactional<00:11:11.160> capabilities 00:11:13.670 --> 00:11:13.680 align:start position:0% transactional capabilities 00:11:13.680 --> 00:11:15.110 align:start position:0% transactional capabilities um<00:11:13.740> so<00:11:13.920> that<00:11:14.100> you<00:11:14.220> end<00:11:14.459> up<00:11:14.579> in<00:11:14.940> both 00:11:15.110 --> 00:11:15.120 align:start position:0% um so that you end up in both 00:11:15.120 --> 00:11:17.449 align:start position:0% um so that you end up in both microservices<00:11:16.019> and<00:11:16.320> those<00:11:16.500> SQL<00:11:16.860> with<00:11:17.100> these 00:11:17.449 --> 00:11:17.459 align:start position:0% microservices and those SQL with these 00:11:17.459 --> 00:11:19.610 align:start position:0% microservices and those SQL with these distributed<00:11:18.000> data<00:11:18.540> management<00:11:18.720> challenges 00:11:19.610 --> 00:11:19.620 align:start position:0% distributed data management challenges 00:11:19.620 --> 00:11:23.630 align:start position:0% distributed data management challenges of<00:11:20.339> needing<00:11:21.240> to<00:11:21.540> have<00:11:21.920> transactions<00:11:22.920> that 00:11:23.630 --> 00:11:23.640 align:start position:0% of needing to have transactions that 00:11:23.640 --> 00:11:26.750 align:start position:0% of needing to have transactions that span<00:11:24.120> multiple<00:11:24.600> databases<00:11:25.380> yet<00:11:25.980> you<00:11:26.399> do<00:11:26.579> not 00:11:26.750 --> 00:11:26.760 align:start position:0% span multiple databases yet you do not 00:11:26.760 --> 00:11:30.530 align:start position:0% span multiple databases yet you do not have<00:11:27.240> two-phase<00:11:28.079> Commit<00:11:28.579> right<00:11:29.579> cap<00:11:30.000> theorem 00:11:30.530 --> 00:11:30.540 align:start position:0% have two-phase Commit right cap theorem 00:11:30.540 --> 00:11:33.050 align:start position:0% have two-phase Commit right cap theorem and<00:11:30.839> and<00:11:31.079> just<00:11:31.440> it's<00:11:32.040> complete<00:11:32.700> you<00:11:32.880> know<00:11:33.000> it's 00:11:33.050 --> 00:11:33.060 align:start position:0% and and just it's complete you know it's 00:11:33.060 --> 00:11:35.630 align:start position:0% and and just it's complete you know it's out<00:11:33.300> of<00:11:33.480> fashion<00:11:33.839> and<00:11:34.680> so<00:11:34.800> the<00:11:35.040> solution<00:11:35.339> to 00:11:35.630 --> 00:11:35.640 align:start position:0% out of fashion and so the solution to 00:11:35.640 --> 00:11:37.550 align:start position:0% out of fashion and so the solution to that<00:11:35.760> is<00:11:36.060> an<00:11:36.240> event-driven<00:11:36.959> architecture 00:11:37.550 --> 00:11:37.560 align:start position:0% that is an event-driven architecture 00:11:37.560 --> 00:11:40.670 align:start position:0% that is an event-driven architecture where<00:11:37.980> things<00:11:38.279> publish<00:11:38.820> events<00:11:39.480> well<00:11:40.140> when 00:11:40.670 --> 00:11:40.680 align:start position:0% where things publish events well when 00:11:40.680 --> 00:11:42.650 align:start position:0% where things publish events well when State<00:11:40.980> changes<00:11:41.459> in<00:11:41.700> one<00:11:41.940> service<00:11:42.240> it 00:11:42.650 --> 00:11:42.660 align:start position:0% State changes in one service it 00:11:42.660 --> 00:11:44.990 align:start position:0% State changes in one service it publishes<00:11:43.079> events<00:11:43.620> and<00:11:43.860> subscribers<00:11:44.519> can 00:11:44.990 --> 00:11:45.000 align:start position:0% publishes events and subscribers can 00:11:45.000 --> 00:11:47.329 align:start position:0% publishes events and subscribers can consume<00:11:45.660> those<00:11:45.899> events<00:11:46.380> and<00:11:46.680> update<00:11:47.100> their 00:11:47.329 --> 00:11:47.339 align:start position:0% consume those events and update their 00:11:47.339 --> 00:11:49.850 align:start position:0% consume those events and update their own<00:11:47.519> State<00:11:47.820> and<00:11:48.060> Implement<00:11:48.480> consistency<00:11:49.079> and 00:11:49.850 --> 00:11:49.860 align:start position:0% own State and Implement consistency and 00:11:49.860 --> 00:11:52.130 align:start position:0% own State and Implement consistency and it<00:11:49.980> turns<00:11:50.279> out<00:11:50.339> that<00:11:50.700> event<00:11:50.880> sourcing<00:11:51.600> is<00:11:51.959> a 00:11:52.130 --> 00:11:52.140 align:start position:0% it turns out that event sourcing is a 00:11:52.140 --> 00:11:55.130 align:start position:0% it turns out that event sourcing is a very<00:11:52.320> good<00:11:52.560> way<00:11:52.980> of<00:11:53.760> implementing<00:11:54.660> an 00:11:55.130 --> 00:11:55.140 align:start position:0% very good way of implementing an 00:11:55.140 --> 00:11:57.470 align:start position:0% very good way of implementing an event-driven<00:11:55.860> architecture<00:11:56.459> yes 00:11:57.470 --> 00:11:57.480 align:start position:0% event-driven architecture yes 00:11:57.480 --> 00:11:59.509 align:start position:0% event-driven architecture yes but<00:11:58.019> you<00:11:58.200> know<00:11:58.380> we<00:11:58.560> actually<00:11:58.680> implemented<00:11:59.279> an 00:11:59.509 --> 00:11:59.519 align:start position:0% but you know we actually implemented an 00:11:59.519 --> 00:12:02.269 align:start position:0% but you know we actually implemented an event<00:11:59.700> sourcing<00:12:00.180> architecture<00:12:00.779> adversal<00:12:01.320> uh 00:12:02.269 --> 00:12:02.279 align:start position:0% event sourcing architecture adversal uh 00:12:02.279 --> 00:12:04.430 align:start position:0% event sourcing architecture adversal uh a<00:12:02.700> couple<00:12:02.880> years<00:12:03.060> ago<00:12:03.420> and<00:12:03.720> we<00:12:03.959> actually<00:12:04.140> ran 00:12:04.430 --> 00:12:04.440 align:start position:0% a couple years ago and we actually ran 00:12:04.440 --> 00:12:05.810 align:start position:0% a couple years ago and we actually ran into<00:12:04.560> this<00:12:04.800> problem<00:12:04.920> that<00:12:05.279> for<00:12:05.640> event 00:12:05.810 --> 00:12:05.820 align:start position:0% into this problem that for event 00:12:05.820 --> 00:12:07.069 align:start position:0% into this problem that for event sourcing<00:12:06.240> you<00:12:06.360> do<00:12:06.480> need<00:12:06.600> transactions 00:12:07.069 --> 00:12:07.079 align:start position:0% sourcing you do need transactions 00:12:07.079 --> 00:12:08.769 align:start position:0% sourcing you do need transactions because<00:12:07.260> you<00:12:07.440> need<00:12:07.620> serialization<00:12:08.160> of<00:12:08.339> events 00:12:08.769 --> 00:12:08.779 align:start position:0% because you need serialization of events 00:12:08.779 --> 00:12:11.990 align:start position:0% because you need serialization of events if<00:12:09.779> that<00:12:10.440> or<00:12:11.040> at<00:12:11.160> least<00:12:11.279> within<00:12:11.579> some<00:12:11.700> context 00:12:11.990 --> 00:12:12.000 align:start position:0% if that or at least within some context 00:12:12.000 --> 00:12:14.030 align:start position:0% if that or at least within some context right<00:12:12.240> because<00:12:12.480> if<00:12:13.019> you're<00:12:13.079> updating<00:12:13.500> a<00:12:13.680> data 00:12:14.030 --> 00:12:14.040 align:start position:0% right because if you're updating a data 00:12:14.040 --> 00:12:15.769 align:start position:0% right because if you're updating a data structure<00:12:14.399> you<00:12:14.940> know<00:12:15.060> you<00:12:15.300> basically<00:12:15.600> read 00:12:15.769 --> 00:12:15.779 align:start position:0% structure you know you basically read 00:12:15.779 --> 00:12:17.389 align:start position:0% structure you know you basically read and<00:12:16.019> write<00:12:16.140> to<00:12:16.320> it<00:12:16.500> you<00:12:16.680> need<00:12:16.800> to<00:12:16.860> know<00:12:17.040> what<00:12:17.220> is 00:12:17.389 --> 00:12:17.399 align:start position:0% and write to it you need to know what is 00:12:17.399 --> 00:12:19.009 align:start position:0% and write to it you need to know what is the<00:12:17.519> order<00:12:17.640> of<00:12:17.880> reason<00:12:18.000> right<00:12:18.300> so<00:12:18.540> we<00:12:18.899> actually 00:12:19.009 --> 00:12:19.019 align:start position:0% the order of reason right so we actually 00:12:19.019 --> 00:12:21.530 align:start position:0% the order of reason right so we actually end<00:12:19.260> up<00:12:19.380> using<00:12:19.800> an<00:12:20.279> abstraction<00:12:20.700> of<00:12:20.940> of<00:12:21.180> an 00:12:21.530 --> 00:12:21.540 align:start position:0% end up using an abstraction of of an 00:12:21.540 --> 00:12:24.350 align:start position:0% end up using an abstraction of of an event<00:12:21.720> log<00:12:22.160> which<00:12:23.160> then<00:12:23.519> we<00:12:23.760> Implement<00:12:24.000> using 00:12:24.350 --> 00:12:24.360 align:start position:0% event log which then we Implement using 00:12:24.360 --> 00:12:26.750 align:start position:0% event log which then we Implement using MySQL<00:12:24.779> because<00:12:24.959> we<00:12:25.260> needed<00:12:25.760> transactional 00:12:26.750 --> 00:12:26.760 align:start position:0% MySQL because we needed transactional 00:12:26.760 --> 00:12:28.670 align:start position:0% MySQL because we needed transactional capabilities<00:12:27.180> so<00:12:27.540> we<00:12:27.779> we<00:12:28.260> found<00:12:28.500> that 00:12:28.670 --> 00:12:28.680 align:start position:0% capabilities so we we found that 00:12:28.680 --> 00:12:31.069 align:start position:0% capabilities so we we found that basically<00:12:28.980> if<00:12:29.339> you<00:12:29.399> if<00:12:29.640> you<00:12:29.820> have<00:12:30.000> this<00:12:30.660> notion 00:12:31.069 --> 00:12:31.079 align:start position:0% basically if you if you have this notion 00:12:31.079 --> 00:12:33.590 align:start position:0% basically if you if you have this notion of<00:12:31.260> a<00:12:31.620> login<00:12:31.860> sequence<00:12:32.579> and<00:12:32.820> you<00:12:32.940> need<00:12:33.120> in<00:12:33.540> this 00:12:33.590 --> 00:12:33.600 align:start position:0% of a login sequence and you need in this 00:12:33.600 --> 00:12:36.050 align:start position:0% of a login sequence and you need in this case<00:12:33.720> we<00:12:33.959> need<00:12:34.079> transactional<00:12:34.880> database<00:12:35.880> to 00:12:36.050 --> 00:12:36.060 align:start position:0% case we need transactional database to 00:12:36.060 --> 00:12:37.850 align:start position:0% case we need transactional database to implement<00:12:36.300> to<00:12:36.540> actually<00:12:36.720> ensure<00:12:37.140> that<00:12:37.680> we'll 00:12:37.850 --> 00:12:37.860 align:start position:0% implement to actually ensure that we'll 00:12:37.860 --> 00:12:39.290 align:start position:0% implement to actually ensure that we'll have<00:12:38.040> the<00:12:38.100> thing<00:12:38.220> so<00:12:38.459> you<00:12:38.579> so<00:12:38.940> you<00:12:39.180> might 00:12:39.290 --> 00:12:39.300 align:start position:0% have the thing so you so you might 00:12:39.300 --> 00:12:40.850 align:start position:0% have the thing so you so you might publish<00:12:39.720> this<00:12:39.899> event<00:12:40.140> but<00:12:40.440> the<00:12:40.560> question<00:12:40.680> is 00:12:40.850 --> 00:12:40.860 align:start position:0% publish this event but the question is 00:12:40.860 --> 00:12:42.829 align:start position:0% publish this event but the question is how<00:12:41.040> you're<00:12:41.220> gonna<00:12:41.399> at<00:12:42.060> some<00:12:42.300> point<00:12:42.420> you<00:12:42.660> you 00:12:42.829 --> 00:12:42.839 align:start position:0% how you're gonna at some point you you 00:12:42.839 --> 00:12:44.509 align:start position:0% how you're gonna at some point you you will<00:12:43.019> need<00:12:43.260> some<00:12:43.620> transactional<00:12:44.160> capability 00:12:44.509 --> 00:12:44.519 align:start position:0% will need some transactional capability 00:12:44.519 --> 00:12:47.150 align:start position:0% will need some transactional capability to<00:12:44.940> to<00:12:45.180> establish<00:12:45.600> the<00:12:45.839> order 00:12:47.150 --> 00:12:47.160 align:start position:0% to to establish the order 00:12:47.160 --> 00:12:50.210 align:start position:0% to to establish the order yes<00:12:48.000> but<00:12:48.899> I<00:12:49.380> mean<00:12:49.440> one<00:12:49.620> of<00:12:49.740> the<00:12:49.800> things<00:12:49.980> I've 00:12:50.210 --> 00:12:50.220 align:start position:0% yes but I mean one of the things I've 00:12:50.220 --> 00:12:53.150 align:start position:0% yes but I mean one of the things I've been<00:12:50.399> working<00:12:50.639> on<00:12:51.000> is<00:12:51.480> an<00:12:51.720> event<00:12:51.839> store<00:12:52.380> that 00:12:53.150 --> 00:12:53.160 align:start position:0% been working on is an event store that 00:12:53.160 --> 00:12:55.790 align:start position:0% been working on is an event store that actually<00:12:53.399> takes<00:12:54.060> care<00:12:54.480> of<00:12:54.660> some<00:12:55.019> of<00:12:55.139> that<00:12:55.440> hard 00:12:55.790 --> 00:12:55.800 align:start position:0% actually takes care of some of that hard 00:12:55.800 --> 00:12:57.829 align:start position:0% actually takes care of some of that hard stuff<00:12:56.160> ah<00:12:56.760> okay 00:12:57.829 --> 00:12:57.839 align:start position:0% stuff ah okay 00:12:57.839 --> 00:12:58.670 align:start position:0% stuff ah okay um 00:12:58.670 --> 00:12:58.680 align:start position:0% um 00:12:58.680 --> 00:13:01.190 align:start position:0% um and<00:12:59.220> so<00:12:59.399> they're<00:12:59.700> sort<00:12:59.940> of<00:13:00.060> inside<00:13:00.660> it<00:13:01.019> there's 00:13:01.190 --> 00:13:01.200 align:start position:0% and so they're sort of inside it there's 00:13:01.200 --> 00:13:03.530 align:start position:0% and so they're sort of inside it there's sort<00:13:01.380> of<00:13:01.500> a<00:13:01.620> transaction<00:13:02.040> Manager<00:13:02.820> Management 00:13:03.530 --> 00:13:03.540 align:start position:0% sort of a transaction Manager Management 00:13:03.540 --> 00:13:05.750 align:start position:0% sort of a transaction Manager Management kind<00:13:04.200> of<00:13:04.440> capability 00:13:05.750 --> 00:13:05.760 align:start position:0% kind of capability 00:13:05.760 --> 00:13:07.550 align:start position:0% kind of capability that<00:13:06.480> that 00:13:07.550 --> 00:13:07.560 align:start position:0% that that 00:13:07.560 --> 00:13:10.310 align:start position:0% that that um<00:13:07.639> enables<00:13:08.639> you<00:13:08.760> to<00:13:09.060> atomically<00:13:09.720> persist 00:13:10.310 --> 00:13:10.320 align:start position:0% um enables you to atomically persist 00:13:10.320 --> 00:13:12.769 align:start position:0% um enables you to atomically persist events<00:13:10.860> and<00:13:11.279> publish<00:13:11.639> them<00:13:11.880> at<00:13:12.240> the<00:13:12.360> same<00:13:12.540> time 00:13:12.769 --> 00:13:12.779 align:start position:0% events and publish them at the same time 00:13:12.779 --> 00:13:15.350 align:start position:0% events and publish them at the same time okay<00:13:13.200> okay<00:13:13.740> now<00:13:14.399> this<00:13:14.579> is<00:13:14.700> great<00:13:14.820> so<00:13:15.120> basically 00:13:15.350 --> 00:13:15.360 align:start position:0% okay okay now this is great so basically 00:13:15.360 --> 00:13:17.150 align:start position:0% okay okay now this is great so basically we<00:13:15.720> are<00:13:15.959> actually<00:13:16.079> working<00:13:16.560> on<00:13:16.740> a<00:13:16.920> very 00:13:17.150 --> 00:13:17.160 align:start position:0% we are actually working on a very 00:13:17.160 --> 00:13:18.949 align:start position:0% we are actually working on a very similar<00:13:17.459> problems<00:13:17.700> yeah<00:13:18.240> I'm<00:13:18.540> very<00:13:18.779> very 00:13:18.949 --> 00:13:18.959 align:start position:0% similar problems yeah I'm very very 00:13:18.959 --> 00:13:21.949 align:start position:0% similar problems yeah I'm very very excited<00:13:19.560> to<00:13:19.740> see<00:13:20.040> you<00:13:20.100> work<00:13:20.399> on<00:13:20.579> this<00:13:20.700> cool 00:13:21.949 --> 00:13:21.959 align:start position:0% excited to see you work on this cool 00:13:21.959 --> 00:13:24.050 align:start position:0% excited to see you work on this cool um<00:13:22.079> so<00:13:22.560> and<00:13:22.680> another<00:13:22.980> thing<00:13:23.279> you<00:13:23.639> are<00:13:23.820> the 00:13:24.050 --> 00:13:24.060 align:start position:0% um so and another thing you are the 00:13:24.060 --> 00:13:26.090 align:start position:0% um so and another thing you are the organizer<00:13:24.600> for<00:13:24.839> the<00:13:25.019> East<00:13:25.260> Bay<00:13:25.440> Java<00:13:25.860> user 00:13:26.090 --> 00:13:26.100 align:start position:0% organizer for the East Bay Java user 00:13:26.100 --> 00:13:27.889 align:start position:0% organizer for the East Bay Java user group<00:13:26.279> and<00:13:26.880> I<00:13:27.000> was<00:13:27.180> you<00:13:27.300> know<00:13:27.420> very<00:13:27.540> happy<00:13:27.720> to 00:13:27.889 --> 00:13:27.899 align:start position:0% group and I was you know very happy to 00:13:27.899 --> 00:13:30.170 align:start position:0% group and I was you know very happy to find<00:13:28.079> that<00:13:28.260> you<00:13:28.380> guys<00:13:28.560> run<00:13:28.800> uh<00:13:29.519> events<00:13:29.880> not<00:13:30.000> far 00:13:30.170 --> 00:13:30.180 align:start position:0% find that you guys run uh events not far 00:13:30.180 --> 00:13:34.009 align:start position:0% find that you guys run uh events not far from<00:13:30.420> from<00:13:30.720> where<00:13:31.079> I<00:13:31.260> live<00:13:31.380> as<00:13:32.360> longevity<00:13:33.360> so 00:13:34.009 --> 00:13:34.019 align:start position:0% from from where I live as longevity so 00:13:34.019 --> 00:13:35.930 align:start position:0% from from where I live as longevity so this<00:13:34.139> is<00:13:34.260> you<00:13:34.440> know<00:13:34.560> and<00:13:35.040> obviously<00:13:35.459> so<00:13:35.700> this 00:13:35.930 --> 00:13:35.940 align:start position:0% this is you know and obviously so this 00:13:35.940 --> 00:13:38.690 align:start position:0% this is you know and obviously so this is<00:13:36.000> a<00:13:36.180> joint<00:13:36.480> event<00:13:36.600> with<00:13:36.959> uh<00:13:37.800> is<00:13:37.980> by<00:13:38.160> jargon 00:13:38.690 --> 00:13:38.700 align:start position:0% is a joint event with uh is by jargon 00:13:38.700 --> 00:13:41.389 align:start position:0% is a joint event with uh is by jargon and<00:13:38.940> as<00:13:39.060> a<00:13:39.300> scholar<00:13:39.660> and<00:13:40.260> you're<00:13:40.680> a<00:13:40.920> long<00:13:41.100> time 00:13:41.389 --> 00:13:41.399 align:start position:0% and as a scholar and you're a long time 00:13:41.399 --> 00:13:44.810 align:start position:0% and as a scholar and you're a long time Jama<00:13:42.060> user<00:13:42.600> so<00:13:42.720> I<00:13:42.899> wonder<00:13:43.079> you<00:13:43.860> know<00:13:43.980> what 00:13:44.810 --> 00:13:44.820 align:start position:0% Jama user so I wonder you know what 00:13:44.820 --> 00:13:47.509 align:start position:0% Jama user so I wonder you know what aspects<00:13:45.300> of<00:13:45.540> Scala<00:13:46.079> uh<00:13:46.860> interest<00:13:47.040> you<00:13:47.339> the 00:13:47.509 --> 00:13:47.519 align:start position:0% aspects of Scala uh interest you the 00:13:47.519 --> 00:13:49.129 align:start position:0% aspects of Scala uh interest you the most<00:13:47.639> how<00:13:47.940> do<00:13:48.120> you<00:13:48.300> see<00:13:48.420> you<00:13:48.660> know<00:13:48.720> scholar 00:13:49.129 --> 00:13:49.139 align:start position:0% most how do you see you know scholar 00:13:49.139 --> 00:13:50.750 align:start position:0% most how do you see you know scholar Community<00:13:49.320> evolve<00:13:49.920> and<00:13:49.980> basically<00:13:50.279> where<00:13:50.579> do 00:13:50.750 --> 00:13:50.760 align:start position:0% Community evolve and basically where do 00:13:50.760 --> 00:13:53.389 align:start position:0% Community evolve and basically where do you<00:13:50.880> see<00:13:51.060> skull<00:13:51.899> Community<00:13:52.139> going<00:13:52.620> in<00:13:53.100> the 00:13:53.389 --> 00:13:53.399 align:start position:0% you see skull Community going in the 00:13:53.399 --> 00:13:55.850 align:start position:0% you see skull Community going in the future<00:13:53.519> yeah<00:13:54.360> so<00:13:54.839> it's<00:13:54.959> interesting<00:13:55.380> so<00:13:55.680> the 00:13:55.850 --> 00:13:55.860 align:start position:0% future yeah so it's interesting so the 00:13:55.860 --> 00:13:57.650 align:start position:0% future yeah so it's interesting so the Oakland<00:13:56.040> Java<00:13:56.700> users<00:13:57.000> group<00:13:57.240> has<00:13:57.480> been 00:13:57.650 --> 00:13:57.660 align:start position:0% Oakland Java users group has been 00:13:57.660 --> 00:14:01.610 align:start position:0% Oakland Java users group has been meeting<00:13:57.899> since<00:13:58.880> 2003.<00:13:59.880> wow<00:14:00.540> so<00:14:00.779> kind<00:14:01.260> of<00:14:01.380> kind 00:14:01.610 --> 00:14:01.620 align:start position:0% meeting since 2003. wow so kind of kind 00:14:01.620 --> 00:14:03.710 align:start position:0% meeting since 2003. wow so kind of kind of<00:14:01.740> a<00:14:01.920> while<00:14:02.040> yeah 00:14:03.710 --> 00:14:03.720 align:start position:0% of a while yeah 00:14:03.720 --> 00:14:07.670 align:start position:0% of a while yeah um<00:14:03.779> and<00:14:04.079> we're<00:14:04.200> still<00:14:04.620> going<00:14:04.800> strong<00:14:05.160> so<00:14:05.760> so 00:14:07.670 --> 00:14:07.680 align:start position:0% um and we're still going strong so so 00:14:07.680 --> 00:14:08.930 align:start position:0% um and we're still going strong so so um 00:14:08.930 --> 00:14:08.940 align:start position:0% um 00:14:08.940 --> 00:14:10.910 align:start position:0% um so<00:14:09.480> if<00:14:09.600> I<00:14:09.779> you<00:14:09.899> know<00:14:10.079> I<00:14:10.139> look<00:14:10.380> back<00:14:10.560> and 00:14:10.910 --> 00:14:10.920 align:start position:0% so if I you know I look back and 00:14:10.920 --> 00:14:14.329 align:start position:0% so if I you know I look back and interestingly<00:14:11.579> the<00:14:12.360> the<00:14:12.480> the<00:14:12.720> the<00:14:12.980> core<00:14:13.980> part 00:14:14.329 --> 00:14:14.339 align:start position:0% interestingly the the the the core part 00:14:14.339 --> 00:14:16.190 align:start position:0% interestingly the the the the core part of<00:14:14.579> the<00:14:14.760> original<00:14:14.880> cloud<00:14:15.300> Foundry<00:14:15.899> was 00:14:16.190 --> 00:14:16.200 align:start position:0% of the original cloud Foundry was 00:14:16.200 --> 00:14:18.710 align:start position:0% of the original cloud Foundry was implemented<00:14:16.920> in<00:14:17.100> groovy<00:14:17.639> right<00:14:18.420> and<00:14:18.600> the 00:14:18.710 --> 00:14:18.720 align:start position:0% implemented in groovy right and the 00:14:18.720 --> 00:14:20.690 align:start position:0% implemented in groovy right and the reason<00:14:18.839> I<00:14:19.019> like<00:14:19.200> groovy<00:14:19.800> is<00:14:19.980> that<00:14:20.160> it's<00:14:20.339> a<00:14:20.579> very 00:14:20.690 --> 00:14:20.700 align:start position:0% reason I like groovy is that it's a very 00:14:20.700 --> 00:14:23.449 align:start position:0% reason I like groovy is that it's a very expressive<00:14:21.480> language<00:14:22.019> right<00:14:22.560> you've<00:14:23.220> sort<00:14:23.339> of 00:14:23.449 --> 00:14:23.459 align:start position:0% expressive language right you've sort of 00:14:23.459 --> 00:14:25.610 align:start position:0% expressive language right you've sort of got<00:14:23.639> some<00:14:23.940> kind<00:14:24.120> of<00:14:24.300> functional<00:14:24.839> capabilities 00:14:25.610 --> 00:14:25.620 align:start position:0% got some kind of functional capabilities 00:14:25.620 --> 00:14:27.590 align:start position:0% got some kind of functional capabilities where<00:14:26.519> you<00:14:26.700> can<00:14:26.820> sort<00:14:27.000> of<00:14:27.120> map<00:14:27.360> over 00:14:27.590 --> 00:14:27.600 align:start position:0% where you can sort of map over 00:14:27.600 --> 00:14:30.170 align:start position:0% where you can sort of map over Collections<00:14:28.560> and<00:14:28.800> filter<00:14:29.100> and<00:14:29.399> that<00:14:29.880> kind<00:14:30.060> of 00:14:30.170 --> 00:14:30.180 align:start position:0% Collections and filter and that kind of 00:14:30.180 --> 00:14:31.670 align:start position:0% Collections and filter and that kind of thing 00:14:31.670 --> 00:14:31.680 align:start position:0% thing 00:14:31.680 --> 00:14:34.490 align:start position:0% thing um<00:14:31.740> so<00:14:31.920> I<00:14:32.100> I<00:14:32.220> love<00:14:33.120> the<00:14:33.420> expressivity<00:14:34.200> of 00:14:34.490 --> 00:14:34.500 align:start position:0% um so I I love the expressivity of 00:14:34.500 --> 00:14:36.889 align:start position:0% um so I I love the expressivity of groovy<00:14:35.160> well<00:14:35.639> the<00:14:35.820> expressiveness<00:14:36.420> rather<00:14:36.660> of 00:14:36.889 --> 00:14:36.899 align:start position:0% groovy well the expressiveness rather of 00:14:36.899 --> 00:14:39.910 align:start position:0% groovy well the expressiveness rather of groovy<00:14:37.320> but<00:14:37.740> then<00:14:37.920> I<00:14:38.279> got<00:14:38.399> very<00:14:38.700> frustrated<00:14:39.180> by 00:14:39.910 --> 00:14:39.920 align:start position:0% groovy but then I got very frustrated by 00:14:39.920 --> 00:14:44.269 align:start position:0% groovy but then I got very frustrated by Dynamic<00:14:40.920> typing<00:14:41.519> I 00:14:44.269 --> 00:14:44.279 align:start position:0% Dynamic typing I 00:14:44.279 --> 00:14:45.710 align:start position:0% Dynamic typing I you<00:14:44.339> know<00:14:44.820> I<00:14:44.940> should<00:14:45.120> have<00:14:45.240> written<00:14:45.540> more 00:14:45.710 --> 00:14:45.720 align:start position:0% you know I should have written more 00:14:45.720 --> 00:14:48.889 align:start position:0% you know I should have written more tests<00:14:46.199> I<00:14:46.440> know<00:14:46.620> that<00:14:46.920> but<00:14:47.639> but<00:14:48.120> basically<00:14:48.660> when 00:14:48.889 --> 00:14:48.899 align:start position:0% tests I know that but but basically when 00:14:48.899 --> 00:14:50.930 align:start position:0% tests I know that but but basically when you<00:14:49.079> have<00:14:49.260> to<00:14:49.440> execute<00:14:49.980> your<00:14:50.279> code<00:14:50.459> in<00:14:50.699> order 00:14:50.930 --> 00:14:50.940 align:start position:0% you have to execute your code in order 00:14:50.940 --> 00:14:53.990 align:start position:0% you have to execute your code in order to<00:14:51.300> find<00:14:51.480> typos<00:14:52.139> that's<00:14:52.980> really<00:14:53.399> frustrating 00:14:53.990 --> 00:14:54.000 align:start position:0% to find typos that's really frustrating 00:14:54.000 --> 00:14:56.030 align:start position:0% to find typos that's really frustrating right<00:14:54.540> and<00:14:54.839> there<00:14:55.199> were<00:14:55.320> a<00:14:55.440> few<00:14:55.560> especially 00:14:56.030 --> 00:14:56.040 align:start position:0% right and there were a few especially 00:14:56.040 --> 00:14:58.610 align:start position:0% right and there were a few especially when<00:14:56.279> some<00:14:56.519> of<00:14:56.699> the<00:14:56.820> tests<00:14:57.180> even<00:14:57.440> launch<00:14:58.440> an 00:14:58.610 --> 00:14:58.620 align:start position:0% when some of the tests even launch an 00:14:58.620 --> 00:15:02.090 align:start position:0% when some of the tests even launch an ec2<00:14:59.160> instance<00:14:59.699> and<00:15:00.540> then<00:15:00.720> fail<00:15:01.079> right<00:15:01.560> that's 00:15:02.090 --> 00:15:02.100 align:start position:0% ec2 instance and then fail right that's 00:15:02.100 --> 00:15:04.250 align:start position:0% ec2 instance and then fail right that's a<00:15:02.399> you<00:15:02.699> know<00:15:02.820> that<00:15:03.000> that<00:15:03.240> process<00:15:03.720> back<00:15:04.079> then 00:15:04.250 --> 00:15:04.260 align:start position:0% a you know that that process back then 00:15:04.260 --> 00:15:05.750 align:start position:0% a you know that that process back then took<00:15:04.620> many<00:15:04.860> minutes 00:15:05.750 --> 00:15:05.760 align:start position:0% took many minutes 00:15:05.760 --> 00:15:09.470 align:start position:0% took many minutes and<00:15:06.720> so<00:15:07.079> I<00:15:07.620> wanted<00:15:07.800> an<00:15:08.519> expressive<00:15:09.060> language 00:15:09.470 --> 00:15:09.480 align:start position:0% and so I wanted an expressive language 00:15:09.480 --> 00:15:11.829 align:start position:0% and so I wanted an expressive language with<00:15:10.199> static<00:15:10.620> typing 00:15:11.829 --> 00:15:11.839 align:start position:0% with static typing 00:15:11.839 --> 00:15:16.310 align:start position:0% with static typing and<00:15:12.839> so<00:15:13.199> I<00:15:13.560> think<00:15:13.680> it<00:15:13.800> was<00:15:13.980> back<00:15:14.220> in<00:15:14.459> 2009<00:15:15.360> 2008 00:15:16.310 --> 00:15:16.320 align:start position:0% and so I think it was back in 2009 2008 00:15:16.320 --> 00:15:20.870 align:start position:0% and so I think it was back in 2009 2008 I<00:15:17.100> discovered<00:15:17.639> Scala<00:15:18.380> and<00:15:19.380> got<00:15:19.980> very<00:15:20.279> excited 00:15:20.870 --> 00:15:20.880 align:start position:0% I discovered Scala and got very excited 00:15:20.880 --> 00:15:22.910 align:start position:0% I discovered Scala and got very excited by<00:15:21.300> it 00:15:22.910 --> 00:15:22.920 align:start position:0% by it 00:15:22.920 --> 00:15:26.629 align:start position:0% by it um<00:15:23.040> and<00:15:23.579> you<00:15:24.120> know<00:15:24.180> to<00:15:24.839> this<00:15:25.079> day<00:15:25.320> I<00:15:25.620> I<00:15:25.800> still 00:15:26.629 --> 00:15:26.639 align:start position:0% um and you know to this day I I still 00:15:26.639 --> 00:15:30.290 align:start position:0% um and you know to this day I I still quite<00:15:27.240> like<00:15:27.720> Scarlet<00:15:28.380> though<00:15:28.860> I'm<00:15:29.300> somewhat 00:15:30.290 --> 00:15:30.300 align:start position:0% quite like Scarlet though I'm somewhat 00:15:30.300 --> 00:15:33.050 align:start position:0% quite like Scarlet though I'm somewhat frustrated<00:15:30.899> by<00:15:31.320> the<00:15:31.560> slow<00:15:31.800> compilation<00:15:32.579> times 00:15:33.050 --> 00:15:33.060 align:start position:0% frustrated by the slow compilation times 00:15:33.060 --> 00:15:36.170 align:start position:0% frustrated by the slow compilation times and<00:15:33.720> the<00:15:33.959> slow<00:15:34.139> ID<00:15:34.440> and<00:15:34.980> and<00:15:35.220> this<00:15:35.519> quality<00:15:36.000> of 00:15:36.170 --> 00:15:36.180 align:start position:0% and the slow ID and and this quality of 00:15:36.180 --> 00:15:40.970 align:start position:0% and the slow ID and and this quality of the<00:15:36.300> Ides<00:15:36.860> do<00:15:37.860> you<00:15:37.980> still<00:15:38.100> write<00:15:38.339> job<00:15:38.639> as<00:15:38.820> well 00:15:40.970 --> 00:15:40.980 align:start position:0% the Ides do you still write job as well 00:15:40.980 --> 00:15:44.870 align:start position:0% the Ides do you still write job as well only<00:15:41.820> when<00:15:42.420> I<00:15:42.720> have<00:15:42.899> to<00:15:43.139> okay<00:15:43.740> I<00:15:44.339> find<00:15:44.519> it<00:15:44.699> very 00:15:44.870 --> 00:15:44.880 align:start position:0% only when I have to okay I find it very 00:15:44.880 --> 00:15:47.509 align:start position:0% only when I have to okay I find it very frustrating<00:15:45.360> actually<00:15:45.720> it's<00:15:46.139> sort<00:15:46.620> of<00:15:46.740> you 00:15:47.509 --> 00:15:47.519 align:start position:0% frustrating actually it's sort of you 00:15:47.519 --> 00:15:50.090 align:start position:0% frustrating actually it's sort of you know<00:15:47.639> give<00:15:48.120> you<00:15:48.240> an<00:15:48.360> example<00:15:48.779> so<00:15:49.260> for<00:15:49.980> the 00:15:50.090 --> 00:15:50.100 align:start position:0% know give you an example so for the 00:15:50.100 --> 00:15:52.189 align:start position:0% know give you an example so for the event<00:15:50.399> sourcing<00:15:51.060> stuff<00:15:51.300> that<00:15:51.600> I<00:15:51.720> did<00:15:51.839> I 00:15:52.189 --> 00:15:52.199 align:start position:0% event sourcing stuff that I did I 00:15:52.199 --> 00:15:54.470 align:start position:0% event sourcing stuff that I did I actually<00:15:52.380> had<00:15:53.220> a<00:15:53.459> scholar<00:15:53.940> and<00:15:54.180> spring 00:15:54.470 --> 00:15:54.480 align:start position:0% actually had a scholar and spring 00:15:54.480 --> 00:15:56.870 align:start position:0% actually had a scholar and spring example<00:15:55.139> and<00:15:55.380> I<00:15:55.620> thought<00:15:55.740> I'd<00:15:55.920> open<00:15:56.160> it<00:15:56.399> up<00:15:56.579> to 00:15:56.870 --> 00:15:56.880 align:start position:0% example and I thought I'd open it up to 00:15:56.880 --> 00:15:59.090 align:start position:0% example and I thought I'd open it up to a<00:15:57.060> wider<00:15:57.420> audience<00:15:57.720> by<00:15:58.079> having<00:15:58.320> a<00:15:58.560> Java<00:15:58.980> and 00:15:59.090 --> 00:15:59.100 align:start position:0% a wider audience by having a Java and 00:15:59.100 --> 00:16:02.629 align:start position:0% a wider audience by having a Java and spring<00:15:59.339> example<00:16:00.079> and<00:16:01.079> the<00:16:01.380> amount<00:16:01.800> of<00:16:01.980> typing 00:16:02.629 --> 00:16:02.639 align:start position:0% spring example and the amount of typing 00:16:02.639 --> 00:16:05.810 align:start position:0% spring example and the amount of typing that<00:16:03.420> required<00:16:04.019> right<00:16:04.320> like<00:16:04.860> a<00:16:05.160> simple<00:16:05.339> case 00:16:05.810 --> 00:16:05.820 align:start position:0% that required right like a simple case 00:16:05.820 --> 00:16:08.569 align:start position:0% that required right like a simple case class<00:16:06.180> in<00:16:06.540> scholar<00:16:07.079> expands<00:16:07.800> out<00:16:07.920> into<00:16:08.220> a 00:16:08.569 --> 00:16:08.579 align:start position:0% class in scholar expands out into a 00:16:08.579 --> 00:16:11.090 align:start position:0% class in scholar expands out into a whole<00:16:08.760> file<00:16:09.180> of<00:16:09.420> java<00:16:09.959> code<00:16:10.079> with<00:16:10.440> Getters<00:16:10.860> and 00:16:11.090 --> 00:16:11.100 align:start position:0% whole file of java code with Getters and 00:16:11.100 --> 00:16:12.829 align:start position:0% whole file of java code with Getters and Setters<00:16:11.519> and<00:16:11.760> it's<00:16:11.940> like 00:16:12.829 --> 00:16:12.839 align:start position:0% Setters and it's like 00:16:12.839 --> 00:16:15.590 align:start position:0% Setters and it's like I<00:16:13.380> hate<00:16:13.500> this<00:16:13.800> it's<00:16:14.220> frustrating 00:16:15.590 --> 00:16:15.600 align:start position:0% I hate this it's frustrating 00:16:15.600 --> 00:16:17.449 align:start position:0% I hate this it's frustrating well<00:16:16.019> I<00:16:16.199> mean<00:16:16.380> certainly<00:16:16.620> skull<00:16:17.040> is<00:16:17.160> more 00:16:17.449 --> 00:16:17.459 align:start position:0% well I mean certainly skull is more 00:16:17.459 --> 00:16:20.569 align:start position:0% well I mean certainly skull is more concises<00:16:18.060> yes<00:16:18.540> yeah<00:16:18.899> yeah<00:16:19.019> I<00:16:19.560> just<00:16:19.680> love<00:16:19.920> I 00:16:20.569 --> 00:16:20.579 align:start position:0% concises yes yeah yeah I just love I 00:16:20.579 --> 00:16:22.610 align:start position:0% concises yes yeah yeah I just love I love<00:16:20.760> the<00:16:21.060> expressiveness<00:16:21.839> of<00:16:22.019> it<00:16:22.139> but<00:16:22.500> then 00:16:22.610 --> 00:16:22.620 align:start position:0% love the expressiveness of it but then 00:16:22.620 --> 00:16:25.009 align:start position:0% love the expressiveness of it but then at<00:16:22.800> the<00:16:22.980> same<00:16:23.100> time<00:16:23.339> I<00:16:23.699> actually<00:16:24.120> got<00:16:24.420> to<00:16:24.600> use<00:16:24.779> a 00:16:25.009 --> 00:16:25.019 align:start position:0% at the same time I actually got to use a 00:16:25.019 --> 00:16:27.530 align:start position:0% at the same time I actually got to use a Java<00:16:25.440> IDE<00:16:25.680> again<00:16:26.279> and<00:16:26.519> it<00:16:26.699> was<00:16:26.820> like<00:16:27.060> oh<00:16:27.360> yeah 00:16:27.530 --> 00:16:27.540 align:start position:0% Java IDE again and it was like oh yeah 00:16:27.540 --> 00:16:30.350 align:start position:0% Java IDE again and it was like oh yeah this<00:16:27.839> is<00:16:27.959> how<00:16:28.199> an<00:16:28.380> idea<00:16:28.740> how<00:16:29.220> how<00:16:29.880> a<00:16:30.240> really 00:16:30.350 --> 00:16:30.360 align:start position:0% this is how an idea how how a really 00:16:30.360 --> 00:16:33.290 align:start position:0% this is how an idea how how a really good<00:16:30.540> ide<00:16:30.839> Works<00:16:31.680> yes<00:16:32.040> absolutely<00:16:32.940> well 00:16:33.290 --> 00:16:33.300 align:start position:0% good ide Works yes absolutely well 00:16:33.300 --> 00:16:34.910 align:start position:0% good ide Works yes absolutely well hopefully<00:16:33.720> we'll<00:16:33.899> see<00:16:34.079> much<00:16:34.320> more<00:16:34.440> we<00:16:34.740> already 00:16:34.910 --> 00:16:34.920 align:start position:0% hopefully we'll see much more we already 00:16:34.920 --> 00:16:36.370 align:start position:0% hopefully we'll see much more we already see<00:16:35.160> a<00:16:35.279> lot<00:16:35.339> of<00:16:35.459> progress 00:16:36.370 --> 00:16:36.380 align:start position:0% see a lot of progress 00:16:36.380 --> 00:16:38.990 align:start position:0% see a lot of progress and<00:16:37.380> we'll<00:16:37.560> see<00:16:37.800> a<00:16:38.040> little<00:16:38.100> more<00:16:38.279> of<00:16:38.399> it<00:16:38.519> well 00:16:38.990 --> 00:16:39.000 align:start position:0% and we'll see a little more of it well 00:16:39.000 --> 00:16:40.370 align:start position:0% and we'll see a little more of it well this<00:16:39.240> is<00:16:39.360> great<00:16:39.540> stuff<00:16:39.720> Chris<00:16:40.019> so<00:16:40.259> we're 00:16:40.370 --> 00:16:40.380 align:start position:0% this is great stuff Chris so we're 00:16:40.380 --> 00:16:41.509 align:start position:0% this is great stuff Chris so we're looking<00:16:40.560> forward<00:16:40.740> to<00:16:40.920> your<00:16:41.100> talking<00:16:41.220> it's 00:16:41.509 --> 00:16:41.519 align:start position:0% looking forward to your talking it's 00:16:41.519 --> 00:16:42.949 align:start position:0% looking forward to your talking it's great<00:16:41.699> to<00:16:41.880> have<00:16:41.940> you<00:16:42.060> in<00:16:42.240> the<00:16:42.360> community<00:16:42.480> it's 00:16:42.949 --> 00:16:42.959 align:start position:0% great to have you in the community it's 00:16:42.959 --> 00:16:44.509 align:start position:0% great to have you in the community it's great<00:16:43.199> around<00:16:43.380> these<00:16:43.680> joint<00:16:43.860> events<00:16:44.220> and<00:16:44.339> I 00:16:44.509 --> 00:16:44.519 align:start position:0% great around these joint events and I 00:16:44.519 --> 00:16:46.490 align:start position:0% great around these joint events and I hope<00:16:44.639> we'll<00:16:44.940> run<00:16:45.420> more<00:16:45.660> events<00:16:46.019> like<00:16:46.199> this<00:16:46.320> in 00:16:46.490 --> 00:16:46.500 align:start position:0% hope we'll run more events like this in 00:16:46.500 --> 00:16:52.850 align:start position:0% hope we'll run more events like this in Auckland<00:16:46.800> yeah<00:16:47.220> same<00:16:47.519> here<00:16:47.699> thank<00:16:48.060> you<00:16:48.180> thanks 00:16:52.850 --> 00:16:52.860 align:start position:0% 00:16:52.860 --> 00:16:55.860 align:start position:0% foreign