blocks|key|883900|text|也许我认为其中一个原因是"nosql不支持ACID“|type|unstyled|depth|inlineStyleRanges|entityRanges|data|883901|这意味着没有交易。|883902|也许它可以解释为什么不使用nosql进行“金融交易”。|883903|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Maybe I think one of the reasons is "nosql doesn't support ACID"

It's same means there is not transaction.

Maybe it can explain why no use nosql for "financial transation".

blocks|key|526121|text|SQL和NoSQL数据库不可互换。没有银弹数据库技术。在选择要用于项目的数据库技术时，您应该考虑利弊。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|526122|简短回答：如果您需要处理事务，您的数据可以很好地安排在关系实体中，然后使用SQL。如果您需要处理大量的半结构化或非结构化数据，并且需要横向可伸缩性，请使用NoSQL。|526123|如果希望更多地了解、SQL、和、NoSQL、之间的差异，请单击“这里”或“这里”。|526124|有关何时使用SQL或NoSQL的一些见解可以找到这里。|526125|entityMap|0|LINK|mutability|MUTABLE|url|http://www.thewindowsclub.com/difference-sql-nosql-comparision|1|https://www.thegeekstuff.com/2014/01/sql-vs-nosql-db|2|https://www.mongodb.com/scale/when-to-use-nosql-database^0|0|3|4|5|0|0|4|11|3|25|5|0|9|5|F|7|W|2|0|11|2|1|0|6|3|A|5|O|2|2|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|19|8|@$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|D|@$9|1E|A|1F|1|1G]|$9|1H|A|1I|1|1J]]|E|$]]|$1|J|3|K|5|6|7|1K|8|@$9|1L|A|1M|B|C]|$9|1N|A|1O|B|C]]|D|@$9|1P|A|1Q|1|1R]]|E|$]]|$1|L|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]|T|$5|O|P|Q|E|$R|U]]|V|$5|O|P|Q|E|$R|W]]]]

SQL and NoSQL databases are not interchangeable. There's no silver bullet database technology. You should consider pros and cons when choosing what database technology you want to use for your project.

Short answer: If you need to process transactions, your data can nicely be arranged in relational entities then use SQL. If you need to handle large volumes of semi-structured or unstructured data, and need horizontal scalability, then use NoSQL. 

If you want to read more about differences between SQL and NoSQL click <a href="http://www.thewindowsclub.com/difference-sql-nosql-comparision" rel="nofollow noreferrer">here</a> or <a href="https://www.thegeekstuff.com/2014/01/sql-vs-nosql-db" rel="nofollow noreferrer">here</a>.

Some insight on when to use SQL or NoSQL can be found <a href="https://www.mongodb.com/scale/when-to-use-nosql-database" rel="nofollow noreferrer">here</a>.

blocks|key|526165|text|正如@A2H所解释的那样，SQL和NoSQL取决于您的需求，说NoSQL不安全是不准确的，这就像说SQL是不可扩展的.这也不是真的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|526166|现在，对于一个金融应用程序，您将有一些非功能性的需求，我可以在下面列出：|526167|文件级别的安全:如果有人能够访问数据库文件，他们是否能够使用该文件将信息加载到其他地方？例如，在Server中，数据库的登录信息包含在文件中，因此，不使用密码复制文件将使黑客很难窃取信息。|unordered-list-item|526168|可扩展性:我们说的是多少？几百万张唱片？从什么意义上说，您需要执行分布式查询，还是只需要本地化数据库，这取决于帐户信息的区域和中央表？或者您是否计划创建一个应用程序，该应用程序将每秒接收大量记录(如外汇信息)，因此您需要一些东西来摄取大量记录并分析结果？那样的话，也许NoSQL是给你的。|526169|交易(ACID)投诉:您是否在处理交易(比如借方的类型--另一种？)然后，您可能需要使用类似Djondb或传统RDBMS的东西，两者都支持事务。|526170|灵活的模式:您需要一个灵活的模式来适应频繁的更改，而不必重新设计数据库和更新以前的记录？NoSQL对此很在行。|526171|名单还会继续。但我觉得你知道这个主意..。|526172|说NoSQL是不安全的，就像任何其他概括一样，是夸大其词。|526173|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|V|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|W|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|X|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|Y|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Z|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|R|$]]

