Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I want to create a new rails application and I'm not sure whether to use MySQL or Postgres. Which one is best and what is the difference between them?
UPDATE:
The project is a health-care project. It may contain more than 500 tables.
postgres is secure, fast, and full of features but comparatively tricky to use.
MySql has its own benefits along with large user community and vast materials. Immensely helpful if you ever get stuck.
But ultimately it all comes to your preference and framework (apart from rails if your app requires any) support.
Read this for detailed comparison and insights: http://wiki.postgresql.org/wiki/Why_PostgreSQL_Instead_of_MySQL%3a_Comparing_Reliability_and_Speed_in_2007
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I understand that Chisel is a HDL/HCL language to overcome some of Verilog/SystemVerilog restrictions by using higher abstraction level.
And it is open source as well.
It might be a bit naive and presumptuous, but still I would like to ask.
My question is that why do so many similar efforts are working in parallel, e.g. Blusspec, spinalHDL, Pyha etc?
I mean, is there any reason why the development community may not choose one of these and concentrate efforts on stabilizing or enhancing one of these.
That's exactly what is happening now, it just takes a while to choose.
Although the past does not show that the best technology wins, let us hope it does this time.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I was reading an article about facebook timeline https://www.facebook.com/note.php?note_id=10150468255628920
I always thought this kind of core produces would prefer Cassandra. However it is using MySQL/InnoDB.
Could anyone briefly explain why?
Available internal / external expertise with MySQL (it's easier to google solutions for existing problems)
Cassandra is much harder to reason about due to eventual consistency and limited transaction support
Moving to a new datastore is a lot of pain and it doesn't seem to be justified
You can check out the slides below for their usecases:
MySQL at Facebook
Scale at Facebook
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I have made a website which does some calculations, so there is no user registration. Just a website where people can do their calculations and leave. However, do I need MySQL as part of the server? I am a bit confused on this.
MySQL (and other database engines like PostgresQL, MongoDB, and even Google's BigTable) are used for storing data outside of user sessions. If you have no need to persist data, then you have no need for a database.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I have two problems with MySQL and started wondering if I should switch to Postgres
1 - Incremental backups are only available on the paid version of MySQL.
2 - It seems that mySQL has performance issues in some cases
So, are these two problems solved with Postgres?
I guess that PostgreSQL's continuous archiving can be considered a valid alternative
for every dbms you can find plenty anecdotal evidence of situations they cannot handle properly/quickly, or only with massive help in the form of cunning query rewrites, data remodelling and whatnot. Just look around here on SO or on any of the thousands of db-centered sites all over the net to see what I mean.
In short, where 1 can be a solid argument to justify a switch (and especially from a business point of view), I wouldn't be overly concerned about 2. And if your db is slow because your datamodel is not performance friendly, you'll just carry over slowness.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
Including...how to set up the partition, how to determine which partition to talk to...etc.
I know replication but am new to partitioning.
Improving Database Performance with Partitioning
http://dev.mysql.com/tech-resources/articles/partitioning.html
This would be a good start: MySQL Partitioning Overview
Also, I haven't watched this one specifically, but the presentations by the Pythian group are usually pretty good. Reading a manual may be more efficient, but as an alternative this video will teach you quite a bit about partitioning in MySQL.
Partitioning in MySQL 5.1