| | 3 | == Hadoop == |
| | 4 | |
| | 5 | * [http://www.cloudera.com/blog/2009/09/28/grouping-related-trends-with-hadoop-and-hive/ Grouping Related Trends with Hadoop and Hive] |
| | 6 | * 我覺得這篇是個很好的應用實例，拿 Wikipedia 的流量當輸入，總共有 320 GB。由於是 public 的資料，因此不會有所有權問題。 |
| | 7 | * [http://developer.amazonwebservices.com/connect/entry.jspa?externalID=2596 Wikipedia Page Traffic Statistics] - 範例資料 |
| | 8 | * [http://download.wikimedia.org/enwiki/ Wikipedia Database backup dumps] - 另一個資料來源 |
| | 9 | * [http://www.datawrangling.com/wikipedia-page-traffic-statistics-dataset Wikipedia Page Traffic Statistics Dataset] |
| | 10 | * [http://code.google.com/intl/zh-TW/edu/submissions/uwashington-scalable-systems/ University of Washington: Scalable Systems: Design, Implementation and Use of Large Scale Clusters] |
| | 11 | * [http://dumbotics.com/2009/03/15/computing-tf-idf-weights/ Computing TF-IDF weights] |
| | 12 | |
| | 14 | |
| | 15 | * [http://www.csoonline.com/article/print/503778 5 Mistakes a Security Vendor Made in the Cloud] |
| | 16 | * 第一個錯誤：未告知使用者系統升級 - 連 Google 都犯過這種錯!! |
| | 17 | {{{ |
| | 18 | MISTAKE 1: Updating the SaaS product without telling customers or letting them opt out |
| | 19 | }}} |
| | 20 | * 第二個錯誤：無法回歸到前一個版本 - 一體兩面，採用雲端服務代表妳永遠可以用最新版，但或許使用者應該也有權利選擇穩定的舊版。這個問題不也在微軟身上發生過。 |
| | 21 | {{{ |
| | 22 | MISTAKE 2: Not offering a rollback to the last prior version |
| | 23 | }}} |
| | 24 | * 第三個錯誤：無法讓使用者選擇升級的時間點 - 嗯，Google 不會通知妳今天 gmail 要改版程式，確實有風險啦～ |
| | 25 | {{{ |
| | 26 | MISTAKE 3: Not offering customers a choice to select timing of an upgrade |
| | 27 | }}} |
| | 28 | * 第四個錯誤：無視前一版的設定將造成客戶使用上的不穩定 |
| | 29 | {{{ |
| | 30 | MISTAKE 4: New versions ignore prior configurations or settings, which creates instability in the customer environment |
| | 31 | }}} |
| | 32 | * 第五個錯誤：未能提供系統安全指標 - 就有點類似網路骨幹會要求 99.99% 的持續穩定運作率 |
| | 33 | {{{ |
| | 34 | MISTAKE 5: Not offering a safety valve |
| | 35 | }}} |
