In your case of just contact and address data I would choose Amazon SimpleDB. I know SimpleDB might not be suitable for a large number of tables with relationships and all, but for your kind of data I think SimpleDB is sufficient. And costs is much much cheaper than Amazon RDS.
I also wanted to use RDS, but the smallest db size costs $80 p/month.
一种方法可能是设置/使用托管包，该包具有链接到 mySQL 数据库的 phpMyAdmin 之类的内容。这样做可以在没有网站前端的情况下访问和编辑数据库等。不漂亮（像网站前端）但实用。一个好的主人还应该为你提供支持。
另外一个就是看Google Documents。好吧，它实际上不是一个数据库，而是一个电子表格，但非常类似于 Excel。您可以与受邀人员共享 Google 文档，甚至可以通过 Google 文档建立一个小型网站。这是一种免费方法，但根据您的需要可能不太实用。
With out a bit more info I may be way off base here. but 2000 names addresses etc. is not a large DB and I would have thought that the possible use of Amazons RDS was a bit "overkill" to say the least.
Depending on how (and who) you want view edit etc. there are a number of free or almost free alternatives.
One method may be to set up /use a hosting package that has something like phpMyAdmin linked to a mySQL DB. Doing this it is possible to access and edit etc. the DB without having a website front end. Not pretty (like a website front end) but practical. A good host should also back up for you.
Another is to look at Google Documents. OK not really a database more a spread sheet, but very much on the lines of Excel. You can share Google docs with invited people and even set up a small website via Google Docs. This is a free method, but may not be that practical depending on your needs.
Have you taken a look at Microsoft SQL Azure? You can use it free for something like 90 days and then if you only need a 1GB db it would only be about $10 a month.
You mention backup so I thought I would talk about that as well. They way SQL Azure works is that it automatically creates 2 additional copies of your database on different machines in the data center. If one of the machines or db's become unavailable it automatically fails over to one of the other db's.
it's inprocess, easy to constantly .dump off to S3 and you can use update hooks to keep checkpoints after updates. backups/restores are almost the equivalent of windows batchfiles and wgets
standard OS Filesystem and user level ACLs control security.
running a file backed db makes sense given the fragility of a normal EC2 backed RDBMS to EBS gremlins.
there are exclusions from to SQL92 (no real showstoppers), but given the project cost sensitivity and the RPO and RTO's of an alumni database, I reckon it's a good bet.
发布评论
评论（5）
如果您只需要联系方式和地址数据，我会选择 Amazon SimpleDB。我知道 SimpleDB 可能不适合大量具有关系的表，但对于您的数据类型，我认为 SimpleDB 就足够了。而且成本比Amazon RDS便宜很多。
我还想使用 RDS，但最小的数据库大小每月花费 80 美元。
In your case of just contact and address data I would choose Amazon SimpleDB. I know SimpleDB might not be suitable for a large number of tables with relationships and all, but for your kind of data I think SimpleDB is sufficient. And costs is much much cheaper than Amazon RDS.
I also wanted to use RDS, but the smallest db size costs $80 p/month.
如果没有更多信息，我可能会偏离基地。但 2000 个名称地址等并不是一个大数据库，我认为亚马逊 RDS 的可能使用至少可以说有点“矫枉过正”。
根据您想要查看编辑等的方式（以及谁），有许多免费或几乎免费的替代方案。
一种方法可能是设置/使用托管包，该包具有链接到 mySQL 数据库的 phpMyAdmin 之类的内容。这样做可以在没有网站前端的情况下访问和编辑数据库等。不漂亮（像网站前端）但实用。一个好的主人还应该为你提供支持。
另外一个就是看Google Documents。好吧，它实际上不是一个数据库，而是一个电子表格，但非常类似于 Excel。您可以与受邀人员共享 Google 文档，甚至可以通过 Google 文档建立一个小型网站。这是一种免费方法，但根据您的需要可能不太实用。
With out a bit more info I may be way off base here. but 2000 names addresses etc. is not a large DB and I would have thought that the possible use of Amazons RDS was a bit "overkill" to say the least.
Depending on how (and who) you want view edit etc. there are a number of free or almost free alternatives.
One method may be to set up /use a hosting package that has something like phpMyAdmin linked to a mySQL DB. Doing this it is possible to access and edit etc. the DB without having a website front end. Not pretty (like a website front end) but practical. A good host should also back up for you.
Another is to look at Google Documents. OK not really a database more a spread sheet, but very much on the lines of Excel. You can share Google docs with invited people and even set up a small website via Google Docs. This is a free method, but may not be that practical depending on your needs.
您是否看过 Microsoft SQL Azure？您可以免费使用大约 90 天，然后如果您只需要 1GB 数据库，每月只需大约 10 美元。
你提到了备份，所以我想我也应该谈谈这个问题。 SQL Azure 的工作方式是，它会在数据中心的不同计算机上自动创建数据库的 2 个附加副本。如果其中一台机器或数据库不可用，它会自动故障转移到其他数据库之一。
如果您需要以上任何内容，还可以使用复制命令来备份数据库。
Have you taken a look at Microsoft SQL Azure? You can use it free for something like 90 days and then if you only need a 1GB db it would only be about $10 a month.
You mention backup so I thought I would talk about that as well. They way SQL Azure works is that it automatically creates 2 additional copies of your database on different machines in the data center. If one of the machines or db's become unavailable it automatically fails over to one of the other db's.
If you need anything above that you can also use the copy command to backup the database.
您可以检查
http://www.enciva.com/postgresql9-hosting.htm
和
http://www.acugis.com/postgresql-hosting.htm
他们为 Postgres 工作和MySQL。
You can check
http://www.enciva.com/postgresql9-hosting.htm
and
http://www.acugis.com/postgresql-hosting.htm
They work for Postgres and MySQL.
对于这种大小的坦率的小数据库，我会认真考虑 http://www.sqlite.org/
它是进程内的，很容易不断地转储到 S3，并且您可以使用更新挂钩在更新后保留检查点。
备份/恢复几乎相当于 Windows 批处理文件，并且
使用 http://sqlcipher.net/
标准操作系统文件系统 进行良好的加密和用户级 ACL 控制安全性。
考虑到普通 EC2 支持的 RDBMS 到 EBS gremlin 的脆弱性，运行文件支持的数据库是有意义的。
SQL92 除外（没有真正的阻碍），但考虑到项目成本敏感性以及 alumni 数据库的 RPO 和 RTO，我认为这是一个不错的选择。
For a frankly tiny db of that size I'd seriously look at http://www.sqlite.org/
it's inprocess, easy to constantly .dump off to S3 and you can use update hooks to keep checkpoints after updates.
backups/restores are almost the equivalent of windows batchfiles and wgets
good encryption using http://sqlcipher.net/
standard OS Filesystem and user level ACLs control security.
running a file backed db makes sense given the fragility of a normal EC2 backed RDBMS to EBS gremlins.
there are exclusions from to SQL92 (no real showstoppers), but given the project cost sensitivity and the RPO and RTO's of an alumni database, I reckon it's a good bet.