WEBVTT

NOTE
This file was generated by Descript 

00:00:00.728 --> 00:00:04.718
Raphaël: Hey, and welcome back to
our series on EC's methodology.

00:00:05.718 --> 00:00:09.408
Last time we talked about
growth and scalability.

00:00:09.588 --> 00:00:12.198
Today, we're going to
talk about infrastructure.

00:00:13.198 --> 00:00:16.768
There are different places you might
want to deploy your application to.

00:00:17.128 --> 00:00:19.108
Remember when we talked
about growth planning?

00:00:19.378 --> 00:00:23.128
Well, you're going to want to use
that growth planning to decide

00:00:23.128 --> 00:00:24.958
what infrastructure to deploy to.

00:00:25.958 --> 00:00:26.348
Okay.

00:00:26.378 --> 00:00:30.128
So you've got your growth curve
mapped out and you're ready

00:00:30.128 --> 00:00:31.628
to start designing this thing.

00:00:32.628 --> 00:00:35.508
One of the things you'll need to
know before you get started is

00:00:35.838 --> 00:00:39.938
what are the capabilities of the
infrastructure I plan to deploy to.

00:00:40.938 --> 00:00:44.448
Basically, you need to know
what you can and can't do with

00:00:44.448 --> 00:00:46.308
the resources available to you.

00:00:47.308 --> 00:00:52.618
For example, if you're deploying a static
site, you can get away with services

00:00:52.618 --> 00:00:55.588
like Firebase Hosting or Netlify.

00:00:56.588 --> 00:01:00.068
However, if you know that your
system is going to require complex

00:01:00.068 --> 00:01:04.688
relational data, you'll probably
need a relational database.

00:01:05.688 --> 00:01:08.838
If you know you're going to keep
things relatively simple, then you

00:01:08.838 --> 00:01:12.648
could use a service like Heroku and
their Postgres database offering.

00:01:13.648 --> 00:01:16.888
If you know you're going to be
building a few different services

00:01:16.888 --> 00:01:20.818
and you want cost stability and
simplicity, then DigitalOcean

00:01:20.818 --> 00:01:22.258
might be a good option for you.

00:01:22.808 --> 00:01:27.098
DigitalOcean's Kubernetes platform
is our go-to for clients who have

00:01:27.098 --> 00:01:29.288
those sort of in-between needs.

00:01:30.288 --> 00:01:34.518
Finally, if you know you're going to
be building complex systems need to

00:01:34.518 --> 00:01:39.918
scale out a lot, have solid engineers,
and your budget isn't too limited,

00:01:40.128 --> 00:01:44.668
then you'll probably want to use one
of the big cloud hosting platforms.

00:01:45.668 --> 00:01:49.208
The two big cloud platforms
we like best are Google Cloud

00:01:49.208 --> 00:01:51.488
Platform and Amazon Web Services.

00:01:51.518 --> 00:01:54.525
But we also know people who
have built amazing things with

00:01:54.525 --> 00:01:56.105
Microsoft's Azure Offering.

00:01:56.179 --> 00:02:01.069
You can keep costs slow with these
big platforms, but it's also easy

00:02:01.069 --> 00:02:05.549
to accidentally rack up a higher
bill because of the complexity.

00:02:06.319 --> 00:02:10.049
You'll also need a more senior engineer to
make sure things are properly configured.

00:02:11.049 --> 00:02:14.079
We'd love to hear what your
favorite platforms are and why.

00:02:14.139 --> 00:02:15.099
So let us know.

00:02:15.243 --> 00:02:16.023
And follow us.

00:02:16.023 --> 00:02:19.353
If you want to keep up with the series,
we've got loads, more stuff we want to

00:02:19.353 --> 00:02:23.703
share with you, and we're constantly
updating our process as we learn from

00:02:23.703 --> 00:02:26.443
ourselves, our partners and our community.

00:02:27.443 --> 00:02:30.593
If you think we could work together,
we'd love to partner with you and

00:02:30.593 --> 00:02:32.993
help you out with your next project.

00:02:33.473 --> 00:02:34.993
Thanks and see you next time.