【MongoDB】應用情境

標籤：style   os   使用   io   ar   for   檔案   資料   問題   

24 Use Cases
24.1適合情境
?Archiving and event logging
?歸檔和日誌記錄
?Document and Content Management Systems - as a document-oriented (JSON) database, MongoDB‘s flexible schemas are a good fit for this.
?文檔和記憶體管理系統-作為面向文檔資料庫，mongodb的靈活的結構正適合這個
?ECommerce. Several sites are using MongoDB as the core of their ecommerce infrastructure (often in combination with an RDBMS for the final order processing and accounting).
?電子商務,採用mongoDB作為電子商務網站基礎設施（通常聯合關係型資料庫處理訂單流程和財務流程）
?Gaming. High performance small read/writes are a good fit for MongoDB; also for certain games geospatial indexes can be helpful.
?遊戲.高效能的讀/寫正適合mongodb；而且對某些遊戲來說，地理資訊的索引也非常有用
?High volume problems.  Problems where a traditional DBMS might be too expensive for the data in question.  In many cases developers would traditionally write custom code to a filesystem instead using flat files or other methodologies.
?高容量問題.這種問題對關係型資料庫來說花費很大，許多情況，開發人員通常寫入到檔案系統
?Mobile. Specifically, the server-side infrastructure of mobile systems. Geospatial key here.
?移動通訊.特別的，手機通訊服務端的基礎建設，比如地理空間資訊
?Operational data store of a web site MongoDB is very good at real-time inserts, updates, and queries. Scalability and replication are provided which are necessary functions for large web sites‘ real-time data stores. Specific web use case examples:
?運營網站，mongoDB非常適合即時的插入更新和查詢。延展性和複製提供大型網站的即時資料的儲存提供了保障。
?content management記憶體管理
?comment storage, management, voting 評論儲存，管理和投票
?user registration, profile, session data 使用者註冊、簡介、session資料
?Projects using iterative/agile development methodologies.  Mongo‘s BSON data format makes it very easy to store and retrieve data in a document-style / "schemaless" format. Addition of new properties to existing objects is easy and does not generally require blocking "ALTER TABLE" style operations.
?項目採用迭代或者極限開發方式。MongoDB的BSON資料格式使儲存和接收資料簡單。
?Real-time stats/analytics
?即時狀態分析
24.2不適合情境
?Systems with a heavy emphasis on complex transactions such as banking systems and accounting.  These systems typically require multi-object transactions, which MongoDB doesn‘t support. It‘s worth noting that, unlike many "NoSQL" solutions, MongoDB does support atomic operations on single documents.  As documents can be rich entities; for many use cases, this is sufficient.
?需要複雜的事務支援的系統如銀行系統，借貸系統等。這些系統需要多個物件的事務，但是mongoDB不支援。值得注意的是，跟其他的NOSQL解決方案不同的是，MongoDB支援單文檔的原子操作。由於文檔能成為實體，對許多情境來說，這已足夠了。
?Traditional Non-Realtime Data Warehousing. Traditional relational data warehouses and variants (columnar relational) are well suited for certain business intelligence problems – especially if you need SQL (see below) to use client tools (e.g. MicroStrategy) with the database. For cases where the analytics are realtime, the data very complicated to model in relationa, or where the data volume is huge, MongoDB may be a fit.
?傳統的非即時的資料倉儲。傳統或者變種的關係型資料倉儲非常適合於某些商業智慧問題。特別是當你需要使用用戶端工具操作資料庫SQL的時候。當需要即時分析時，而且相對於關係型資料庫資料模型複雜，或者資料容量很大，mongoDB非常即時
?Problems requiring SQL.
?需要SQL解決的問題。

【MongoDB】應用情境