用于故障转移的 DBMS
我们正在开发场馆支付系统。 现在我们正在考虑为我们的应用程序使用什么 DBMS。 目前我们正在使用微软的sqlexpress来存储我们的数据。 但由于该系统将在非常繁忙的场所使用，我们认为我们需要一个故障转移系统来应对数据库服务器出现故障的情况。 我们一直在考虑使用 mssql 服务器进行复制，但是对于（希望）永远不会发生的情况来说，这将花费大量资金。 数据库只能运行几个小时（场地持续时间），最长可达几天。 但如果数据库宕机 30 分钟，就没有人可以点饮料或进入会场。场内有数千人，这会造成很多麻烦。
那么...任何人都可以分享他的一些专业知识和/或为我分享一些有关故障转移、复制或其他内容的读物吗？
提前致谢
We are developing a payment system for venues.
Now we're considering what DBMS to use for our application.
At the moment we're using microsoft's sql express to store our data.
But because the system is going to be used on very busy venues, we think we need a failover system for the case the database server goes down.
We have been looking at using mssql server for replication, but that is going to cost a lot of money for a case that is (hopefully) never going to happen.
The database has to be up for only a couple of hours (duration of venue) to max a couple of days.
But if the database is down for 30 minutes, noone can order drinks or get access to the venue. And with thousands of people in the venue, thats going to cause a lot of trouble.
So... can anyone share some of his expretise and/or share some reads for me about failovers, replication or anything?
Thanks in advance
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我建议您忘记 DBMS，直到您有清晰的业务计划、系统架构和明确的可用性目标。理想情况下，找到以前实施过此类系统的人并雇用他们或使用他们作为顾问。
您还必须考虑如果系统出现故障您将损失多少钱：实际销售额、声誉和未来业务的损失、合同处罚条款等。与这些成本相比，添加第二台服务器可能看起来相当便宜。但它们将在哪里托管、连接如何工作、谁负责运营等？如果您唯一的 POS 终端 Wifi 基站突然失效，拥有完全冗余的故障转移数据库集群对您没有任何帮助。
也许您已经考虑并回答了所有这些问题，如果是这样，在您的问题中添加一些有关您所拥有的主要限制和要求的更多详细信息会很有帮助。
I would suggest that you forget about the DBMS until you have a clear business plan, systems architecture and defined goals for availability. Ideally, find someone who has implemented a system like this before and hire them or use them as a consultant.
You also have to look into how much money you will lose if the system goes down: actual sales, loss of reputation and future business, contractual penalty clauses etc. Compared to those costs, adding a second server might start looking fairly cheap. But where will they be hosted, how does connectivity work, who does Operations etc.? Having a fully redundant failover database cluster will not help you if your one and only Wifi base station for the POS terminals suddenly dies.
Perhaps you have already considered and answered all these questions, and if so it would be helpful to add some more details to your question about the main constraints and requirements you have.