DBMS > FatDB vs. Infobright
System Properties Comparison FatDB vs. Infobright
Please select another system to include it in the comparison.
Our visitors often compare FatDB and Infobright with SQLite, OpenTSDB and MySQL.
|Editorial information provided by DB-Engines|
|Name||FatDB Xexclude from comparison||Infobright Xexclude from comparison|
|FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.|
|Description||A .NET NoSQL DBMS that can integrate with and extend SQL Server.||High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend|
|Primary database model||Document store|
|Developer||FatCloud||Ignite Technologies Inc.; formerly InfoBright Inc.|
|License Commercial or Open Source||commercial||commercial The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016|
|Cloud-based only Only available as a cloud service||no||no|
|DBaaS offerings (sponsored links) Database as a Service|
Providers of DBaaS offerings, please contact us to be listed.
|Server operating systems||Windows||Linux|
|Typing predefined data types such as float or date||yes||yes|
|XML support Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.||no|
|Secondary indexes||yes||no Knowledge Grid Technology used instead|
|SQL Support of SQL||no Via inetgration in SQL Server||yes|
|APIs and other access methods||.NET Client API|
RESTful HTTP API
Windows WCF Bindings
|Supported programming languages||C#||.Net|
|Server-side scripts Stored procedures||yes via applications||no|
|Triggers||yes via applications||no|
|Partitioning methods Methods for storing different data on different nodes||Sharding||none|
|Replication methods Methods for redundantly storing data on multiple nodes||selectable replication factor||Source-replica replication|
|MapReduce Offers an API for user-defined Map/Reduce methods||yes||no|
|Consistency concepts Methods to ensure consistency in a distributed system||Eventual Consistency|
|Foreign keys Referential integrity||no||no|
|Transaction concepts Support to ensure data integrity after non-atomic manipulations of data||no||ACID|
|Concurrency Support for concurrent manipulation of data||yes||yes|
|Durability Support for making data persistent||yes||yes|
|In-memory capabilities Is there an option to define some or all structures to be held in-memory only.||yes|
|User concepts Access control||no Can implement custom security layer via applications||fine grained access rights according to SQL-standard exploiting MySQL or PostgreSQL frontend capabilities|
More information provided by the system vendor
We invite representatives of system vendors to contact us for updating and extending the system information,
Related products and services
We invite representatives of vendors of related products to contact us for presenting information about their offerings here.
|Recent citations in the news|
Should I use the Infobright database or is there a better aggregation solution?
Writing to Infobright Database
Fig. 1. Loading and querying in Infobright database system. Data is...
provided by Google News
Share this page