Which AWS Database Should I Use for My Key-ID Mapping Needs?

0
7
Asked By TechieTurtle42 On

I'm looking for some guidance on choosing the right AWS database for my project. I have keys labeled A, B, C, D, E, F, and G, and each points to an ID. Sometimes, keys can have optional values (like A, *, C, *, E, F, G), where * means that value isn't mandatory. I want to find all overlapping keys based on a given key, and I also need to retrieve and update information related to these key-ID pairs. My access requirements include getting all matching keys for a specific key, updating all matching keys based on custom logic, and listing keys associated with a specific ID or attribute. Additionally, I anticipate that I might want to add more keys or attributes in the future. I need advice on which AWS database (like DynamoDB, DocumentDB, Neptune, OpenSearch, etc.) would best fit these needs.

4 Answers

Answered By DataWhiz99 On

If you don't have a huge amount of complexity or scale involved, starting with a standard relational database like Postgres is a solid choice. It's user-friendly and versatile for most use cases. If you reach a point where your needs outgrow it, you can then consider specialized databases without too much hassle. You'll likely have the resources to manage a transition at that stage anyway.

Answered By GraphGuru77 On

Based on your needs, it sounds like you might benefit from a graph database due to the relationships between your keys. AWS Neptune could be a good fit here if you need to model complex relationships. However, it might be overkill depending on your team's experience and if you have the infrastructure to manage it.

Answered By DBMaster31 On

First, you should clarify your requirements, but I would lean towards a traditional relational database for your scenario. Something like RDS or Aurora could work well, especially since you might want to leverage relationships between your keys. Setting up tables for your keys and metadata sounds like a straightforward approach.

Answered By SQLSavant22 On

I recommend sticking with relational databases like Postgres or MySQL, as they’re suited for your SQL query needs. SQL can handle the relationships you're describing quite effectively, and it’s easier to set up and manage without diving into more complex or niche setups.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.