Let's begin our dialogue with one of the most well-known examples of software
development
and DevOps.
And that is Amazon.com.
That's what you're seeing right here on the screen.
We've got Amazon.com up.
I want you to think about this for a second.
When was the last time you saw Amazon.com go down for maintenance?
I mean, they ship updates quite literally every single day to this website.
Whether it's new features or changing the UI or changing something in the back WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Whether it's new features or changing the UI or changing something in the back
end.
They're changing something with this application every single day.
They are multiple times a day even.
But it never goes down.
And then the next thing is when was the last time you saw some major hack or
threat take
place on Amazon.com?
I'm racking my brain and I can't think of a time for either. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I'm racking my brain and I can't think of a time for either.
And I've been shopping on Amazon.com literally for over 20 years now.
I made my first purchase on Amazon in 2005.
I bought a CD on Amazon.com in 2005.
And since then I don't recall a time that they ever took Amazon down for like
software
updates or operating system patches or any sort of threat that took it down.
Now there's things that can happen like somebody attacks a global DNS center WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now there's things that can happen like somebody attacks a global DNS center
and that could
be a big problem.
But for the most part, like that's not an Amazon specific problem.
That's a, you know, some global attack threat going on there.
Now I want you to think about this.
What is Amazon's product?
What is it that they build and ship and ultimately sell?
It's this marketplace, this marketplace right here, Amazon.com. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
It's this marketplace, this marketplace right here, Amazon.com.
It is a application.
They build software and that software is an online marketplace.
One of the biggest things that they ever did, really two of the biggest things
they ever
did was they enabled a way to vet other sellers to sell their products on their
website.
Amazon, of course, you know, takes a cut.
And then those sellers can piggyback off of Amazon's magical logistics, which WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then those sellers can piggyback off of Amazon's magical logistics, which
of course
Amazon really nailed down and that became with prime and two day shipping.
And even same day shipping, that became one of their competitive advantages.
But it ultimately starts right here, the thing that they build and sell is an
application,
a website and software.
It's the thing that they do.
It's the thing that they do best is building this website.
This is a lot different from other websites, right? WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
This is a lot different from other websites, right?
If you go to a website, you know, like an HVAC shop in your town, you go to
their site,
it's for the most part, a relatively static website where you're just getting
information
about their service, but then you have to call them and schedule them and then
they come
out and they perform the service and that's ultimately what they're selling.
The HVAC's website is not dynamic.
It's not an application.
You know, they're not really collecting a lot of data and they're not really WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
You know, they're not really collecting a lot of data and they're not really
generating
a lot of sales or revenue directly from their website because HVAC shops, like
a lot of
other shops, if not most other shops, don't build software for a living.
They perform a service.
Amazon.com is by definition a software company.
So what is the secret sauce that Amazon and Google and Meta all kind of figured
out at
the same time.
That is the software development lifecycle and cloud scale. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
That is the software development lifecycle and cloud scale.
And the thing that makes all of this work, the software development lifecycle
and cloud
scale applications is DevOps.
So what we're here to talk about now is how this comes to be.
How does DevOps come to be?
Well, what is DevOps at the end of the day?
The primary operation of this business is software development. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
The primary operation of this business is software development.
That's what they do.
So you'll have a lot of software developers, devs, sitting, you know, at home,
working
on their computer or sitting in an office, working on their computer and the
writing
code and the writing code and they're shipping that code to someplace.
They're storing that code in someplace.
You could think of it just as a very basic example as a file share, even though WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
You could think of it just as a very basic example as a file share, even though
that's
not what they're really doing.
But you could kind of think about it that way.
So the thing that happens, the big challenge that happened in the early 2000s
right around,
you know, the 2008, 2009 period is how do we get that new code that they've
written delivered
to a server and vetted so that we know that it works.
That this part right here, the delivery and testing and confirmation and then WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
That this part right here, the delivery and testing and confirmation and then
review and
feedback, that is all the operations that facilitate software development.
So when we think about DevOps, we're not really thinking about dev because
software developers
are doing that.
They've been doing dev for decades now. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
They've been doing dev for decades now.
When we start talking about DevOps, we're talking about how do we streamline
the process
of getting the devs work into the final server, knowing that once it's there,
it's going
to work and it's not going to break anything and it's not going to take
everything down.
How do we know that it's bug free?
This fundamentally is the point of DevOps.
The point of DevOps is to manage the operations that facilitate software WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
The point of DevOps is to manage the operations that facilitate software
development.
This ultimately came about because software developers don't really have a
problem sitting
on their computer writing code.
It's getting the code into its final resting place on a server that became the
real challenge.
If we start thinking about what really happened in those early 2000s, what did
really happen?
Well, it was time to deliver the code to the server. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Well, it was time to deliver the code to the server.
Did we have a server?
If not, who is going to deploy that server?
How do we configure that server?
Does the server need certain things in order to run the application?
What about the networking stack?
And then maybe a public DNS stack which goes along with it, firewall provision
ing, routing
the web servers traffic to the right back end page.
This all became a full stop because now we had to invoke a series of other team WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
This all became a full stop because now we had to invoke a series of other team
members
to come in and do a lot of work that took a long time.
So the software developer was mostly done for their work.
They were waiting for it to be reviewed and feedback given to them so they know
what to
do next.
But now we've stopped all progress for months because we're waiting for this
whole new set
of infrastructure to be deployed and everything else to facilitate this new WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
of infrastructure to be deployed and everything else to facilitate this new
application going
live.
So DevOps itself really became a lifestyle.
It's really a management practice of how we get software into the end state as
quickly
as possible.
So I'm sitting here telling you the way we were doing things used to take
months.
Now Amazon delivers new code multiple times per day. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now Amazon delivers new code multiple times per day.
How how did that much change in progress happen?
In the next video, we're going to start breaking apart how DevOps and CI CD
really works under
the hood.