数据库服务器要求建议
我正在为客户端构建一个带有 Web 前端的 MySQL 数据库。客户及其员工每天都会使用这个网络应用程序，每年创建几千到几十万条记录。我刚刚找到了第二位客户，他希望拥有相同的产品，并且每年可能会创建相同数量的记录，甚至可能更多。
未来我希望能够接待更多的客户。在接下来的几年里，我最多可以拥有 5 个数据库和多个数据库。为 5 个不同的客户端运行的 Web 前端，所有客户端都需要严格的安全性，同时每年可能会创建数百万条记录（所有数据库中的累积记录）。
我想使用 Amazon 的 EC2 服务运行所有这些，但很难决定运行哪种类型的实例。我不确定我是否应该拥有几个不同的 Linux 实例（每个客户端一个），或者运行一个“大型”实例来管理所有客户端的数据库和 Web 前端。
我知道硬件配置对于当前的任务来说是相当特定的。 Web 前端将使用 JQuery 使 MySQL 查询变得“漂亮”，我可能会做一些数据图表（再次使用 JQuery）。前端将使用 SSL 来确保安全，据我所知，这会增加网络速度的一些开销。
我正在寻找您对这种情况的一些想法。
谢谢
I am building a MySQL database with a web front end for a client. The client and their staff will use this webapp on a daily basis, creating anywhere from a few thousand, to possibly a few hundred thousand records annually. I just picked up a second client who wishes to have the same product and will probably be creating the same number of records annually, possibly more.
In the future I hope to pick up a few more clients. In the next few years I could have up to 5 databases & web front ends running for 5 distinct clients, all needing tight security while creating, likely, millions of records annually (cumulatively across all the databases).
I would like to run all of this with Amazon's EC2 service but am having difficulty deciding on what type of instance to run. I am not sure if I should have several distinct Linux instances, one per client, or run one "large" instance which would manage all the clients' databases and web front ends.
I know that hardware configuration is rather specific to the task at hand. The web front ends will be using JQuery to make MySQL queries "pretty" and I will likely be doing some graphing of data (again with JQuery). The front ends will be using SSL for security, which I understand can add some overhead to the network speed.
I'm looking for some of your thoughts on this situation.
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
使用可用的工具。 Amazon RDS 服务可让您在云中运行 MySQL 数据库，无需额外的工作。您可以根据需要放大或缩小它 - 从小规模开始，然后当您达到极限时，增加额外的容量（需要额外付费）。
接下来，将 Elastic Load Balancing (ELB) 与 SSL 证书结合使用，这样您就可以减轻 SSL 解密的开销到亚马逊服务。
如果您的 Web 应用程序使用 Java，则可以使用 Elastic Beanstalk 处理整个托管过程你。
不要害怕尝试 - 您始终可以调整实例的大小而不会丢失数据（如果它们从 EBS 卷启动），并且您始终可以创建和删除实例。水平扩展通常比垂直扩展更好，因为您可以将实例分散到多个可用区。
祝你好运！
Use the tools that are available. The Amazon RDS service lets you run a MySQL database in the cloud with no extra effort. You can scale it up and down as you need - start small, and then as you hit your limits, add extra capacity (at extra cost).
Next, use Elastic Load Balancing (ELB) with an SSL certificate, so you offload the overhead of SSL decryption to an Amazon service.
If you're using Java for your webapp, you could use Elastic Beanstalk to handle the whole hosting process for you.
Don't be afraid to experiment - you can always resize instances with no data loss (if they boot from an EBS volume) and you can always create and delete instances. Scaling horizontally is often better than scaling vertically, as you can spread your instances across multiple Availability Zones.
Good luck!