Trends....

Damien Clochard <[email protected]>
Newsgroups gmane.comp.db.postgresql.advocacy
Organization Dalibo
Message-ID <[email protected]>
Hey guys,

The most difficult question I get when I'm on a PostgreSQL booth is 
"What is PostgreSQL's market share ?". I often espond with questions : 
"How do you measure that ?", "What does "market share" even mean for an 
Open Source project ?", etc. etc.

These are interesting discussions but that's not what people want to 
hear. They want numbers and so far we don't have that many statistics to 
provide:

There's the DB Engines Ranking, which has already been discussed here a 
lot :

http://db-engines.com/en/ranking

There's also the Google Search Trends :

https://www.google.com/trends/explore?q=Postgres%2BPostgreSQL%2Bpgsql,%2Fm%2F01vw9z,%2Fm%2F04y3k,SQL%20Server&hl=fr&sni=1

Both of them evaluate the state of the competition "as of today" but 
it's also interesting to look at the problem in term of progression and 
growth.

Yesterday I found a nice stats here :

https://blog.whoishiring.io/hacker-news-who-is-hiring-thread-part-3/#storage


This is a stat based on the jobs offers published on the monthly "Who is 
Hiring" threads of Hacker News. These jobs are mainly offered by 
startups in USA so that's only a subset of the entire IT Industry. But 
that's probably the most dynamic and leading subpart. In French we say 
"avant-garde" :)

Anyway this trend is not suprising in itself but it's a nice 
illustration of the difference between "current position" and 
"velocity". Instead of answering where PostgreSQL is right now it's more 
interesting to answer with where PostgreSQL will be in the near future.


-- 
--
Damien Clochard


-- 
Sent via pgsql-advocacy mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-advocacy
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.