C-JDBC 1.0 Released 14
StupidEngineer writes "The C-JDBC is a middleware RAID system for databases written in Java. The 1.0 release is finally ready for download after years of the team's hard work. The system definitely has come a long way and is probably a very viable solution for those of us that can't afford large DB clustering solutions, yet still want good scalability and redundancy."
cloudscape (Score:2)
Anything with a JDBC driver (Score:2, Informative)
Cool stuff.
Nonsense... this is an awesome project (Score:3, Informative)
Here's the homepage [objectweb.org], with much better info that the download link above.
Basically, they provide a standard JDBC interface that your application can use normally (no code modification needed at all!). The driver forwards t
Re:Nonsense... this is an awesome project (Score:1)
Fantastic! (Score:2, Informative)
Memcached (Score:3, Interesting)
For all those people reading this thread looking for a cheap way to resolve DB load problems for websites etc, check out Memcached:
http://www.danga.com/memcached/
After adding a memcache layer to your site you might find 1 lowly database server is more than enough
ha-jdbc (Score:1)
It's not as feature rich as c-jdbc, but it might be another alternative for us that avoid the expensive clustering systems.
How about transactions? (Score:2)
I mean how do they handle locking with things such as SELECT FOR UPDATE?
I mean if to clients different SELECT FOR UPDATE fon the same row, could you not have a situation where one client have the lock on db1 and an other client have the lock on db2 for the same row?.
And how do they handle transaction order. I mean if to transactions a and b are comitted at the same time, could
Re:How about transactions? (Score:2, Informative)
Honestly, you *might* have to wait until all databases were finished, when performing an update, insert or delete. Otherwise how could it possibly handle a rollback (which the docs do mention, so they're supported)?
This isn't as bad as it sounds, though. It's not as if the databases were updated in sequence; they're all updating at once, so it won't take any longer than if you were us
Re:How about transactions? (Score:2)
Nice project (Score:1)
Of course it would be useless if you couldn't cluster the C-JDBC server as well--the reason you are using multiple DBs is to not have a single point of failure.
Now what I have to figure out is syncing all the databases--that would be quite a few triggers that nee
Re:Nice project (Score:1)