3 ms·
So your solution is to reimplement Basecamp on top of another database?
by sstephenson 16y ago
So your solution is to reimplement Basecamp on top of another database?
- deleted 16y ago[deleted]
- smydhacker 16y agoTHE SOLUTION IS MUNGDB
- antidaily 16y agoDuh
- prodigal_erik 16y agoFrom a couple of web searches it sounds like they're on MySQL. Targeting a database that has working transactions has to be less work than implementing transactions yourself from scratch, which it seems everyone stuck on MySQL eventually has to do (that's what they're describing, and I know we've done similar things).
- dabeeeenster 16y agoDepends what MySQL table types they are using. I think MyISAM has no transactional ability.
- gaius 16y agoI'd argue any database on modern hardware where you can't do a single transaction on a few hundred rows without noticeably affecting performance does not have "working transactions".
- Andys 16y agoRails has always been very MySQL-centric, probably because 37S & DHH use it for Basecamp. Perhaps now that PostgreSQL v9.0 has built in master/slave replication they will finally make the switch.