虚拟化（和云）环境中的集群和数据库复制
复制和集群都是物理（真实）服务器的服务器设置术语，通常在数据库或应用服务器级别实现。
现在的问题是：在一个虚拟化环境中，通过云服务器提供商提供的虚拟服务器的高可用性，具有“简单”的可扩展服务器（触及集群）和更高的可用性（数据库复制），我们真的需要复制和集群吗？涵盖传统服务器的问题）？ 从灵魂/应用程序提供商的角度提出问题。
请排除具有业务需求背景的复制需求，例如。需要在两个不同的地理位置复制数据库以确保性能和数据。
感谢您的见解！
Both replication and clustering are terms for servers setups with physical (real) servers, usually implemented on a DB or AS level.
Now the question: In a virtualized environment with "easy" scalable servers (touching clustering) and a higher availability (DB replication) through the means of high availability of the virtual server by the cloudserver provider, do we really need replication and clustering (as in covering the problems of traditional servers) ?
Question is asked from a soultion/application provider viewpoint.
Please exclude the need of replication with a business requirement background, eg. the need to replicate a DB at 2 different geographical locations to ensure performance and data.
Thanks for your insights !
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
虽然在大多数情况下，在专用服务器生产环境中拥有高可用性几乎是神圣的，但同样适用于云。您的云服务器所在的主机可能会像专用服务器一样出现问题。虽然大多数“好的”云主机会立即将您的服务器迁移到新的主机，但这仍然会减少停机时间......除非您有 HA 设置。在这种情况下，您已经被网络中的其他系统覆盖。
问题是，HA 设置是由您还是由您的主机负责？
关于你的排除，请从较小的范围来考虑。想象一下，如果您在加利福尼亚州有一台服务器，那么如果发生中断，可以在内华达州恢复它。理想情况下，您希望在一个地理位置有一个小集群，在另一个地理位置有一个小集群，等等。因此，如果某个数据中心的一台主机发生故障，它可以被同一数据中心的另一台服务器接收。
...如果数据中心出现故障，另一个数据中心的集群将承担负载。如果美国服务器出现故障，欧盟服务器就会恢复正常，依此类推。
我希望这能回答你的问题。
While having HA in a dedicated server production environment is next to godliness in most cases, the same applies to the cloud. The host machine your cloud server is on can have issues just as a dedicated server would. While most "good" cloud hosts will immediately work to migrate your server to a new host machine, that's still cutting in to downtime...unless you have a HA setup. In which case, you would already be covered by other systems in your network.
The question is, are you handling the HA setup, or is your host?
In regards to your exclusion, think of it on a smaller scale. Think on the level that if you had a server in California, it could be picked up in Nevada if there was an outage. Ideally, you would want to have a small cluster in one geographic location, a small cluster in another, etc. so if one goes down in one host machine in a certain datacenter, it could be picked up by another server in that same datacenter.
...And if the datacenter goes down, another datacenter's cluster takes the load. If the US goes down, EU servers pick up, and so on.
I hope that answers your question.
这不仅与可用性有关，还与性能有关。如果你的数据库服务器在云端，并不意味着你有无限的性能储备。复制通常用作扩展性能的一种手段。在云中运行数据库实际上与拥有自己的硬件没有什么不同。它可以在虚拟服务器（或多个服务器）上运行，但您也可以使用自己的硬件来执行此操作。
It isn't just about availability, it's also about performance. If your database server is in the cloud, it doesn't mean you have infinite performance reserves. Replication is often used as a means of scaling performance. Running the database in the cloud is really no different than having your own hardware. It can be running on a virtual server (or servers) but that's something you could do with your own hardware as well.