Databases
StackOverflow2013
Postsdbo
POpractical solution for dynamodb's max item length (64k) and no-sql's lack of table joins
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POpractical solution for dynamodb's max item length (64k) and no-sql's lack of table joins
    primarykey
    data
    text
    <p><strong>First, some background context that I think may be very relevant:</strong></p> <p>I'm proofing <a href="http://aws.amazon.com/dynamodb/" rel="nofollow">dynanodb</a> as a viable solution for an upcoming app. This is a learning experiment to familiarize myself with the dynamodb offering. My platform is amazon EC2 (Linux), node.js with the <a href="https://github.com/Wantworthy/dynode" rel="nofollow">dynode</a> library.</p> <p>My question came along when considering one-to-many relationships (e.g. tags, keywords, categories, etc) in the context of no-sql, where it's not possible to join tables. At first it seemed a no-brainer: just store them as an attribute list. But then I read about the 64KB limit.</p> <p><strong>so my question:</strong></p> <p>An item, including it's attributes, (i.e. a db row with all its columns) in DynamoDB cannot exceed a total of 64KB binary size. So how do I go about checking the data to make sure it will not violate that length?</p> <p>Obviously numbers are straightforward, but "Unicode with UTF8 binary encoding" strings are going to be a challenge. </p> <p>The second part of this question might be obvious to the no-sql ninjas: how do I avoid bumping into this limitation while easing the burden of not being able to join tables? A lengthy answer is likely beyond the scope of the Q&amp;A format, but if anyone has comments or could offer alternatives I should be exploring while solving the 64k length, I would be grateful.</p> <p>Best, and thanks in advance for any and all suggestions.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKato
    1. USKato
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POpractical solution for dynamodb's max item length (64k) and no-sql's lack of table joins
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you worried about one entity having more than 64KB of tags, or something else? Also, there's no one solution to the lack of joins, it depends on what join you're replacing.
      singulars
      1. POpractical solution for dynamodb's max item length (64k) and no-sql's lack of table joins
      1. USBCoates
    2. COTrue, there is no one solution to the joins, but how do I count the binary size of the record in node? That's the primary question
      singulars
      1. POpractical solution for dynamodb's max item length (64k) and no-sql's lack of table joins
      1. USKato
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload