Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Logging in...
Previously on "MySQL or PostgreSQL for high-volume high-performance database?"
Yep, most of clientco's clients send them data in CSV format.
But most of the baboons who write the code to produce the CSV seem to have no idea there is a CSV standard. So we have endless problems with the data (although it all helps keep me in contract!)
Might be worth running them through Simon Willison's csvs-to-sqlite - although SQLite might not be a suitable database for your end product, it's easier to automate the extraction of the data from it after the import so you can get it into wherever it needs to be.
If you talking high volume high performance in the context of a financial app handling millions of transactions, MySQL and PostGre do not come any close to Apache Cassandra. In fact even Oracle and MSSQL struggle to cope.
Cassandra doesn't offer the same guarantees of transactional DBs, so Cassabdra certainly is not used for high transactional workloads from my experience, it only has weak pseudo transactions. Financial apps vertically scale things like Oracle/Postgres which still get tens of thousands of tx regardless of what NoSQL hipsters say. Right tool for the workload at the end of the day.
Yep, most of clientco's clients send them data in CSV format.
But most of the baboons who write the code to produce the CSV seem to have no idea there is a CSV standard. So we have endless problems with the data (although it all helps keep me in contract!)
MySQL is owned by Oracle. Ergo MySQL will never be as good as Oracle as it will be hampered. Therefore PostgreSQL could always become better.
Also MySQL is very bloated since Oracle took over and I hate that. Went from 5MB download to over 80MB almost overnight. I guess it’s probably a gig by now.
If you talking high volume high performance in the context of a financial app handling millions of transactions, MySQL and PostGre do not come any close to Apache Cassandra. In fact even Oracle and MSSQL struggle to cope.
I haven't done much backend work in recent years (mostly mobile) but PostgreSQL is my goto choice (except for tiny projects where I might even use sqlite). I can't remember the last time I used MySQL. Possibly before Oracle bought it.
Leave a comment: