Best way to structure AWS's DyanomoDB for user accounts?
<p>This is from an Android context. I'm using Amazon Web Service's sdk to build an Android app that has basic social media functions. I'll need to store users, their posts, misc data, etc... I'm thinking of structuring it like this:</p>

<p>One big Table called "Users" which will contain an Item for each user. And then just have a ton of attributes for each user that stores all of their posts and misc data. </p>

<p>But I'd love to hear other opinions on how I should best structure this thing. I have essentially no experience with this sort of thing so I can't help but suspect that I'm going about this wrong. </p>

<p>Thanks</p>