- "データの多くのTB (もしくは PB)" doesn’t make sense.
- "ワークロード" is used for the translation of "workload" rather than
"負荷" in this context.
- "集中的、大規模なデータ負荷" doesn't make sense.
- Usually "リレーション" is used for the translation of "relationship"
rather than "関係性" in this context.
- "a social network" doesn’t mean "SNS" in this context.
- "サービス" ("service") is unnecessary.
- "特性" is commonly used for the translation of "properties" rather than
"プロパティ" in this context.
- Make the translation more fluent ("しばしば" is too literal).
- "different" means "複数の" rather than "異なる" in this context.
- "distribute" means "分散" rather than "分割" (split).
- "断片" (fragment) is mistranslation for "shards".
- Make the translation more fluent.
- "Once" (いったん) is missing in the translation.
- "コミット" is commonly used for the translation of "commit" rather
than "処理" (process).
- "そのように保存される" doesn’t make sense in this context.
- Usually "並行に" is used for the translation of "concurrently" rather
than "同時に" (simultaneously).
- "serially" means "順に" in Japanese. "連続的" isn’t used in this kind
of context.
- “特性” is commonly used for the translation of “(ACID) property” rather
than “プロパティ”.
- “set of properties” couldn’t be literally translated in this situation
(“プロパティの集合” doesn’t make sense), so substitute with “4つの特性” (four
properties).
* JA: Fix mistranslation in Horizontal scaling section
- The Japanese translation is ambiguous about “vertical scaling” means scaling out or scaling up.
- The word “expensive” is missing in the Japanese translation.
* ja: Fix mistranslation in "Horizontal scaling"
- The Japanese translation is ambiguous about “vertical scaling” means scaling out or scaling up.
- The word “expensive” is missing in the Japanese translation.
- "best effort" should be literally "ベストエフォート" in Japanese.
- "メムキャッシュ" is overtranslation. Remain in English: "memecached".
- The modification structure of last sentence in Japanese is ambiguous.
SATO Yusuke