javascript - Meteor.js - Should you denormalize data? -


This question is driving me crazy and I can not take my head around it. I came from a MySQL relational background and am using Meteorjs and Mongo. Take the example of posts and writers for the purposes of this question. An author for many articles has come in two ways to do this:

  1. There is a collection of posts - each post contains the author's information written in the document. Of course this denormalization and issues such as if the name of the author changes, how do you keep the data right.

  2. There are two collections: posts and authors - each post has an author, the id that references the author's collection, then I try to "connect" to a non-relational database, while the response I am trying to maintain

    3. I think the degree of MongoDB denormalization is acceptable and I take the exam applying embed as to actually run against the ideals of Mongo Feels.

    Can any light shed any specific thing, especially what is the right approach to properly appraise my app data and to be manageable? / P>

    thanks

Denormalization is useful when you are scaling your application and You see that taking some time to complete certain questions I have also found that most mozed developers forget about data normalization, but this is another topic.

Some developers say that: "Do not use inspection and inspection because it is slow". We are building real-time applications so that one thing is normal, this is a CPU intensive app design.

In my opinion, you should always design a generalized design, and then you have to decide, try and test which fields, which can be repeated / denormalised, improve your app's performance. Are there. Example: You remove 1 query per user. UI requires an additional area and it is repeated, etc.

With denormalisation you have an additional cost to pay, you have to update denormalized fields according to the main collection. Example: Suppose you are in a collection of authors and articles. On each article you have the author's name. With the usual scenario, the author can change his name, it works fine, with a denormalised scenario, you have to update the author's document name and each article owned by this author, with the new name.

Having a generalized design lets you make life easier but denormalisation, eventually, becomes necessary

From a MeteorJs perspective: With a generalized scenario, Are sending. With the distorted scenario, you send only 1 collection. You can join responsibly on the server and send 1 archive to the customer, although it increases the usage of the RAM due to the server.

Denormalisation is something that is very clear for the requirements of your application. You can use the database to find ways to make your application faster. Design is the only factor 1, which you can demonstrate Play with performance while performing.


Comments

Post a Comment

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

I'm having trouble overriding a ModelForm save method. I get this error I'm: Exception type: TypeErier Exception Value: Save () found an unexpected keyword argument 'committed' My intentions include a form 3 fields Submit several values ​​for, then create an object for each combination of those areas, and to save each object file models.py class collarsult type (models.Model): id = model. AutoField (db_column = 'icontact_result_code_type_id', primary_key = true) callResult = models.ForeignKey ( 'CallResult', db_column = 'icontact_result_code_id') campaign = models.ForeignKey ( 'campaign', db_column = 'icampaign_id') CALLTYPE = models.ForeignKey ( 'CALLTYPE', db_column = 'icall_type_id') agent = models.BooleanField (db_column = 'bagent', default = true) teamLeader = models.BooleanField (db_column = 'bTeamLeader', default = true) active = models.BooleanField (db_column = Django.form...
Read more

html - CSS autoheight, but fit content to height of div -

I have a div in which there are three children- div in the left and middle div: float: left while true: float: true because it is my layout Actually will spoil, I've used ClearFix Hack: .cf {zoom: 1; }. Cf: First,. Cf: {content: ""; Display: Table; }. Cf: After {clear: both; } It still works, but I want to be the right div an indicator. So it should fill 100% of the parent unit of height. How can I complete this? PS is the full code: & Lt; / Div & gt; & Lt; Div class = "mobile_content" & gt; & Lt; H5 & gt; {{Data.titel}} & lt; / H5> & Lt; Table & gt; & Lt; TR & gt; & Lt; Th & gt; Komponist: & lt; / Th & gt; & Lt; TD & gt; {{Data.komponist}} & lt; / TD & gt; & Lt; / TR & gt; & Lt; TR & gt; & Lt; Th & gt; Instrument: & lt; / Th & gt; & Lt; TD & gt; {{Data.instrumente}} & lt; / TD & gt; & Lt; / TR & gt;...
Read more

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -

I have been trying to use Qt5 multimedia to record audio with QAudioInput, however, when I see If QAudioInput is started, it increases the master volume of my sound device to 100%. How can I prevent QAudioInput from changing the master volume? My current development platform is Linux with PalsAdio (with flat audio disabled). How can I use QAudioInput : QAudioDeviceInfo device_info = QAudioDeviceInfo :: defaultInputDevice (); QAudio format format; Format.setSampleRate (44100); Format.setChannelCount (1); Format.setSampleSize (16); Format.setCodec ("Audio / PCM"); Format.setSampleType (QAudioFormat :: SignedInt); Format.setByteOrder (QAudioFormat :: LittleEndian); Std :: cout & lt; & Lt; Device_info.deviceName (). ToUtf8 (). ConstData () & lt; & Lt; Std :: endl; QAudioInput * default_device = new QAudioInput (device_info, format); QIODevice * default_io_device = default_device-> Start (); a QAudioInput.setVolume () method is not you I ...
Read more