blocks|key|4130160|text|你应该阅读Automated+Teller+Machine，Online+transaction+processing和其他关于数据加密的主题，如果你想在网站上使用HTTPS，也可以考虑使用HTTPS。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4130161|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Automatic_teller_machine|1|http://en.wikipedia.org/wiki/Online_transaction_processing^0|5|O|0|U|T|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

You should read about <a href="http://en.wikipedia.org/wiki/Automatic_teller_machine" rel="nofollow">Automated Teller Machine</a>, <a href="http://en.wikipedia.org/wiki/Online_transaction_processing" rel="nofollow">Online transaction processing</a>, and others topics about data encryption, also consider use HTTPS if you are thinking on web sites.

blocks|key|5598523|text|基本技术是消除任何单点故障。任何在设置中可能失败的东西都需要一个备份或多个备份。从多个交换机、服务器、UPS、硬盘等...数据库不断被复制，数据被备份并存储在异地，以防发生火灾或其他可能使建筑物变得复杂的灾难。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5598524|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The basic technique is removing any single point of failure. Anything that can fail in your setup needs to have a back or multiple backups. From Multiple switches, servers, UPSs, harddrives, etc... Databases are constantly being replicated, and data is backed up and stored off site in case of a fire or other disaster which could comprimise the building.

blocks|key|4130146|text|这一切都可以归结为在两个地方拥有相同的数据；从下到在提交数据之前持有缓存的代码，一直到服务器冗余。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4130147|确保你不会丢失东西的唯一方法就是拥有它的多个副本。|4130148|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It can all really boil down to having the same data in two places; from down to a the code which is holding a cache prior to a commitment of data, all the way up to server redundancy.

The only way to make sure you don't lose something is have multiple copies of it.

blocks|key|1503161|text|您可能希望阅读有关XA或X/Open事务的知识，这些事务可以协调多个系统，包括数据库、队列等，并将更多内容整合到ACID+DB类事务中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1503162|我没有使用过它，但我听说它在延迟和计算方面都很昂贵。但是话又说回来，你的数据完整性值多少钱？|1503163|http://en.wikipedia.org/wiki/X/Open_XA|offset|length|1503164|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|12|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@$F|R|G|S|1|T]]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|E]]]]

You might want to read up on XA or X/Open transactions which can co-ordinate multiple systems including databases, queues, and more into ACID DB-like transactions.

I've not worked with it but I've heard it can be expensive latency-wise and computationally. But then again how much is your data integrity worth?

<a href="http://en.wikipedia.org/wiki/X/Open_XA" rel="nofollow">http://en.wikipedia.org/wiki/X/Open_XA</a>

blocks|key|5598609|text|在银行示例的情况下，每个银行都会为每笔交易保留一个记录，说明什么是金额，金额是多少，从哪里开始，金额是多少，以及它们的时间顺序|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5598610|这样以后如果出现问题，您可以比较两个事务日志，如果它们不匹配，则可以识别丢失的事务|5598611|这也涵盖了一个问题，即一家银行不能信任另一家银行为其保存记录|5598612|当他们交叉检查时，这几乎是一个分布式事务协议|5598613|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

in the case of the bank example, each bank would keep a record for every transaction stating what how much and to where and from where and how much and their time order

so that later if there is a problem you compare the two transaction logs if they don't match you can identify the missing transactions

this also covers the problem that one bank can't trust another to keep records for it

as they cross check this is almost a distributed transaction protocol

