61–70 of 101 posts
No Solr but ElasticSearch?
The reason I thought of adding ElasticSearch in the end was because some projects have started to use it as a DB on its own.
IBM Domino... :-(
Are people voting for it because they use redis as their primary data store, or just because they use it at all?
I use it redis a cache and I haven't voted for it because I assume this poll is asking about the primary data store. Does anyone use redis as their main db?
Earlier quoted context omitted.
The reason I thought of adding ElasticSearch in the end was because some projects have started to use it as a DB on its own.
ElasticSearch and Solr are both search engines built on top of Lucene. ElasticSearch just has all the hipster hype these days. Maybe update the description to include all three.
I just felt silly voting so many times. I guess I work at a big company. Our big data team is dealing with HBase and Vertica, our game team is dealing with mysql, our web team migrates a redis into couchdb, my team deals with mysqldb, neo4j, cassandra and sqlite on a test server where no one wants to set something proper up. Memcached and the file system is working on most services it makes sense on.
* Postgres (including RDS), Oracle, and MariaDB all used as transactional stores on projects of varying vintage
* Vertica for aggregate reporting
* Hadoop/HBase in another data warehouse
* Mongo in several key-value stores
* Amazon DynamoDB under evaluation for likely adoption for a newer key-value store
* memcached ubiquitous
* SQLite for simple read-only stores within web services
* Cassandra and Redis under evaluation for task queue result stores
In a large, mature organization, I think this kind of heterogeneity is both inevitable and appropriate.
IBM Domino... :-(
I worked on Domino--it's a mail server that uses DB2.
A word of opinionated advice to anyone deciding on a database to use for their new project: Just go with something popular (MySQL, Postgres, Mongo, etc.), or go with an Amazon hosted cloud database if you really don't want to set anything up (RDS, SimpleDB, DynamoDB). There's no good reason to start a project with other databases. If you're worried about the scalability of something like MySQL when you haven't even g…
Three reasons: 1) your data is probably relational, even if you think it's not, 2) if you have non-relational records, Postgres has JSON and hash storage types that perform better than most NoSQL databases, and 3) The architecture, standards compliance, and sheer capabilities of Postgres are all best in class. Seriously, if you want to read some good C, peruse the PostgreSQL source. Go Bears.
Unless you're trying to do some analytics (in which case, find a column store), or want to use it and forget it (Amazon's database services; and RDS is Postgres), Postgres is the way to go.