GitHub - twitter-archive/gizzard: [Archived] A flexible sharding framework for creating eventually-consistent distributed datastoresYou signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
![GitHub - twitter-archive/gizzard: [Archived] A flexible sharding framework for creating eventually-consistent distributed datastores](https://cdn-ak-scissors.b.st-hatena.com/image/square/4f3f245db0e22fb536339111ee35e08ac7e990e3/height=288;version=1;width=512/https%3A%2F%2Fopengraph.githubassets.com%2Faffe9254a3f18ef9f8f603e789b6de2c81710c10e9f2a0971877c974209fcbf6%2Ftwitter-archive%2Fgizzard)
Kazuho@Cybozu Labs: パフォーマンスとスケーラビリティのためのデータベースアーキテクチャ (BPStudy#25発表資料)
先週金曜日、BPStudy#25で、「パフォーマンスとスケーラビリティのためのデータベースアーキテクチャ」という題目で話をさせていただきました。その際に使用した発表資料は以下のとおりです。 1. Happy Optimization 最初に、最適化の考え方として、上限値を予測し、それを元にリソース配分を考える、という手法を説明しました。
Dealing with multi-partition transactions in a distributed KV solution - High Scalability -
I've been getting asked about this a lot lately so I figured I'd just blog about it. Products like WebSphere eXtreme Scale work by taking a dataset, partitioning it using a key and then assigning those partitions to a number of JVMs. Each partition usually has a primary and a replica. These 'shards' are assigned to JVMs. A transactional application typically interacts with the data on a single par
Introducing DataFabric
FiveRuns Blog On Rails production performance and monitoring Posts No comments Open Source Rails One of the lingering issues we’ve had to deal with over the last year in the Manage service is ActiveRecord’s reluctance to talk to more than one database. It’s really quite stubborn in that regard and while there are a few solutions out there, none of them worked quite like we wanted. Some required in
Acts As Partitioned
Acts As Partitioned ================= Allows ActiveRecord models to connect to different databases on-the-fly. Horizontal Partitioning is when you remove rows from one table and put them in a separate table (usually on a separate database, usually on a separate machine.) For example, say you have a users table with one million rows and it is getting too large. You can cap it at one million and sa
How FriendFeed uses MySQL to store schema-less data - Bret Taylor's blog
Background We use MySQL for storing all of the data in FriendFeed. Our database has grown a lot as our user base has grown. We now store over 250 million entries and a bunch of other data, from comments and "likes" to friend lists. As our database has grown, we have tried to iteratively deal with the scaling issues that come with rapid growth. We did the typical things, like using read slaves and
はてなグループの終了日を2020年1月31日(金)に決定しました - はてなの告知
はてなグループの終了日を2020年1月31日(金)に決定しました 以下のエントリの通り、今年末を目処にはてなグループを終了予定である旨をお知らせしておりました。 2019年末を目処に、はてなグループの提供を終了する予定です - はてなグループ日記 このたび、正式に終了日を決定いたしましたので、以下の通りご確認ください。 終了日: 2020年1月31日(金) エクスポート希望申請期限:2020年1月31日(金) 終了日以降は、はてなグループの閲覧および投稿は行えません。日記のエクスポートが必要な方は以下の記事にしたがって手続きをしてください。 はてなグループに投稿された日記データのエクスポートについて - はてなグループ日記 ご利用のみなさまにはご迷惑をおかけいたしますが、どうぞよろしくお願いいたします。 2020-06-25 追記 はてなグループ日記のエクスポートデータは2020年2月28
BlueBlog: How and Why Glue is Using Amazon SimpleDB instead of a Relational Database
AdaptiveBlue makes products that leverage personalization and semantics to create a better online experience.Amazon SimpleDB is a new service, part of the Amazon Web Services family, which offers a scalable, cloud-based database solution. In this post we will discuss how we are using SimpleDB instead of a traditional relational database to power Glue, our popular browser add-on. Connecting People
Sharding the Hibernate Way - High Scalability -
Update: A very nice JavaWorld podcast interview with Google engineer Max Ross on Hibernate Shards. Max defines Hibernate Shards (horizontal partitioning), how it works (pretty well), virtual shards (don't ask), what they need to do in the future (query, replication, operational tools), and how it relates to Google AppEngine (not much). To scale you are supposed to partition your data. Sounds good,
An Unorthodox Approach to Database Design : The Coming of the Shard - High Scalability -
Update 4: Why you don’t want to shard. by Morgon on the MySQL Performance Blog. Optimize everything else first, and then if performance still isn’t good enough, it’s time to take a very bitter medicine. Update 3: Building Scalable Databases: Pros and Cons of Various Database Sharding Schemes by Dare Obasanjo. Excellent discussion of why and when you would choose a sharding architecture, how to sha
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
http://svn.trac.washington.edu/svn/plugins/table_partitions/README
Database Sharding At Netlog
jurriaanpersyn.com
Scaling in Games & Virtual Worlds - ACM Queue
http://blog.maxindelicato.com/2009/01/alternative-memcache-usage-a-highly-scalable-highly-available-inmemory-shard-index.html
http://blog.maxindelicato.com/2008/12/scalability-strategies-primer-database-sharding.html