Hot answers tagged distributed-databases
OK, let's imagine that you have a distributed database. Let's say you have a node in Oregon and one in California. The CAP theory says that you will run into problems when setting up this type of database. For example, if you query data from one database, it needs to be the same as the data in the other database. This insures that whatever value you have ...
BigTable doesn't use SQL (a query language) so SQL can't be used directly to query the database. And BigTable doesn't have "relations" in the same way as relational databases, it's more like bare tables. If you want to get data from two tables, you have to do two lookups, and combine the result set in the application code. In other words the "join" ...
I have been in a similar situation and highly recommend looking into MongoDB or HBase for your needs. The others (Cassandra/Redis) are good too, but HBase and MongoDB have been battle-tested in large environments, have a large community, good documentation (MongoDB's is better) and generally fulfill the three requirements you are looking for.
If I understand you right, you are going from DB2 10.1 Express-C edition to DB2 10.1 Work Group Server Edition or Enterprise Edition. If that is case then you shouldn't have any issues. The binaries for DB2 are basically the same across editions. It is just a matter of a license file that enables or disables certain features and enables/disables use of ...
If you are looking for data models to start with, I'd recommend you take a look at: http://www.databaseanswers.org/data_models/index.htm This is the most comprehensive list of data model examples that I found so far. In fact I have used some samples as starting point for some of my projects. These models won't show you how to take horizontal fragmentation ...
How big are the keys? How big are the values? Will the data arrive "continually", or is this a one-time load? Let's see all the representative queries. You have mentioned only SELECT val FROM tbl WHERE key = 'constant'; Are there others ? In general key-value stores suck big time. But maybe we can make your special case work not-too-badly.
They are not really the same, because of the scope of the data ACID Atomicity Consistency : All Applied Data Changes Provide Consistent View of Data For All DB Connections Isolation Durability CAP Consistency (All Nodes Have Same Data via Eventual Consistency) Availability Partition-Tolerance : system continues to operate despite arbitrary message ...
Postgres-XC does not run on Windows: Postgres-XC currently runs on the Linux Operating Systems running on 64-bit Intel(R) processors. The development team tested this with Cent-OS 5.3 and 5.4. You might be able to build the data nodes and possibly the coordinators on Windows, but the GTM will take major work to port to Windows.
HP Vertica has their community edition for download at https://my.vertica.com/download-community-edition/. If you don't have one already, you will be prompted to create a MyVertica login. If you have problems creating a login, please email me at firstname.lastname@example.org. If you have further issues loading your data, you can tweet at @VerticaHelp and support will ...
Don't do this with only one slave. If you do you are making your application more subject to failure, not less. Basically if you do this, and you lose your slave, your master will hang. You say your backup box is crappy, and I assume that means reliability-wise too, so this is more likely than losing your master. This is probably not what you want. Do ...
To my knowledge it does not allow that level of parallelism. If that's what you are trying to do the best approach is to go with Postgres-XC or GridSQL, but Postgres-XC while more complex is also more flexible. http://postgres-xc.sourceforge.net/ is the project page.
Only top voted, non community-wiki answers of a minimum length are eligible