Reddit Architecture - Web Development Udacity Japanese English

Reddit Architecture - Web DevelopmentYouTube↗ IA↗(long shot)
Education 27.7K views 397 likes 3 dislikes 27 May 2012

Udacity 651K subscribers United States YouTube↗

ではRedditのアーキテクチャについて説明します

The architecture originally looked something like this --we basically had one machine

名前は伏せますが[br]初めにマシンを1台レンタルした会社は最悪でした

that we were renting from this company--I'm not even going to mention their name, they're so bad.

いい会社のことだけ話しますね

I'll try to only mention companies I like.

ともかくそのマシンがRedditのすべてでした

But we are renting one machine and let's basically ran this, and this is all of Reddit.

そのマシンでPostgreSQLを動作させ

We're also running post quiz on this machine and that was it.

またインメモリハッシュテーブルを使っていました

We didn't have any fancy caching. I just used in-memory hash tables.

データベースは十分推測可能な構造で

The database had a fairly guessable structure.

テーブルはリンク用と投票用と[br]ユーザ用のものがありました

We had a table for links, we had a table for votes, and a table for users.

最初はそれくらいでしたね

That may have been it to begin with. There wasn't a whole lot to Reddit.

長いこと投稿はありませんでした

We didn't have any comments for a long while, and the links and votes tables

リンクと投票のテーブルにはスコアとタイトルと

were basically kind of as I represented them in this lecture.

URLがあり[br]投票にはIDとディレクションが必要で

These had things like score, title, URL. Vote basically had a length ID, a direction.

ユーザは名前とパスワードを持っていました

User had a name and a password.

私はパスワードを保存していたのですが

Notice I didn't say password hash-- I actually stored the password

それがしばしばトラブルを招いたのです

and told you that story how I'd gotten trouble as a result of doing that.

私たちは半年くらい結合を繰り返していました

We actually did a lot of joins--this lasted probably about for 6 months or so.

その後スタッフを2人雇いました

After 6 months, we hired a couple guys --well, we kind of merged our company

Infogamiという会社と合併して

with another company called Infogami and that brought us another engineer

アーロン･スワーツとクリス･スロウを迎えたのです

named Aaron Swartz and we hired Chris Slowe who was doing a PHD at the time.

私とアレクシスとアーロンとクリスの4人になりました

So the four of us--me, Alexis, Aaron and Chris-- worked on Reddit then.

アーロンと私でまず最初にしたのは

And the first change that Aaron and I made together was

LISPからPythonへの移行でした

we reroute Reddit from Lisp to Python.

それとほぼ同時に[br]データベースをマシンから取り出し

And then at about the same time, we pulled the database out of that one machine

2台目のマシンに移行しました

and put it on the second machine, and so now we had two machines

ホストに2台のサーバが入ったのです

with this hosting company--our app server and our DB.

このLISPからPythonへの移行が大変でした

And the switch from Lisp to Python was kind of performance agnostic.

LISPは速いのですがPythonは更によく

Lisp was a faster language but our rewrite of Python was better,

ほぼ同じ速さでコードが動きました

so the code actually run at about the same speed.

1台から2台のマシンに移行すると[br]4倍のスピードになるのです

Going from one machine to two machines gave us something on the order of 4x speed improvement.

私の前の講義を思い出してください　APサーバと

Remember how I talked in the last lecture about separation of services--separating our app server

データベースを分けると[br]処理速度が格段に上がると言いましたね

from our database gave us a tremendous speed improvement because these two

別々に動く2つのソフトを[br]別々のマシンで動かせるからです

pieces of software run totally different --use computers in a totally different way.

これが最初の変更でした

That was the first architecture change we made.

マシンは1～2度アップグレードしました

I think we upgraded this machine once or twice to like a more beefy machine.

それでもまだダウンタイムに悩まされていました

At the time we are still plagued by downtime, whether it was our Lisp or a Python program,

時々わけもなくクラッシュするので[br]私はよく呼び出されました

it would occasionally just crash and we'd have to get notified--more often I'd just get called.

サイトがダウンしては直すの繰り返しだったのです

I would check the site or somebody would call me to tell me the site was down and I'd bring it back up.

これを回避する方法はたくさんあります

There's so many easy ways to avoid this scenario.

当時のストレスと時間の浪費を思うとうんざりします

It makes me cringe when I think about how much time and stress I spent on

動くかどうかはらはらしていました