blocks|key|4130262|text|正如您已经提到的，有各种机制(如事务)可以确保基于软件的“握手”是可靠的，并成功完成。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4130263|架构真的-是的，拥有两份拷贝会给你带来冗余，这有助于不丢失东西。除此之外：|4130264|4130265|Clear+Processes:人们需要准确地知道信息的去向-无论是在晴朗的日子里，还是在棕色的东西击中风扇的时候。拥有数据，但无法找到它，或无法识别它，就像丢失它一样糟糕。你的流程越清晰(而且有充分的文档记录)，better.|unordered-list-item|4130266|Consistency:自动化显然比随机的人为错误更好。|4130267|专门回答了你的问题-但上面的几点应该在清晰的体系结构和设计中得到回应，并且清楚地将possible.|4130268|Focus的故障点与对高风险领域的关注分开。|4130269|使用经过验证的技术(我猜这就是你真正想要的)。|4130270|使事情尽可能简单。|4130271|4130272|不久前，我为一个现成的文档管理系统开发了一个解决方案架构；没有数据丢失是主要的驱动因素。该系统是在全国范围内推出的，因此在服务于本地用户的“地区性”缓存和实际的“数据中心”方面都是多站点的。一些有趣的地方：|4130273|4130274|所有组件(在可能的情况下)都部署到虚拟机箱上，并将其返回到SAN，因此在发生物理主机宕机事件时，我们可以更快地恢复服务。在数据丢失方面，这意味着如果系统宕机，用户更有可能使用受保护的系统，而不是将数据存储在本地。|4130275|另外，SAN被认为比本地磁盘更安全。|4130276|上述内容是现有设置的一部分，因此对于Ops+to+SAN+site而言，复制并不是什么新鲜事。这不是实时的，数据库上的事务日志增加了这一点。|4130277|4130278|我猜所有这些都不是以软件为中心的，但我确实认为“我们”使用的所有好的软件架构/设计原则都有助于指导我的思考。|offset|length|style|BOLD|4130279|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|A|2|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|1D|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|1E|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|1F|8|@]|9|@]|A|$]]|$1|L|3|M|5|G|7|1G|8|@]|9|@]|A|$]]|$1|N|3|O|5|G|7|1H|8|@]|9|@]|A|$]]|$1|P|3|Q|5|G|7|1I|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1K|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|V|3|W|5|G|7|1M|8|@]|9|@]|A|$]]|$1|X|3|Y|5|G|7|1N|8|@]|9|@]|A|$]]|$1|Z|3|10|5|G|7|1O|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1Q|8|@$14|1R|15|1S|16|17]]|9|@]|A|$]]|$1|18|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]]|19|$]]

As you've alluded to, there are various mechanisms (like transactions) for ensuring the software based "handshake" is reliable and completes successfully.

Architectureally - yes having two copies of stuff gives you redundencey which helps not losing stuff. beyond that: 

<ul>
<li>Clear Processes: people need to know exactly where information is going - both in sunny day senarios and when the brown stuff hits the fan. Having the data but not being able to find it, or recognise it is just as bad as lossing it. The clearer (and well documented) your processes are the better.</li>
<li>Consistency: automated is obviously better that random human error.</li>
<li>To specifically answer your question - but the above points should be echoed in an architecture and design that was clear, and which clearly seperated concerns.</li>
<li>Reduce points of failure as much as possible.</li>
<li>Focus attention on higher risk areas.</li>
<li>Use proven techniques (I guess that's what you're actually asking for).</li>
<li>Keep things as simple as possible.</li>
</ul>

I worked on a solution architecture for an off-the-shelf document management system a while back; no loss of data was the big driver. The system was rolled out nationally, so multi-site in terms of both 'regional' caches for servicing local users, and actual 'data centers'. Some points of interest:

<ul>
<li>All components (where possible) were deployed onto virtual boxes, which were back-ed to a SAN, so iun the event of a physcial host going down we could restore service faster. In terms of data loss it means that users are more likely to be able to use the protected system than storing stuff locally if the system was down. </li>
<li>Also, the SAN was seen as being more safer than local disks.</li>
<li>The above was part of the existing set-up, so nothing new for Ops to learn.</li>
<li>Failover site, with replication. This wasn't real-time, and was augmented by the transactional logs on the databases.</li>
</ul>

I guess none of this is heavily software centered, but I do think that all the good software architecture / design principles "we" use helped guide my thinking.

I'm curious about techniques used to build a system where ensuring that no data is lost is of the utmost priority. For a simplistic example, what does a financial institution do to make sure that when money is transferred between accounts, once it is withdrawn from one account it is without a doubt put in the other account. I'm not so much looking for particular techniques like database transactions, but larger, more architecty concepts, like how the data is saved if a server goes down, or a queue runs out of space, or whatever.

If someone could point me to books or articles on I'd be much obliged.

Never losing data techniques

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我对用于构建系统的技术感到好奇，在这种系统中，确保数据不丢失是最重要的。举一个简单的例子，一家金融机构如何确保资金在账户之间转移时，一旦从一个账户提取，毫无疑问会存入另一个账户。我并不是在寻找特定的技术，比如数据库事务，而是更大、更具体系结构的概念，比如在服务器宕机、队列空间耗尽等情况下如何保存数据。如果有人能给我指点一些书或文章，我将不胜感激。

问永不丢失数据技术
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问永不丢失数据技术EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问永不丢失数据技术
EN