• 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!

MySQL or PostgreSQL for high-volume high-performance database?

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    #21
    DB2

    Comment


      #22
      CSV

      Comment


        #23
        Asynchronous punched card.

        Comment


          #24
          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.
          See You Next Tuesday

          Comment


            #25
            Originally posted by NickFitz View Post
            CSV
            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!)
            Work in the public sector? Read the IR35 FAQ here

            Comment


              #26
              Originally posted by BR14 View Post
              DB2
              high-volume high-performance database.

              Comment


                #27
                Originally posted by fullyautomatix View Post
                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.

                Comment


                  #28
                  Originally posted by OwlHoot View Post
                  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.

                  Comment


                    #29
                    SQL Server 2016. Yes, really.

                    qh
                    He had a negative bluety on a quackhandle and was quadraspazzed on a lifeglug.

                    I look forward to your all knowing and likely sarcastic and unhelpful reply.

                    Comment


                      #30
                      Call me crude but unless you have less than no money or are working on some kind of massive data real time thing it's probably not going not matter.

                      Comment

                      Working...
                      X