Couchbase建模技术

Question

我正在为我的团队做一些研究，试图了解couchbase。现在，我正在研究couchbase中的建模实践。

我发现了这篇写于2016年8月的文章，它谈到了couchbase modeling。

它表明，不是只有一个文档

key : hernandez94
{
        "username" : "hernandez94",
        "firstName" : "Jennifer",
        "middleName" : "Maria",
        "lastName" : "Hernandez",
        "addresses" : [
                 { "type" : "home", "addr1" : "1929 Crisanto Ave", "address" : "Apt 123", "addr3" : "c/o  J. Hernandez", "city" : "Mountain View", "state" : "CA", "country" : "USA", "pcode" : "94040" },
                 { "type" : "work", "addr1" : "2700 W El Camino Real", "addr2" : "Suite #123", "city" : "Mountain View", "state" : "CA", "country" : "USA", "pcode" : "94040" }
        ],
        "createdate" : “2016-08-01 15:03:40”,
        "lastlogin": "2016-08-01 17:03:40",
        "pword": "app-hashed-password",
        "loc": "IP or fqdn",
        "enabled" : true,
        "sec-questions" : [
                 { "question1" : "Security question 1 goes here", "answer" : "Answer to security question 1 goes here" },
                 { "question2" : "Security question 2 goes here", "answer" : "Answer to security question 2 goes here" },
                 { "question3" : "Security question 3 goes here", "answer" : "Answer to security question 3 goes here" }
        ],
        "doc-type" : "user"
}

您将其拆分为多个文档: user-doc

key : hernandez94

{
    "firstName" : "Jennifer",
    "middleName" : "Maria",
    "lastName" : "Hernandez",
    "addresses" : [
        { "type" : "home", "addr1" : "1929 Crisanto Ave", "address" : "Apt 123", "addr3" : "c/o J. Hernandez", "city" : "Mountain View", "state" : "CA", "country" : "USA", "pcode" : "94040" },
        { "type" : "work", "addr1" : "2700 W El Camino Real", "addr2" : "Suite #123", "city" : "Mountain View", "state" : "CA", "country" : "USA", "pcode" : "94040" }
    ]
    "createdate" : "2016-08-01 15:03:40",
    "doc-type" : "user"
}

登录-文档

key : login-info::hernandez94

{
        "lastlogin": "2016-08-01 15:03:40",
        "pword": "app-hashed-password",
        "loc": "IP or fqdn",
        "enabled" : true,
        "doc-type" : "login-info",
        "username" : "hernandez94"
}

sec-问题文档

key : sec-questions::hernandez94

{
 "question1" : { "question" : "Security question 1 goes here", "answer" : "Answer to security question 1 goes here" },
    "question2" : { "question" : "Security question 2 goes here", "answer" : "Answer to security question 2 goes here" },
    "question3" : { "question" : "Security question 3 goes here", "answer" : "Answer to security question 3 goes here" },
 "doc-type" : "sec-questions",
 "username" : "hernandez94"
}

由于这是一种较新的技术，做某事的最佳方式更频繁地改变，这种策略仍然可行吗？或者是N1QL在CouchBase5.0上的性能要好得多，这使得这种建模技术过时了？应该将我的所有数据(每个用户)放在一个文档中，还是将其拆分成1000万个x(子文档的数量)？我会有大约1000万的用户。

谢谢

Answer 1

如果不做测量，或者不知道你确切的使用模式，我只能给出一般性的建议。

我建议您考虑如何访问此用户文档。您是经常只获取中心文档，还是通常将其与辅助文档连接并获取所有内容？如果前者占主导地位，请务必将文档拆分为多个部分，并只获取您需要的内容。但如果后者占主导地位，则将所有数据保存在单个文档中，以避免每次需要为用户获取数据时进行多次提取和连接的成本。