AS explained by @A2H, the SQL and NoSQL depends on your requirements, saying that NoSQL is not secure is not accurate, this is like saying that SQL is not scalable... which is not true either.

Now, for a financial application you will have some non-functional requirements that I can list below:

<ul>
<li>Secure at file level: if someone has access to the database file will they be able to use this to load the information somewhere else? for example, in SQL Server the login information about the db is included in the files, therefore copying the files without the password will make hard for hackers to steal information.</li>
<li>Scalable: How much,are we talking about? some millions records? Scalable in what sense, do you require to do distributed queries or just localized databases depending on the region and central tables for accounts info? or are you planning to create an application that will receive tons of records per second (like forex information) and therefore you need something to ingest tons of records and analyse results? in that case maybe NoSQL is for you.</li>
<li>Transaction (ACID) complaint: Are you handling transactions (like the type of debit this credit this other?) then you might need to use something like Djondb or traditional RDBMS, both support transactions.</li>
<li>Flexible schemas: You need a flexible schema that can adapts to your frequent changes without having to redesign your database and updating previous records? NoSQL is good at this.</li>
</ul>

the list will continue... but I think you get the idea...

Saying that NoSQL is un-secure is an overstatement, as any other generalisation.

blocks|key|526200|text|在支付、转帐、股票市场交易的情况下，我们需要严格的酸。甚至简单的事情，如，我想阅读我的帐户余额(100美元)和取款90美元，但在我可以取款之前，我的妻子提取80美元。因此，银行最终在我的账户中出现负余额，这很可能违反了银行不允许负余额的一些规定。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|526201|那我们该怎么办？关系数据库提供了优秀的ACID和数据库锁定工具。人们也可以在MongoDB上进行黑客攻击，但黑客仍然是黑客。MongoDB正在开发ACID等，但是在一个基于分布式碎片的系统中，没有很强的一致性，我会远离它。|526202|最后，在服务器端应用程序的微服务体系结构时代，每个服务都有数据库(我指的不是专门的物理服务，而是逻辑上每个服务的db+)。因此，有两个数据库很简单:一个是MongoDB，另一个是关系数据库。将关系用于事务性事务，这将仅占用例的10%25。其余的用例使用MongoDB，如浏览数据、图像、阅读评论、内容、帐户历史等。因此，由于90%25%2B上的大多数用例都是基于MongoDB的，所以仍然达到了高可伸缩性的目的。|526203|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

In scenario of making payments, transferring money between accounts, stock market transactions, we need strict ACID. Even simple things like, I want to read my account balance ($100) and withdraw $90, but before I can withdraw, my wife withdraws $80. So bank ends up with negative balance in my account which probably violates some rule that bank disallows negative balance.
 
So what do we do about this? Relational databases provide excellent ACID and database locking tools. One can hack around in MongoDB too, but hack is still a hack. MongoDB is coming up with ACID etc, but in a distributed shards based system with no strong consistency, I would stay away from it.
 
Finally, in era of micro services architecture on server side apps, we have database per service (not dedicated physical I mean, but logically a db per service). So it is straightforward to have two databases; a MongoDB and a Relational. Use relational for transactional stuff which will be barely 10% of use cases. Use MongoDB for the remainder use cases like, browsing data, images, reading reviews, content, accounts history etc etc. So since most uses cases over 90%+ will be MongoDB based, so still achieve the goal of high scalability.

I heard from a speaker at a Hackaton event organized by a bank that you should not use nosql for financial transaction for security reasons. But I have no idea what he's saying. I have been looking for an answer as to why I should not use nosql database in my application.

What are the pros and cons of nosql, and what are the pros and cons about sql databases for financial transaction?

Now, I'm building an application for shop cashier, where the cashier will use this app to store transactions, receive orders, and receive payments with Cash or Credit Card.

What is the best possible approach for this project's API? SQL or NoSQL, and why?

Why you should not use nosql for financial transaction

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我在一家银行组织的Hackaton活动上听到一位发言者说，出于安全原因，您不应该在金融交易中使用nosql。但我不知道他在说什么。我一直在寻找一个答案，为什么我不应该在我的应用程序中使用nosql数据库。nosql的优点和缺点是什么，金融交易sql数据库的优缺点是什么？现在，我正在为商店出纳员建立一个应用程序，出纳员将...

问为什么不使用nosql进行金融事务处理？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么不使用nosql进行金融事务处理？EN