3 ms·

I don't have the best knowledge on DBs, but why would you use more than one of the same "tech"/paradigm? Why postgreSQL and MySQL? Don't they work similarly? Or

I don't have the best knowledge on DBs, but why would you use more than one of the same "tech"/paradigm? Why postgreSQL and MySQL? Don't they work similarly? Or is it because you use postgreSQL for the things it is better than MySQL, and vice-versa?

martinp 14y ago
In my experience the database usually gets evaluated on a per-project basis. It's a good way to determine the strengths and weaknesses of each. Currently we use PostgreSQL for all new projects, but we have a few legacy projects still using MySQL that we haven't bothered migrating. Additionally, most developers find it a hassle if they have to configure a fullblown database just to do development on a given project. That's why we use H2 (in-memory database) for development.