![https://eng.uber.com/m-uber/](https://cdn-ak-scissors.b.st-hatena.com/image/square/688bf92376fb945cef0ed5790820220e5fdec4f2/height=288;version=1;width=512/https%3A%2F%2Feng.uber.com%2Fwp-content%2Fuploads%2F2017%2F06%2Fimage2-1.jpg)
While all three systems are able to scale linearly by adding new nodes online, only a couple systems can also receive writes during failover. None of the solutions have a built-in way of notifying downstream dependencies of changes, so we would need to implement that at the application level. They all have indexes, but if you’re going to index many different values, the queries become slow, as the
You’re seeing information for Japan . To see local features and services for another location, select a different city. Show more Like many startups, Uber began its journey with a monolithic architecture, built for a single offering in a single city. At the time, all of Uber was our UberBLACK option and our “world” was San Francisco. Having one codebase seemed “clean” at the time, and solved our c
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く