Need data model advice for an AWS app

I'm building a news application. Each article can be tagged with words like "Politics", "Food", "San Jose, CA". I'd like users to be able to select a tag, and see all related articles. What would be the recommended way of storing this data?

My instinct is to use S3 for each news article and tag, and then to use DynamoDB to store the relationship of tag to article (edges). So, when a user wants to view articles for a tag, I'd retrieve the S3 object for that tag, do a DynamoDB query for the ID's of articles associated with that tag, and then retrieve the S3 objects for each article.

Does this sound like a good plan, or is there a better way?
zumpoofAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bbaoIT ConsultantCommented:
i think it depends on how S3 tags are used to classify an article and its content.

say if search criteria are limited to article catigories only, it will be rarely having more than 100 categories, commonly about 20. in this case, a tags-only solution might be simple yet working well.

say if search critrria are for randomly defined keywords or attributes, especially one attribute may have multiple related attributes depending on the content of an article, then the tagging mechanism and query APIs of S3 can't handle that in an efficient way. in this case, DynamoDB is a good choice to manage the attributes, keywords, relationships and their index.

actually S3 plus DynamoDB is one of the best practices in managing metadata for S3 based BOLB data. below AWS blog is a very good reference and just for your scenario. please review.

https://aws.amazon.com/blogs/big-data/building-and-maintaining-an-amazon-s3-metadata-index-without-servers/

hope it helps,
bbao
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
AWS

From novice to tech pro — start learning today.