SQL to MongoDB
db.runCommand({ mapreduce: "DenormAggCollection", query: { filter1: { '$in': [ 'A', 'B' ] }, filter2: 'C', filter3: { '$gt': 123 } }, map: function() { emit( { d1: this.Dim1, d2: this.Dim2 }, { msum: this.measure1, recs: 1, mmin: this.measure1, mmax: this.measure2 < 100 ? this.measure2 : 0 } );}, reduce: function(key, vals) { var ret = { msum: 0, recs: 0, mmin: 0, mmax: 0 }; for(var i = 0; i < val
SQL脳ã«å„ªã—ã„MongoDBクエリー入門 - taka512's blog
mongoコマンドã‹ã‚‰æŽ¥ç¶šã—ãŸéš›ã«ã‚ªãƒ¼ãƒ«ãƒ‰ã‚¿ã‚¤ãƒ—(SQL脳)ãŸã‚‹æˆ‘々人類ã«ã‚‚ 調ã¹ã‚„ã™ã„å½¢ã§insertã€selectã€updateã‚’è¡Œã†æ–¹æ³•ã‚’調ã¹ã¾ã—ãŸã€‚ 定義å‚ç…§ // use [データベースå] use [データベースå] // show databases show dbs // show tables show collectionså‚照系 // select * from [コレクションå] db.[コレクションå].find() // select * from [コレクションå] where x=4 db.[コレクションå].find({x:4}) // select j from [コレクションå] where x=4 db.[コレクションå].find({x:4}, {j:1}) // select * from [コレクションå] limit 1 db.[コレクション
Data consistency with asynchronous queues and MongoDB
One of the challenges you face when using asynchronous work queues to modify the state of a document in MongoDB is keeping the data consistent when work units are applied out of order. Â Here is a simple, but somewhat contrived example of the problem. Â Lets say you have a web application that lets students enroll and unenroll from classes. Â Rather than making the user wait for the synchronous actio
Sharding を使ã„ã“ãªã™ãŸã‚ã®5ã¤ã®Tips - doryokujin's blog
@doryokujinã§ã™ã€‚今日も相変ã‚らãšMongoDBã®ã€ãã—ã¦Shardingã«é–¢ã™ã‚‹è¨˜äº‹ã‚’書ã“ã†ã¨æ€ã„ã¾ã™ã€‚ …ã¨ã€ãã®å‰ã«ãŠçŸ¥ã‚‰ã›ã§ã™ï¼6月ã¯2ã¤ã®MongoDB勉強会を予定ã—ã¦ãŠã‚Šã¾ã™ã€æ˜¯éžã”å‚åŠ ä¸‹ã•ã„ï¼ ãƒ»2011å¹´6月11日（土） 「第4回 MongoDB 勉強会 in Tokyoã€@フューãƒãƒ£ãƒ¼ã‚¢ãƒ¼ã‚テクト ・2011å¹´6月28日（ç«ï¼‰ã€Œç¬¬1回 MongoDB ソースコードリーディングã€@PFI ã•ã¦ã€ãã‚Œã§ã¯æœ¬é¡Œã«å…¥ã‚ŠãŸã„ã¨æ€ã„ã¾ã™ã€‚ MongoDBã®Shardingã¨ã„ãˆã°ã€ ・åˆæœŸè¨å®šã‚„Shardã®è¿½åŠ ・削除ã¨ã„ã£ãŸå°Žå…¥ã®å®¹æ˜“㕠・Shardã®é¢å€’ã‚’Mongoå´ãŒãšã£ã¨è¦‹ã¦ãれるã¨ã„ã†ç®¡ç†ã®å®¹æ˜“ã• ã‚’å‚™ãˆã¦ã„ã‚‹ã¨è¨€ã†ã“ã¨ã§èˆˆå‘³ã‚’æŒã£ã¦ãŠã‚‰ã‚Œã‚‹æ–¹ã‚‚多数ã„ã‚‹ã¨æ€ã„ã¾ã™ã€‚ ã—ã‹ã—ãã®ä¸€æ–¹ã§å®Ÿéš›ã«Sharding環境を導入ã—ã¦ã„る方々ã®ä¸ã®å¤šãã¯ã€éé‡ã™ã‚‹æ§˜ã€…ãªä¸éƒ½åˆã‚„ä¸æ•´
20110514 mongo dbãƒãƒ¥ãƒ¼ãƒ‹ãƒ³ã‚°
The document provides tips and explanations for various MongoDB commands and operations including explain, hint, setProfilingLevel, currentOp, and mongostat. It discusses using indexes to optimize queries, setting profiling levels to log slow queries, using currentOp to view currently running operations, and using mongostat to view MongoDB server statistics.Read less
『ドã‚ュメント指å‘データベース「MongoDBã€ã€
皆様ã€ã¯ã˜ã‚ã¾ã—ã¦ã€‚ アメーãƒäº‹æ¥æœ¬éƒ¨ã¨è¨€ã†ã¨ã“ã‚ã§ã‚µãƒ¼ãƒ“ス開発ã®ãƒ—ãƒã‚°ãƒ©ãƒžã‚’ã—ã¦ã„る津田ã¨ç”³ã—ã¾ã™ã€‚ 先日ã€M.S.æ°ã‚ˆã‚Šã€å½“エンジニアブãƒã‚°ã«ã¦ã€ŒæŠ€è¡“ã«é–¢ã—ã¦æ›¸ãよã†ã«ã€ã¨ãŠé”ã—ãŒä¸‹ã‚Šã¾ã—ãŸã€‚ åŒã˜æŠ€è¡“者ã¨ã—ã¦ã€å°Šæ•¬ã®æ°—æŒã¡ã‚’通り越ã—ã€ç•æ€–ã®å¿µã™ã‚‰æŠ±ã„ã¦ã„ã‚‹M.S.æ°ã« 「技術ã€ã«é–¢ã—ã¦æ›¸ã‘ã¨è¨€ã‚れるã¨ã¯ã€ã‚‚ã¯ã‚„è·¯é ã«è¿·ã£ãŸå羊ã®æ°—分ã§ã™ã€‚ ã©ã†ã«ã‹é•ã†è©±é¡Œã«å‡ºæ¥ãªã„ã‹ã¨ã”ã¾ã‹ã—ã¦ã¯ã¿ãŸã‚‚ã®ã®ã€ ã‚„ã¯ã‚Šã€ŒæŠ€è¡“ã€ã«é–¢ã—ã¦æ›¸ãよã†ã«ã¨å¿µã‚’押ã•ã‚Œã¦ã—ã¾ã„ã¾ã—ãŸã€‚ è·¯é ã«è¿·ã£ã¦ã„ã¦ã‚‚致ã—æ–¹ãªã„ã®ã§ã€ä»Šå¾Œã‚µãƒ¼ãƒ“スã«åˆ©ç”¨ã™ã‚‹äºˆå®šã§æ¤œè¨¼ã‚’è¡Œã£ã¦ã„㟠「MongoDBã€ã¨è¨€ã†ãƒ‰ã‚ュメント指å‘データベースã«é–¢ã—ã¦ç´¹ä»‹ã•ã›ã¦é ‚ãã¾ã™ã€‚ â– MongoDBã¨ã¯ ã“ã“数年注目を浴ã³ã¦ã„る「NOSQL（NotOnlySQL）ã€ã®ãƒ‡ãƒ¼ã‚¿ã‚¹ãƒˆã‚¢ã®ä¸€ã¤ KVSã¨ã¯ç•°ãªã‚Šã€ã‚¹ã‚ーマレスã§ã¯ã‚ã‚‹ãŒã€ã‚«ãƒ©ãƒ ã«è¿‘ã„概念ãŒã‚ã‚‹
Replica Sets
This document provides an overview of MongoDB replica sets. It discusses the key concepts including primary nodes, secondary nodes, elections, write acknowledgments, failovers, topologies, configuration, and commands. Replica sets improve availability, durability, and performance compared to single node deployments. A replica set consists of multiple MongoDB instances that maintain the same data s
snailinaturtleneck.com - snailinaturtleneck リソースãŠã‚ˆã³æƒ…å ±
This webpage was generated by the domain owner using Sedo Domain Parking. Disclaimer: Sedo maintains no relationship with third party advertisers. Reference to any specific service or trade mark is not controlled by Sedo nor does it constitute or imply its association, endorsement or recommendation.
CouchDBã¨MongoDBを比較ã—ã¦ã¿ãŸ - Masatomo Nakano Blog
ドã‚ュメント指å‘ãªKVSã£ã¦ã“ã¨ã¨ã€å—é¢ãŒä¼¼ã¦ã„ã‚‹ã¨è¨€ã†ã“ã¨ãらã„ã—ã‹æ¯”較ã™ã‚‹æ„味ãŒãªã•ãã†ãªCouchDBã¨MongoDBã ã‘ã©ã€ã“ã“2，3ヶ月ã§ä¸¡æ–¹ã‚’ãã‚Œãªã‚Šã«çªã£è¾¼ã‚“ã§è¦‹ã¦ããŸã®ã§æ¯”較ã—ã¦ã¿ãŸã€‚実装é¢ã‚„パフォーマンスã€ã¨ã„ã†ã“ã¨ã‚ˆã‚Šã¯ã©ã¡ã‚‰ã‹ã¨ã„ã†ã¨(ç§ãŒæ„Ÿã˜ã‚‹)æ€æƒ³çš„ãªã‚‚ã®ã‚„ã€ãƒ¦ãƒ¼ã‚¶å´ã‹ã‚‰ã®è¦–点ã§ã®æ¯”較。 共通ã™ã‚‹ã¨ã“ã‚ ã“ã‚Œã¯ã‚‚ã†ç°¡å˜ã«ã€ ドã‚ュメント指å‘データベース - RDBMSã®ã‚ˆã†ãªã‚«ãƒ©ãƒ ã¨è¨€ã£ãŸã‚‚ã®ã‚’æŒãŸãšã«ã‚¹ã‚ーマレスã§å¥½ããªæƒ…å ±ã‚’å…¥ã‚Œã‚‰ã‚Œã‚‹ Javascript/JSONを使用 - データ自体もJSONã¨ã„ã†Javascriptç”±æ¥ã®ãƒ•ã‚©ãƒ¼ãƒžãƒƒãƒˆã§æŒã¡(MongoDBã¯JSONã‚’å…ƒã«ã—ãŸBSONã¨ã„ã†ã‚‚ã®ã ãŒ)ã€ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã®ã‚¢ã‚¯ã‚»ã‚¹ã«ã¯Javascriptを使用ã™ã‚‹ スケールアウトã™ã‚‹ã‚ˆã†ã«è€ƒãˆã‚‰ã‚Œã¦ã„ã‚‹ NoSQLãªæµè¡Œ CouchDBã®ç‰¹å¾´ 機能をé™å®šã—ã¦ã„ã‚‹
MongoDBã®ãƒ©ã‚¤ã‚»ãƒ³ã‚¹ã«ã¤ã„㦠- Masatomo Nakano Blog
Twitterã§å°‘ã—話題ã«ãªã£ã¦ã„ãŸã®ã§ã€MongoDBã®ãƒ©ã‚¤ã‚»ãƒ³ã‚¹ã«ã¤ã„ã¦æ›¸ã„ã¦ã¿ã‚‹ã€‚ 「MongoDBを使ã†å ´åˆã€è‡ªåˆ†ã§æ›¸ã„ãŸã‚¢ãƒ—リケーションå´ã®ã‚½ãƒ¼ã‚¹ã‚‚全部公開ã—ãªã„ã¨ã„ã‘ãªã„ã€çš„ãªå˜˜ãŒåºƒãŒã‚‹ã®ã¯ã¡ã‚‡ã£ã¨å«Œãªã®ã§ã€‚ http://www.mongodb.org/display/DOCS/Licensing ã¨ã‹ã€Â http://blog.mongodb.org/post/103832439/the-agpl をèªã‚“ã§ã¿ã¦ã‚‚らãˆã°ã ã„ãŸã„ã‚ã‹ã‚‹ã¨æ€ã†ã®ã ã‘ã©ã€MongoDB自体ã¯ã€ç¢ºã‹ã«AGPLãªã®ã§ã€æ”¹å¤‰ã—ãŸå ´åˆã€(一般ã«å…¬é–‹ã™ã‚‹)サーãƒç”¨é€”ã®åˆ©ç”¨ã§MongoDB自体ã®ã‚½ãƒ¼ã‚¹ã®å…¬é–‹ã®ç¾©å‹™ã¯ã‚る。ãŸã ã€ã“ã‚Œã¯MongoDB本体ã®è©±ã§ã€è‡ªåˆ†ã§ä½œã£ãŸã‚¢ãƒ—リケーションã«ã¯é©ç”¨ã•ã‚Œãªã„。ã¾ãŸã€ãƒ‰ãƒ©ã‚¤ãƒãƒ¼é–¢é€£ã¯Apache licenseãªã®ã§ã€ãƒ‰ãƒ©ã‚¤ãƒãƒ¼ã‚’組ã¿è¾¼ã‚€ã‚ˆã†ãªè‡ªåˆ†ã®ã‚¢ãƒ—リケーションを
1
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Don't use MongoDB
事例：ã¨ã‚る写真共有アプリã§ã®MongoDB
MongoDBを用ã„ãŸã‚½ãƒ¼ã‚·ãƒ£ãƒ«ã‚¢ãƒ—リã®ãƒã‚°è§£æž 〜解æžåŸºç›¤æ§‹ç¯‰ã‹ã‚‰ãƒ•ãƒãƒ³ãƒˆUIã¾ã§ã€MongoDBを最大é™ã«æ´»ç”¨ã™ã‚‹ã€œ
MySQL versus MongoDB - yet another silly benchmark
Mongo DB is web scale
The MongoDB NoSQL Database Blog - On Distributed Consistency - Part 5 - Many Writer Eventual Consistency
Blog Archives
{{#tags}}- {{label}}
{{/tags}}