Ggtcf

Why do Radio Buttons not fill the entire outer circle?

Should a narrator ever describe things based on a character's view instead of facts?

Why is indicated airspeed rather than ground speed used during the takeoff roll?

How to track Account Description field changes in Field history Tracking?

What properties make a magic weapon befit a Rogue more than a DEX-based Fighter?

How do you say "Trust your struggle." in French?

Started in 1987 vs. Starting in 1987

How to get directions in deep space?

Why is participating in the European Parliamentary elections used as a threat?

Extract substring according to regexp with sed or grep

How to preserve electronics (computers, ipads, phones) for hundreds of years?

Would this string work as string?

Output visual diagram of picture

What is this high flying aircraft over Pennsylvania?

Walter Rudin's mathematical analysis: theorem 2.43. Why proof can't work under the perfect set is uncountable.

Asserting that Atheism and Theism are both faith based positions

Has the laser at Magurele, Romania reached a tenth of the Sun's power?

Did I make a mistake by ccing email to boss to others?

Weird lines in Microsoft Word

Reasons for having MCU pin-states default to pull-up/down out of reset

Would a primitive species be able to learn English from reading books alone?

Can you take a "free object interaction" while incapacitated?

Unfrosted light bulb

Can a Knock spell open the door to Mordenkainen's Magnificent Mansion?

couchbase document size limit, is storing generic data preferable

How do I keep existing data in couchbase and only update the new data without overwritingOvercoming querying limitations in CouchbaseDesigning record keys for document-oriented database - best practicesBulk inserting documents into couchbase database with php - how to?Denormalizing and querying a giant Couchbase data setLoading only a subset of my data when querying Couchbase?Purging documents in Couchbase LiteCouchbase Lite: reading document vs querying dataLoading Data onto CouchbaseGeneric Entity in Spring Data for Couchbase Documents

0

Say I have a couchbase document that is sized 12 MB (Actual size, not size on disk). Couchbase literature says there is a sizing limitation of 20 MB on documents' actual size.
If I were to have a significant part as generic data on this document (6 MB out of 12 MB). Suggest me which is a better approach from below.

• Drop the generic data altogether from the document and build it myself after database operation and append it to the response object that gets sent to UI layer. Again drop any generic data received from UI while upserting back to database.


• Let the current document structure stay as is. Fetch and Upsert back the entire 12 MB data each time.

If I were to adopt the first approach, I will have to create a service that builds 6 MB data by iterating with a sychronous change. I will have to call this service everytime during the database operation for this document. Is this going to be an overhead, or, will it reduce the time for the whole operation compared to fetching a 12 MB document?

javascript node.js nosql couchbase dao

share|improve this question

asked Mar 7 at 20:20

mr.Gmr.G

23

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Is the "generic data" different for every document, or the same for all?
  
  – Johan Larson
  Mar 7 at 20:56
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Attributes are same, and values can be generated by repeated iteration with a synchronous change starting from some data that is always available in the document. But when I am saying generic, I am saying that this information can be constructed from the actual impacting data stored to database.
  
  – mr.G
  Mar 8 at 17:23
  

  
  
  
  

add a comment | 

0

Say I have a couchbase document that is sized 12 MB (Actual size, not size on disk). Couchbase literature says there is a sizing limitation of 20 MB on documents' actual size.
If I were to have a significant part as generic data on this document (6 MB out of 12 MB). Suggest me which is a better approach from below.

• Drop the generic data altogether from the document and build it myself after database operation and append it to the response object that gets sent to UI layer. Again drop any generic data received from UI while upserting back to database.


• Let the current document structure stay as is. Fetch and Upsert back the entire 12 MB data each time.

If I were to adopt the first approach, I will have to create a service that builds 6 MB data by iterating with a sychronous change. I will have to call this service everytime during the database operation for this document. Is this going to be an overhead, or, will it reduce the time for the whole operation compared to fetching a 12 MB document?

javascript node.js nosql couchbase dao

share|improve this question

asked Mar 7 at 20:20

mr.Gmr.G

23

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Is the "generic data" different for every document, or the same for all?
  
  – Johan Larson
  Mar 7 at 20:56
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Attributes are same, and values can be generated by repeated iteration with a synchronous change starting from some data that is always available in the document. But when I am saying generic, I am saying that this information can be constructed from the actual impacting data stored to database.
  
  – mr.G
  Mar 8 at 17:23
  

  
  
  
  

add a comment | 

Say I have a couchbase document that is sized 12 MB (Actual size, not size on disk). Couchbase literature says there is a sizing limitation of 20 MB on documents' actual size.
If I were to have a significant part as generic data on this document (6 MB out of 12 MB). Suggest me which is a better approach from below.

• Drop the generic data altogether from the document and build it myself after database operation and append it to the response object that gets sent to UI layer. Again drop any generic data received from UI while upserting back to database.


• Let the current document structure stay as is. Fetch and Upsert back the entire 12 MB data each time.

If I were to adopt the first approach, I will have to create a service that builds 6 MB data by iterating with a sychronous change. I will have to call this service everytime during the database operation for this document. Is this going to be an overhead, or, will it reduce the time for the whole operation compared to fetching a 12 MB document?

javascript node.js nosql couchbase dao

share|improve this question

asked Mar 7 at 20:20

mr.Gmr.G

23

share|improve this question

asked Mar 7 at 20:20

mr.Gmr.G

23

share|improve this question

asked Mar 7 at 20:20

mr.Gmr.G

23

asked Mar 7 at 20:20

mr.Gmr.G

23

asked Mar 7 at 20:20

mr.Gmr.G

23