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.
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 1 year ago.
Improve this question
both innodb_buffer_pool and redis they are all suppert memery. and they are all support LRU. so why should i use both redis and mysql at same time?, what's the point of using redis in my case.
my application is coding use golang(game server). It provides http api. but applications are becoming more complex. it has 100 sql query per request (20% insert/update, 80% select).because the game hasn't been released yet so
the data set is small, about 400000 rows, stress testing in progress,i want to improving it. i increased innodb_buffer_pool_size,the performance improved but it didn't meet my expectations. so i want using redis.
thanks for you answer
If the data is changing, the buffer_pool can give you up-to-the-second data; no external caching mechanism can.
It is usually folly to have a cache in front of another cache.
How big is the dataset? What do the queries look like? (That is, please provide more info so we can come closer to answering your question.)
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 4 years ago.
Improve this question
i work on a project with node.js and a mysql database.
i have a connection between them with the npm modul mysql.
Now my question:
is it better to send a SQL command and sort the data in node.js or multiple detailed sql commands?
what is faster / more performant?
Thanks.
Without knowing the exact SQL queries, I would say that database operations are faster compared to your own implementation. Many smart people have worked to assure performance, accuracy, atomicity, concurrency etc. of the Mysql engine.
Even if you can gain marginal improvements in some aspect with your own code, it is unlikely that you will be able to justify the investment.
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 5 years ago.
Improve this question
I am curios why some prefer MYSQL over SQLITE, i am interested on learning MYSQL
SQLite is an embedded library, it requires no server process, and everything it saves is contained within a single, portable file. MySQL is an RDBMS server that's a lot more work to set up, but is multi-user, more scalable, and far more featured.
For example, SQLite is used for mobile applications as well as "development" instances of code where it's only lightly loaded. It can be used at scale but generally isn't, its simple design has limitations.
If you're writing a mobile application and need a local database, SQLite is not a bad call. Spinning up a huge, cumbersome MySQL process to do the same thing on a mobile device is a bad plan.
Although they're both "SQL databases" and have a lot of functional overlap, they're engineered to solve some very different problems. In some trivial use cases it might be an arbitrary choice as to which is best, but in most cases it's pretty obvious which of the two you need.
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
In absolute terms, Postgres has more features and has been used at scale by Instagram, etc. while MySQL has a much bigger user base and has been used at scale by likes of Facebook, Quora, etc. But how about in combination with NodeJS?
Which is more popular with NodeJS?
MySQL is probably more popular, solely in terms of userbase. (You sorta answered this yourself)
MySQL probably has more examples around the net which could help make things easier to set up. You'll probably also find MySQL more likely to come preloaded on a VPS if that's the sort of route you're taking. However setting up PostgreSQL on your server is not difficult, and there is plenty of documentation available.
It really depends on what your intentions are with your data. Digital Ocean wrote a nice concise comparison of MySQL and PostgreSQL found here
As far as how these play with node.js, in my experience the node modules for PostgreSQL and MySQL are equally pleasant to work with. Ultimately its more about picking the database that suits your data and what you want to do with your data. Then deciding how it fits into your node stack.
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