not knowing whether our website was running.

今はSuperviseというソフトで検証しています

The way we do it now is we use a piece of software called Supervise,

基本的にプログラムを監視し検証するソフトです

which we integrated shortly thereafter. Basically what supervise does is that it watches a program.

プログラムがクラッシュしていれば再始動してくれます

It runs a program, and if that program crashes, it restarts it.

これはすばらしい進歩でした　そして次に

And that's really a nice setup to have, and we actually got to the point where we'd run

1つのマシンで2つのPythonを動かし[br]ロードバランサとしました

two Python programs on one machine and then we had a little mini load balancer

2つのPythonにトラフィックを送り[br]マシンを同等に動かすのです

kind of running on that machine as well that would send traffic to both of these Pythons

どちらかが動かなくなったら[br]Superviseが始動してくれます

and if one of them died, Supervisor bring it back up.

両方同時に故障しなかったのは幸運でした

And so unless the whole machine died--luckily, it never actually happened to us.

データベース用のマシンはまだ1台でした

On the website would stay running. At that time, we still only had one database machine.

マシンが一度も壊れなかったのもとても幸運でした

We were very lucky, and we're very lucky that neither of these machines ever died

次のマシンが手に入るまでサイトが停止するからです

Because if you lost this machine, the website would have been down until we could get a new one,

ただプロバイダが遅いのは痛手でした

and our hosting provider was very slow--it would've been very difficult.

マシンを失ったら中のデータも[br]永久に失っていたでしょう

And if we had lost this one, our database machine, we would've lost the data--like forever.

当時はバックアップが不完全だったので[br]Redditの人気も出て

We weren't doing good backups back then and it was really fortunate that Reddit turned into a

昔のアーカイブがあるのも幸運なことです

でもマシンは壊れることを忘れないでください

as a result of luck that we didn't lose those because you will lose machines.

人生の教訓にしてください

Machines die all the time. This is kind of a fact of life.

24時間高負荷で動かすので[br]ハードディスクが壊れるのです

I mean you're running these machines around the clock, high load, hard disk can fell,

メモリも消えます　高負荷をかけて動かし続けると

memory can fell--there's lots of things that can go wrong

様々な不具合が起きるので十分気をつけましょう

if you use a machine constantly on high load.

Similar videos:

Scaling - Web Development
Udacity
12.5K views 81 likes 1 dislikes 27 May 2012100% 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

More Handlers - Web Development
Udacity
9.1K views 9 likes 2 dislikes 22 Apr 2012100% match

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

Inline Vs Block
Udacity
17.3K views 139 likes 5 dislikes 23 Feb 2015100% match

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

Whitespace
Udacity
47.8K views 26 likes 4 dislikes 23 Feb 2015100% match

Scaling Databases - Web Development
Udacity
64.3K views 795 likes 7 dislikes 25 Apr 2012100% match

Web Applications - Web Development
Udacity
19.5K views 59 likes 4 dislikes 02 Jun 2014100% match

Paragraph Tag - Web Development
Udacity
8.6K views 4 likes 0 dislikes 23 Feb 2015100% match

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

Correct URL - Web Development
Udacity
10.9K views 6 likes 1 dislikes 23 Feb 2015100% match

Adding Images
Udacity
12.9K views 36 likes 0 dislikes 23 Feb 2015100% match

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

User Agent Header - Web Development
Udacity
11.6K views 24 likes 7 dislikes 23 Feb 2015100% match

App Server Architecture - Web Development
Udacity
14K views 52 likes 5 dislikes 27 May 2012100% match

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

Stateless - Web Development
Udacity
9.2K views 35 likes 8 dislikes 23 Feb 2015100% match

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

Rot13 - Web Development
Udacity
9.3K views 46 likes 8 dislikes 23 Apr 2012100% match

World Wide Web Solution - Web Development
Udacity
12.6K views 14 likes 0 dislikes 23 Feb 2015100% match

File Types Solution - Web Development
Udacity
9.9K views 9 likes 0 dislikes 23 Feb 2015100% match

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

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

Memcached - Web Development
Udacity
13.5K views 115 likes 3 dislikes 23 Feb 201573% match

Frameworks - Web Development
Udacity
28.7K views 154 likes 25 dislikes 23 Feb 201573% match

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

Course Outline - Web Development
Udacity
46.2K views 169 likes 0 dislikes 23 Feb 201567% match

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