Design considerations on JSON schema for scalars with a consistent attachment property
Want to improve this post? Provide detailed answers to this question, including citations and an explanation of why your answer is correct. Answers without enough detail may be edited or deleted. I’m trying to create a JSON schema for the results of doing statistical analysis based on disparate pieces of data. The current schema I […]
Would this data requirement suit a Document -Oriented database?
I have a requirement to allow users to fill in journal/diary entries per day.
I want to provide a handful of known journal templates with x columns to fill in. An example might be a thought diary; a user has to record a thought in one column, describe the situation, rate how they felt etc.
What is the recommended MongoDB schema for this quiz-engine scenario?
I’m working on a quiz engine for learning a foreign language. The engine shows users four images simultaneously and then plays an audio file. The user has to match the audio to the correct image. Below is my MongoDB document structure. Each document consists of an image file reference and an array of references to audio files that match that image. To generate a quiz instance I select four documents at random, show the images and then play one audio file from the four documents at random.
NoSQL Document Database as a Message Queue
I am considering using a NoSQL Document database as a messaging queue.
Would a model like this translate well to a document or graph database?
I’m trying to understand what types of models that I have traditionally persisted relationally would translate well to some kind of NoSQL database. Suppose I have a model with the following relationships:
Would a model like this translate well to a document or graph database?
I’m trying to understand what types of models that I have traditionally persisted relationally would translate well to some kind of NoSQL database. Suppose I have a model with the following relationships:
Would a model like this translate well to a document or graph database?
I’m trying to understand what types of models that I have traditionally persisted relationally would translate well to some kind of NoSQL database. Suppose I have a model with the following relationships:
Would a model like this translate well to a document or graph database?
I’m trying to understand what types of models that I have traditionally persisted relationally would translate well to some kind of NoSQL database. Suppose I have a model with the following relationships:
Generating documents from a graph data structure where each document represents a Node in the Graph
TLDR
Is there an accepted design pattern for storing a few global variables in a NoSQL database?
I’m wanting to create an admin dashboard for my app, and to show new events there. In order to know which events are new, I’ll need to store at least one extra datapoint to the server: the last date at which the admin user (me) looked at the events and marked them all as read.