361–370 of 378 posts
Earlier quoted context omitted.
Can you make a blog post about the issues instead? It would greatly benefit everyone.
I'd love to, but there are things politically complicated about all this in the very small startup world. So maybe one day, but I can't do it right now.
Oh, and PostgreSQL for reporting.
Earlier quoted context omitted.
I'm probably starting to sound like a broken record around here, but: 1. I build products on Oracle at a startup. 2. Oracle has many compelling features that really don't have first-class open source alternatives: OLAP, encryption (wire and at-rest), VPD, materialized views with query rewriting, object and document storage, monitoring and tracing, among others... 3. Oracle got more compelling since being offered--lic…
It is perplexing that Microsoft (presumably SQL-Server) has got so many votes. In my experience, absolutely nobody chooses to use it. They just have aggressive sales people who use it as a bargaining chip to elbow out Oracle and help win other business.
Sybase was better than Oracle, and Postgres was just as good as Sybase at that time. But SQL Server (version 2005 on) has stood taller than all of them in my view. Excellent management tools, stable, reliable and no performance issues for our apps. Most of our apps are write light and read heavy with thousands of users hitting the db - served off one Win 2003 server (we have a warm spare).
So there is some truth to your statement about nobody choosing to use it - for us the primary motivation to not use it internally was cost. At our customer premises they picked up the tab. We have MSDN so sql server development licenses are not an issue. Have not met a Microsoft salesperson yet!
Earlier quoted context omitted.
TBH, we didn't seriously pursue Cassandra when we considered distributed database systems b/c the vast majority of "back-reference checks" we did on the YC network and other area startups was "stay away." We got some very frank advice from some people whose opinions on databases I take very seriously to stay away, including reports from within FB. Having said that, I cannot claim to have firsthand proven or disproven…
Quora's decisions to not use Cassandra and Adam's answer regarding it lead me to the same conclusion ( http://www.quora.com/Quora-Infrastructure/Why-does-Quora-use... ). Evidently few from Facebook are advocating it.
At large loads and footprints, imvho, Riak, Cassandra and HBase present viable options. But there are some factors to consider that don't seem to get mentioned in the pop tech press
- What are you able to operate in production?
- What are you able/willing to debug and patch?
- What hardware options do you have?
- What are your workloads?
- Which variable of C.A.P, when you lose it, most damages your business?
- Will your company's choices be evaluated in the press?
- Does your board/investors have capital tied up in business's that are using something else?
- What architecture tradeoffs and styles sit well with you?
- What kind of data access and consumption patterns make you money?
- Can you pay for help?
The right choice is context sensitive, and I'm fairly sure for this class of systems at this point in time, there's no free lunch. That means you have to do the legwork for yourself and make your own choices and commitments; doing what you heard worked for someone else is a cargo cult.
Earlier quoted context omitted.
Hear hear! Mongo but no Riak? Come on.
Riak isn't in the same ballpark as MongoDB. They are closer to Hadoop.
Based on merits, architecture, and implementation Riak handily beats several of the DBs listed. It's a glaring omission and not the only one. As many chose Other as did Oracle.
SQLite all over the place – it's great having a super portable DB format for quick little hits. There's nothing quite like sending a DB as an email attachment.
SQLite is so pervasive that I'm pretty sure everyone uses it at some point. It's in client applications, it's used by yum (the package manager found on CentOS/RHEL/Scientific Linux systems), it's part of many web applications, it's part of many spam filtering systems, it's part of Android (maybe iOS, too?), it's basically impossible to avoid it if you're a nerd. Also, it's awesome.
Earlier quoted context omitted.
Quora's decisions to not use Cassandra and Adam's answer regarding it lead me to the same conclusion ( http://www.quora.com/Quora-Infrastructure/Why-does-Quora-use... ). Evidently few from Facebook are advocating it.
Quora on MySQL failed outright when AWS EBS failed, companies on AWS using Cassandra like SimpleGeo and NetFlix did not. To their credit, Facebook were clear enough on their reasons for using HBase over MySQL and Cassandra, such as wanting to double down on their current Hadoop system/knowledge and having easily obtainable ordering guarantees on messages. It's also clear they've invested in making HBase good enough.…