3 ms·
Their methodology is here: https://db-engines.com/en/ranking_definition https://db-engines.com/en/ranking_definition A lot of it is highly suspect in my opinio
by hn_throwaway_99 3y ago
Their methodology is here: https://db-engines.com/en/ranking_definition https://db-engines.com/en/ranking_definition
A lot of it is highly suspect in my opinion. First off, they don't specifically say how they consider Postgres for some of their factors. E.g. in their "Mentions on system websites" section they say
> In order to count only relevant results, we are searching for <system name> together with the term database, e.g. "Oracle" and "database".
But I'd expect Postgres mentions to be split a lot between "Postgres" and "Postgresql", and it's not clear they included both terms.
More importantly, the vast majority of these factors are trailing indicators. Even if no same person would use Oracle for a new installation, their existing giant (and very difficult to migrate) install base means you'll see tons of Oracle mentions in LinkedIn profiles and job reqs for decades.
- hyperman1 3y agoAs someone who has worked with Oracle, mssql and postgres: If it gets complex I tend to use a search engine for oracle or mssql, for postgres I go straight to their official docs. Postgres documentation quality is very good and honest. Also, the number of postgres weird edge cases and ad hoc hacks in SQL feels lower. If my experience generalizes, this ranking will score you higher the more support you need. Well working software generates less noise and is measured as less popular as a result.