Skip to content

remove broken links on overview page #224

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 9, 2025
Merged

remove broken links on overview page #224

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 5 additions & 6 deletions docs/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,11 +12,10 @@ of data. In addition there were a number of trends in the company which presaged
increase in metric volume:

* Rolling pushes to [Red/Black deployments](http://techblog.netflix.com/2012/06/asgard-web-based-cloud-management-and.html).
* Leveraging [auto-scaling for large clusters](http://techblog.netflix.com/2012/01/auto-scaling-in-amazon-cloud.html).
Netflix has always used auto-scaling groups in AWS, but initially most were configured with fixed
size and just used as a group and to replace instances.
* Expansion internationally into [Latin America](http://blog.netflix.com/2011/07/netflix-is-coming-to-latin-america.html)
and [Europe](http://ukirelandblog.netflix.com/2012_01_01_archive.html). This led to an increase
* Leveraging auto-scaling for large clusters. Netflix has always used auto-scaling groups in AWS,
but initially most were configured with fixed size and just used as a group and to replace
instances.
* Expansion internationally into Latin America and Europe. This led to an increase
in the number of countries being tracked for key metrics and for Europe it was the first move
into additional AWS regions. With additional regions we also wanted to have better isolation so
a problem with monitoring in one region would not impact another, but at the same time have
Expand Down Expand Up @@ -330,4 +329,4 @@ come in the future:

These projects were originally developed and run internally and thus only needed to be setup by our
team and assume many internal infrastructure pieces to run. There is a goal to try and make this
easier, but it will take some time.
easier, but it will take some time.