3 ms·

An interview with the director responsible for the system, props to @kalleboo for finding this: http://fcw.com/Articles/2014/10/20/State-Department-database-cr

An interview with the director responsible for the system, props to @kalleboo for finding this: http://fcw.com/Articles/2014/10/20/State-Department-database-crash-1.aspx?Page=all&p=1 http://fcw.com/Articles/2014/10/20/State-Department-database... Typical quote: "We knew we could run it on one node. We needed to have one very powerful node."

BinaryIdiot 11y ago
> Typical quote: "We knew we could run it on one node. We needed to have one very powerful node." As someone who has done government contracting...it's always alarming when this path is suggested. The last time was a beefy server with about 50TB of ram to keep all data in memory with multiple hard drives to keep backups. Ugh.
- codecamper 11y ago
  The WOPR? How about a nice game of chess?
- crdb 11y ago
  Mind talking more about what the challenges in running a 50TB relational database? I and I'm sure many others would be very interested in a blog post or long-ish comment with anecdotes and lessons learnt...
  - BinaryIdiot 11y ago
    > Mind talking more about what the challenges in running a 50TB relational database? I wish I could but it wasn't my direct project so I wasn't part of the team implementing it. I'm not even sure it was successfully delivered.
marcosdumay 11y ago
One of the problems with proprietary databases is that licensing issues are another barrier to creating proper clusters (and to have equal environments on development, testing and production).