我正在研究基本的餐厅预订系统,并正在考虑为此项目使用 Amazon DynamoDB 。话虽这么说,我什至不确定 DynamoDB 是否适用于这种情况,或者我是否应该坚持 MySQL RDS ,因为某些查询可能非常复杂。
I'm working on basic restaurant reservation system and was thinking about using Amazon DynamoDB for this project. That being said, I'm not even sure if DynamoDB is suitable for something like this or if I should stick to MySQL RDS since some of the queries may be quite complex.
我需要的功能:
用户将提交 查找表表格
关于 DynamoDB 数据库设计的任何建议或技巧,尤其是 hash&范围用于这样的事情?
Any suggestions or tips on the DynamoDB database design especially hash & range use for something like this?
还是您认为 MySQL 数据库更适合此类应用?
Or do you think MySQL database is better suited for this kind of app?
这是一种快速的数据库设计,可让您更好地了解我要做什么。
This is a quick DB design to give you better idea what I'm trying to do.
推荐答案
我在关系数据库方面做了很多工作,在NoSQL数据库方面也做了很多工作(只是您知道我来自哪里)。恕我直言,NoSQL数据库最适合一个或多个为真的情况:
I've done a lot with relational databases, and a bit with NoSQL databases (just so you know where I'm coming from). IMHO, NoSQL databases are best suited to scenarios where either one or more are true:
您绝对可以使用Dynamo的索引编制功能来构建问题中包含的架构,但是您将试图使NoSQL数据库像RDS一样发挥作用。
You can definitely build the schema you include with your question using the indexing abilities of Dynamo, but you'd be trying to make a NoSQL database act like a RDS.
那是说:我本人将首先与Dynamo一起尝试这种学习体验。 :)
That said: I myself would try it with Dynamo first as a learning experience. :)
更多推荐
预订系统是否适用于Amazon DynamoDB / NoSQL?
发布评论