Infinite scalability, lowest latency, lowest costsCount on the real-time database that’s always on – globally. Grow from gigabytes to petabytes without tradeoffsPredictable and consistent performance, for any amount of data. How we make it happen
![Aerospike | Aerospike](https://cdn-ak-scissors.b.st-hatena.com/image/square/5649d6b5106f4cf967ea4983941dbaa115f7351a/height=288;version=1;width=512/https%3A%2F%2Fimages.ctfassets.net%2Fdrk57q8lctrm%2F7Lu0enPkmC1UBPCAdNiAzl%2F4a4e59826fdb8ad861c52dd669b73a57%2Fdefault_feature_image_1.webp%3Fw%3D1200%26h%3D630%26fit%3Dcrop%26f%3Dleft)
An article by Sarah Mei titled "Why you should never use MongoDB" discusses the issues you’ll run into if you try to use a NoSQL database when a relational database would be far superior. An example of this is when data that was thought to be in a silo needs to cross boundaries (what relational DBs are great at). Another example is when you store a user’s name in various places for easy access, bu
A talk at Code Mesh, London, UK, 04 Nov 2015 Slides Video This was a repeat of my talk at Strange Loop 2015. Abstract Back in the 1970s, the earliest databases had transactions. Then NoSQL abolished them. And now, perhaps, they are making a comeback… but reinvented. The purpose of transactions is to make application code simpler, by reducing the amount of failure handling you need to do yourself.
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く