How should I implement logs into a document store db?
I am somewhat unsure if I want to use document store(noSQL) for the sake of using it or because it could really help in my situation.
Here is my problem, I have users, I can think about them as documents with no problem (it even seems great like that) - but when I want to add logs that are connected to those users I get somewhat dazzled.
Most of the app creates and updates those user entities. But there is another part, logging (and viewing those logs) the user's actions which is unclear to me, logs are connected to those users for example:
User = {
name: "John",
active: true,
age: 32
}
I don't know if the logs should be in the user document or separated.
My main concern is when I would like to view all of the logs of all of the users ordered by date, that may take a considerable amount of time to query (at least this is how I think) - I would need to to stack the logs by iterating over all of the users and then order them. On the other had, separating the logs seem not true to the "noSQL way of things".
Am I wrong about this? should I even use document store?
nosql logs document-oriented
asked Jul 25 '14 at 7:19
funerrfunerr
1013
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am somewhat unsure if I want to use document store(noSQL) for the sake of using it or because it could really help in my situation.
Here is my problem, I have users, I can think about them as documents with no problem (it even seems great like that) - but when I want to add logs that are connected to those users I get somewhat dazzled.
Most of the app creates and updates those user entities. But there is another part, logging (and viewing those logs) the user's actions which is unclear to me, logs are connected to those users for example:
User = {
name: "John",
active: true,
age: 32
}
I don't know if the logs should be in the user document or separated.
My main concern is when I would like to view all of the logs of all of the users ordered by date, that may take a considerable amount of time to query (at least this is how I think) - I would need to to stack the logs by iterating over all of the users and then order them. On the other had, separating the logs seem not true to the "noSQL way of things".
Am I wrong about this? should I even use document store?
nosql logs document-oriented
asked Jul 25 '14 at 7:19
funerrfunerr
1013
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am somewhat unsure if I want to use document store(noSQL) for the sake of using it or because it could really help in my situation.
Here is my problem, I have users, I can think about them as documents with no problem (it even seems great like that) - but when I want to add logs that are connected to those users I get somewhat dazzled.
Most of the app creates and updates those user entities. But there is another part, logging (and viewing those logs) the user's actions which is unclear to me, logs are connected to those users for example:
User = {
name: "John",
active: true,
age: 32
}
I don't know if the logs should be in the user document or separated.
My main concern is when I would like to view all of the logs of all of the users ordered by date, that may take a considerable amount of time to query (at least this is how I think) - I would need to to stack the logs by iterating over all of the users and then order them. On the other had, separating the logs seem not true to the "noSQL way of things".
Am I wrong about this? should I even use document store?
nosql logs document-oriented
asked Jul 25 '14 at 7:19
funerrfunerr
1013
I am somewhat unsure if I want to use document store(noSQL) for the sake of using it or because it could really help in my situation.
Here is my problem, I have users, I can think about them as documents with no problem (it even seems great like that) - but when I want to add logs that are connected to those users I get somewhat dazzled.
Most of the app creates and updates those user entities. But there is another part, logging (and viewing those logs) the user's actions which is unclear to me, logs are connected to those users for example:
User = {
name: "John",
active: true,
age: 32
}
I don't know if the logs should be in the user document or separated.
My main concern is when I would like to view all of the logs of all of the users ordered by date, that may take a considerable amount of time to query (at least this is how I think) - I would need to to stack the logs by iterating over all of the users and then order them. On the other had, separating the logs seem not true to the "noSQL way of things".
Am I wrong about this? should I even use document store?
nosql logs document-oriented
nosql logs document-oriented
asked Jul 25 '14 at 7:19
funerrfunerr
1013
asked Jul 25 '14 at 7:19
funerrfunerr
1013
asked Jul 25 '14 at 7:19
funerrfunerr
1013
asked Jul 25 '14 at 7:19
funerrfunerr
1013
asked Jul 25 '14 at 7:19
funerrfunerr
1013
1013
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 15 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I would imagine that you would be querying the log collection based on username, so it should be fine to create a single collection for the logs. The reason I wouldn't suggest nesting log documents is that there is a limit on document size.
If you know your query pattern is name and date then it should work out pretty well.
Can I ask what the "noSQL way of things" is?
answered Aug 22 '14 at 17:29
digitalohmdigitalohm
262
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f72362%2fhow-should-i-implement-logs-into-a-document-store-db%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I would imagine that you would be querying the log collection based on username, so it should be fine to create a single collection for the logs. The reason I wouldn't suggest nesting log documents is that there is a limit on document size.
If you know your query pattern is name and date then it should work out pretty well.
Can I ask what the "noSQL way of things" is?
answered Aug 22 '14 at 17:29
digitalohmdigitalohm
262
add a comment |
I would imagine that you would be querying the log collection based on username, so it should be fine to create a single collection for the logs. The reason I wouldn't suggest nesting log documents is that there is a limit on document size.
If you know your query pattern is name and date then it should work out pretty well.
Can I ask what the "noSQL way of things" is?
answered Aug 22 '14 at 17:29
digitalohmdigitalohm
262
add a comment |
I would imagine that you would be querying the log collection based on username, so it should be fine to create a single collection for the logs. The reason I wouldn't suggest nesting log documents is that there is a limit on document size.
If you know your query pattern is name and date then it should work out pretty well.
Can I ask what the "noSQL way of things" is?
answered Aug 22 '14 at 17:29
digitalohmdigitalohm
262
I would imagine that you would be querying the log collection based on username, so it should be fine to create a single collection for the logs. The reason I wouldn't suggest nesting log documents is that there is a limit on document size.
If you know your query pattern is name and date then it should work out pretty well.
Can I ask what the "noSQL way of things" is?
answered Aug 22 '14 at 17:29
digitalohmdigitalohm
262
answered Aug 22 '14 at 17:29
digitalohmdigitalohm
262
answered Aug 22 '14 at 17:29
digitalohmdigitalohm
262
answered Aug 22 '14 at 17:29
digitalohmdigitalohm
262
262
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f72362%2fhow-should-i-implement-logs-into-a-document-store-db%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
