Built on what?
Summary
Next in our EC Methodology Series... infrastructure! One of the things you’ll need to know before you get going is “what are the capabilities of the infrastructure I’ll be deploying to.” You'll need to know what you can and can't do with the resources you have available to you.Raphaël: Hey, and welcome back to
our series on EC's methodology.
Last time we talked about
growth and scalability.
Today, we're going to
talk about infrastructure.
There are different places you might
want to deploy your application to.
Remember when we talked
about growth planning?
Well, you're going to want to use
that growth planning to decide
what infrastructure to deploy to.
Okay.
So you've got your growth curve
mapped out and you're ready
to start designing this thing.
One of the things you'll need to
know before you get started is
what are the capabilities of the
infrastructure I plan to deploy to.
Basically, you need to know
what you can and can't do with
the resources available to you.
For example, if you're deploying a static
site, you can get away with services
like Firebase Hosting or Netlify.
However, if you know that your
system is going to require complex
relational data, you'll probably
need a relational database.
If you know you're going to keep
things relatively simple, then you
could use a service like Heroku and
their Postgres database offering.
If you know you're going to be
building a few different services
and you want cost stability and
simplicity, then DigitalOcean
might be a good option for you.
DigitalOcean's Kubernetes platform
is our go-to for clients who have
those sort of in-between needs.
Finally, if you know you're going to
be building complex systems need to
scale out a lot, have solid engineers,
and your budget isn't too limited,
then you'll probably want to use one
of the big cloud hosting platforms.
The two big cloud platforms
we like best are Google Cloud
Platform and Amazon Web Services.
But we also know people who
have built amazing things with
Microsoft's Azure Offering.
You can keep costs slow with these
big platforms, but it's also easy
to accidentally rack up a higher
bill because of the complexity.
You'll also need a more senior engineer to
make sure things are properly configured.
We'd love to hear what your
favorite platforms are and why.
So let us know.
And follow us.
If you want to keep up with the series,
we've got loads, more stuff we want to
share with you, and we're constantly
updating our process as we learn from
ourselves, our partners and our community.
If you think we could work together,
we'd love to partner with you and
help you out with your next project.
Thanks and see you next time.