16 ms·
If you're running into concurrency issues, than both MySQL or Postgres are good solutions. Tanks compared to SQLite? Yes. Slower? No. But if you're looking int
by selectnull 10y ago
If you're running into concurrency issues, than both MySQL or Postgres are good solutions. Tanks compared to SQLite? Yes. Slower? No.
But if you're looking into something small, check out Firebird (http://firebirdsql.org/ http://firebirdsql.org/).
It's fully ACID compliant relational database, can work both in embedded or client/server mode, fast, easy to maintain and cross platform. IMHO, the only drawback of that RDBMS is small(er) developer mindshare. I worked a lot with it before (8 years ago) and loved it.
- dozzie 10y ago8 years ago I actually disliked it, because it was descendant of Borland's database and shared with it the administration tools and documentation. In both aspects it was worse than PostgreSQL or MySQL. I don't know if anything got better, because I haven't worked with it ever since.
- selectnull 10y agoYes, Firebird came to the world after Borland's Interbase got open sourced. After that, Borland continued with Interbase development and they kinda existed for a while. I have no clue what happened to Interbase afterwards, as I've stopped caring. As a former Delphi developer, I also dislike Borland. But I very much loved their products, no reason I would dismiss one just because it was made by Borland (and I'm talking about "new" Borland, not the Borland of the 80es and early 90es which was awesome).
- dozzie 10y agoIt's not that I disliked Firebird because Borland. I disliked it because tools and procedures (mainly the latter) were underdocumented and felt unpleasant to work with from a sysadmin's perspective compared to PostgreSQL and MySQL. At that time I didn't care about Borland for a long time already, because I was a Linux sysadmin then.
- rgacote 10y agoNice Firebird feature is the ability to embed it and run without a server.