App Server Architecture - Web DevelopmentYouTube↗  IA↗(long shot)
Education  14K views 52 likes 5 dislikes   27 May 2012
Udacity 651K subscribers United States YouTube↗


Please select the problem
You must specify your email and describe the problem in detail
Describe your problem in detail if it's not obvious

Click to Play Video Click to Play Video
behind a chair proxy we actually get
ではRedditのインフラの中身について話します
into the meat of reddit's infrastructure we had a bunch of app servers these are
私たちはAPサーバをたくさん持っていました
these are physical machines that are running Python programs like you've been
それらはこの講義でやってきたような[br]Pythonプログラムを実行する物理的なマシンです
working on in this class when I laughed I think we had maybe 20 of these um I
私が辞めた頃はおそらく20台はあったと思います
was in that many how many do you guys
今は何台くらいありますか?
have now uh 180 I'm okay so that's
180台ですね
pretty significant so we went they went
それはすごい数ですね
from 20 when reddit was a big site to 180 when reddit became a huge site now
Redditが大規模なサイトだった時の20台から[br]更に巨大になった今では180台になりました
these are running Python they're there
現在このサーバではPythonを使っており
they're using a web framework that I talked about previously in this unit
フレームワークは以前お話ししたPylonsを使っています
called pylons do you guys still use pylons yes yeah mostly coastal there yep
まだPylonsを使っていますか?
and so this handle just about every
Pylonsは ほぼ全てのリクエストを処理してくれました
request um I don't recall if we had special web servers for static content
以前静的コンテンツに特別なWebサーバを使っていたか
do you guys have special web servers now
思い出せませんが今は何か使っていますか?
for static content we use s3
Amazon S3です
that's three for static oh yes yes we transition to that at some point before
そうでした　辞める前に[br]ちょうどAmazon S3に切り替えていましたね
I left so everything we do is on Amazon
すべてをAmazonのAWS上で行っています
AWS basically you rent machines from Amazon and one of the systems in AWS is s3 maybe you could explain yeah what s3
AWSのシステムの1つがAmazon S3で[br]基本的にAmazonからマシンを借ります Amazon S3の内容と機能を[br]ちょっと説明してみてくれませんか?
is and how it works sure s3 is simple storage service and it's basically a distributed file storage thing in the cloud and Amazon
Amazon S3は単純なストレージサービスで 基本的には[br]クラウドにおける分散型ファイルストレージです
lets you put objects into the bucket and it's literally just a key value store of these files and other people can hit a URL and grab the object so we store all
S3ではオブジェクトをバケットに入れられますが[br]それが そのファイルのキー値の保存先となります そして第三者がURLを入力し[br]そのオブジェクトをつかむことができるんです
of our static content like CSS and JavaScript on s3 and when you're hitting
私たちはCSSやJavaScriptのような静的コンテンツを[br]S3上に保存しています
the site you're actually going via our Chrome I to s3 instead of our
皆さんがサイトにアクセスする時[br]実際にはAkamai経由でS3に行っているのです
infrastructure so for static content a user never even hits H a proxy or the app servers or anything at all yes for
では静的コンテンツに関してはユーザがHAProxyや[br]APサーバにアクセスすることは全くないんですね?
the most part and we can get away with
ええ　大部分はそうです
that because the content never changes
コンテンツは変わらないので[br]私たちは何もしなくていいですね
right so I know in the early days with Reddit and certainly in the applications
Redditの初期の頃から構築してきた全コンテンツは
we've been building this class you know all the content static or not get served from these app service and as you grow there's no
APサーバから提供されているとお話ししましたね
reason why you need to waste you know
規模が大きくなる過程でJavaScriptやCSS画像との
all these resources handling connections for JavaScript and CSS and images and
つながりを処理するために[br]時間を無駄に使いたくないからです
and and for awhile we were using nginx for the static content I think we were
しばらくの間は[br]静的コンテンツにEngineXを使用していました
just in transition when I left some of
辞める頃に移行しましたっけ?
the static was on s3 and we just moved all the CSS and stuff in October so we
コンテンツのいくつかはS3上にありましたが[br]10月に全CSSなどを移したばかりです
were using nginx and it got to the point where the one nginx server doing all of
EngineXを使っていたのですが[br]コンテンツを変更した際に
the static content couldn't handle it anymore when we changed the content and
あるEngineXサーバが[br]もう処理しきれなくなってしまったのです
everybody's caches were invalidated and
全員のキャッシュが無効化されました
so we would do a deploy of new code and there would be this static content
それで新しいコードを展開し[br]静的コンテンツの変更がされる予定でしたが
change and all of a sudden that nginx
突然EngineXがオーバーロードしてしまい
would get overloaded and everybody would be getting completely unstyled read it
未完成のRedditが[br]ユーザの目に触れることになったのです
it seemed that happen a few times yeah
そうですね　私も何度か目にしました
and so nginx is just a web server you
つまりEngineXはただのWebサーバなのです
know back in the early days of the internet almost all the content online
ネットが普及し始めた頃は[br]オンラインのほぼ全コンテンツが静的でした
was stack and it was served by this
コンテンツはWebサーバから提供されていました
things called web servers which basically take HTTP requests find a file you know that was in the URL like the
WebサーバはHTTPリクエストを受け取り[br]URL中のファイルを探します
actual file name map directly to a file
URLはサーバ上のあるファイルに直接関連づけられた[br]実際のファイル名のようなもので
on the web server and they would serve
そうしてサーバはコンテンツを提供するのです
and that was basically almost the entire
これがインターネットのすべてでした
Internet in over the last 15 years the content online has changed from basically being 100% static to almost on
ここ15年でオンラインのコンテンツは[br]基本的に100％静的から
recent dynamic and in fact when I
ほぼ100％動的へと変化しました
started teaching this course in unit 1 I
現在100％静的なウェブサイトがあるか[br]思い出してみましたが
was trying to think of a website that was 100% static and I can't think of
1つも思いつきませんでした
what do you do I mean do you have any idea someone I'll stop your head so
何か思いつくものはありますか?
there's actually been a resurgence of static in the form of websites that get
実はファイルからコンパイルされたWebサイトの形式で[br]スタティック復活の動きがありました
compiled from files ok and so there's
現在実際には完全に静的に提供されているブログが[br]たくさんありますが
actually a lot of blogs out there now that are purely static served but are generated from files dynamically we're
実際それらは動的ファイルから生成されているのです
going to talk about how how much content reddit precompute is like a form of like
次はRedditの事前計算についてお話しします
this we talked about unit 6 is kind of
レッスン6でキャッシュの概念について説明しましたね
notion of caching and then you can wait to cache something until it's needed or you can cache it ahead of time so that
キャッシングは必要な時にも[br]また事前にもすることができます
the user never actually touches the
ですからユーザが実際にデータベースに[br]触れることはありません
database and what you're getting at is
目指しているのはこの究極の形ですね?
like an extreme form of that yeah yeah you know you only compile it when you
ええ　コンパイルするのは[br]必要な時と変更する時だけです
need to when you change it so you build up your whole blog I guess so static
たとえば静的コンテンツで[br]ブログ全体を構築するなどでしょうか
content and then sad content I mean the whole thing is it's really easy to serve
とにかく静的コンテンツは[br]とても簡単に提供できるのです
because it's the same for everybody yeah you know having static content in s3 or nginx even when read it was pretty big
私が辞めた時はすでに[br]静的コンテンツはかなり膨大な数でしたが
when I left we could get away with one web server there because Akamai handled
Akamaiがほとんどの負荷を処理していました
most of the load and Akamai is pretty clever about oh this this piece of contents about to expire I'll go ahead
Akamaiは期限の切れそうなコンテンツに関しては[br]かなり優れているんです
and fetch it in advance and then to keep
ユーザがAkamaiからすり抜けないように[br]またサーバに負荷をかけないように
the users from all slipping through a command pounding this guy
先に行って前もってコンテンツを取得するのです
Similar videos:

Locking and Memcache - Web Development
Udacity
5.6K views 16 likes 0 dislikes 27 May 2012100% match

Scaling - Web Development
Udacity
12.5K views 81 likes 1 dislikes 27 May 2012100% match

Port - Web Development
Udacity
15.8K views 18 likes 0 dislikes 23 Feb 2015100% match

Italics
Udacity
49.1K views 16 likes 2 dislikes 23 Feb 2015100% match

Dynamic Content - Web Development
Udacity
6.1K views 2 likes 0 dislikes 23 Feb 2015100% match

Code Organization - Web Development
Udacity
7.2K views 25 likes 1 dislikes 27 May 2012100% match

Web 简介
Udacity
25.7K views 60 likes 0 dislikes 23 Feb 2015100% match

Whitespace Solution - Web Development
Udacity
15.7K views 10 likes 1 dislikes 23 Feb 2015100% match

The Method Attribute - Web Development
Udacity
9.6K views 14 likes 8 dislikes 22 Apr 2012100% match

Cache Architecture - Web Development
Udacity
7.2K views 16 likes 1 dislikes 27 May 2012100% match

Telnet Request - Web Development
Udacity
8.2K views 2 likes 0 dislikes 23 Feb 2015100% match

Components of the Web Solution - Web Development
Udacity
9.6K views 19 likes 0 dislikes 23 Feb 2015100% match

Most Common Method - Web Development
Udacity
9.7K views 5 likes 0 dislikes 23 Feb 2015100% match

Shopping List Take 1 - Web Development
Udacity
841 views 1 likes 0 dislikes 23 Feb 2015100% match

Reddit Architecture - Web Development
Udacity
27.7K views 397 likes 3 dislikes 27 May 2012100% match

Bold Tag - Web Development
Udacity
53K views 29 likes 0 dislikes 23 Feb 2015100% match

Components of the Web
Udacity
28K views 54 likes 0 dislikes 23 Feb 2015100% match

Types of Databases - Web Development
Udacity
8.5K views 43 likes 4 dislikes 25 Apr 2012100% match

Caching - Web Development
Udacity
12.1K views 102 likes 0 dislikes 23 Feb 2015100% match

File Types
Udacity
34.4K views 11 likes 3 dislikes 23 Feb 2015100% match

Missing End Tag
Udacity
43K views 15 likes 1 dislikes 23 Feb 2015100% match

Introduction - Web Development
Udacity
23.3K views 107 likes 0 dislikes 23 Feb 2015100% match

Part 2 - Web Development
Udacity
643 views 2 likes 0 dislikes 07 May 2012100% match

The Action Attribute - Web Development
Udacity
7.5K views 7 likes 0 dislikes 22 Apr 2012100% match

Security - Web Development
Udacity
5.7K views 64 likes 0 dislikes 23 May 2012100% match

Datastore Types Solution - Web Development
Udacity
656 views 1 likes 0 dislikes 25 Apr 2012100% match

URL Encoding - Web Development
Udacity
13.7K views 17 likes 13 dislikes 22 Apr 2012100% match

Growing Reddit - Web Development
Udacity
82.7K views 484 likes 27 dislikes 27 May 2012100% match

App Server Scaling - Web Development
Udacity
28.2K views 277 likes 8 dislikes 23 Feb 201583% match

Reddit Architecture 2 - Web Development
Udacity
11.1K views 88 likes 2 dislikes 27 May 201275% match


Settings Privacy About Contact Donate