WEBVTT

NOTE
This file was generated by Descript 

00:00:00.500 --> 00:00:05.000
Hey, and welcome back to our
series on EC's methodology.

00:00:05.500 --> 00:00:08.680
Last time we talked about services
you might need for your application.

00:00:09.180 --> 00:00:12.390
Today, we'll talk about
coordinating all of those services.

00:00:12.890 --> 00:00:16.760
Your services are an orchestra
and it needs a conductor.

00:00:17.260 --> 00:00:17.560
Okay.

00:00:17.560 --> 00:00:19.540
So we've got all of these services.

00:00:19.930 --> 00:00:22.810
And we know they need some
way to talk to each other.

00:00:23.310 --> 00:00:24.930
So, how do we do that?

00:00:25.430 --> 00:00:29.749
Everything we build gets turned
into a container, a way of

00:00:29.749 --> 00:00:33.980
packaging applications that was
popularized by a tool called Docker.

00:00:35.079 --> 00:00:39.019
So when we're developing, we recommend
using a tool called docker-compose

00:00:39.309 --> 00:00:41.799
to run and coordinate those services.

00:00:42.299 --> 00:00:45.240
Though, we're also exploring
an alternative called pod man.

00:00:45.740 --> 00:00:48.770
Now let's talk about getting all
of those services up and running

00:00:48.830 --> 00:00:50.450
in a production environment.

00:00:50.950 --> 00:00:55.450
Until a couple of years ago, we probably
would have spun up a bunch of virtual

00:00:55.450 --> 00:00:59.350
machines in auto scaling groups on AWS.

00:00:59.710 --> 00:01:02.020
In some cases we might still do that.

00:01:02.520 --> 00:01:06.400
But since the explosive growth
of Kubernetes an open source

00:01:06.420 --> 00:01:11.130
platform designed to orchestrate
containerized workloads, we find

00:01:11.130 --> 00:01:15.960
that to be a much better way of
deploying and managing our services.

00:01:16.460 --> 00:01:21.140
It has pros and cons, but one of
the advantages of Kubernetes is

00:01:21.140 --> 00:01:24.679
it's an open source system with
managed offerings on most cloud

00:01:24.679 --> 00:01:29.929
platforms, including Google, Amazon,
Microsoft, Digital Ocean, and others.

00:01:30.429 --> 00:01:33.999
So, if you build for Kubernetes, you
should be able to pick and choose

00:01:33.999 --> 00:01:36.489
the cloud that best suits your needs.

00:01:36.989 --> 00:01:40.440
Tell us about how you manage
and deploy your services.

00:01:40.940 --> 00:01:43.340
And follow us if you want
to keep up with this series.

00:01:43.840 --> 00:01:45.580
We have a lot more to share with you.

00:01:46.080 --> 00:01:48.029
We're constantly updating this process.

00:01:48.029 --> 00:01:51.749
As we learn from ourselves,
our partners and our community.

00:01:52.249 --> 00:01:55.549
If you think we could work together,
we'd love to partner with you and

00:01:55.549 --> 00:01:57.649
help you out with your next project.

00:01:58.070 --> 00:01:59.960
Thanks and see you next time.