Slashdot Mirror
Keeping Google's In-house Database Ticking
An anonymous reader writes "ZDNet has a short but interesting piece on the what Google did with its 12GB database when it became a challenge for the finance department. The database was split into three, says Chris Schulze, technical program manager for Google — one for the current financial planning projections, one for the actual current data from existing HR and general ledger systems, and one storing historic information. The article says Google has been using a variety of products from Hyperion (recently bought by Oracle) to manage its internal financial systems since 2001."
12 GB? You call that big? I haven't seen an Exchange mail store that small!
Gamingmuseum.com: Give your 3D accelerator a rest.
This is the bit that gets me in the summary:
ZDNet has a short but interesting piece
Interesting to whom, precisely? Hyperion's marketing department? Scant technical details and really only notable for the link to the photos of Google's new Sydney office which are kind of interesting, I suppose, in an "ooh wow shiny...okay what's next?" kind of way.
What's so special about Google's database?
Google.
Obviously that's 12 GOOGLE-Bytes*. Which are far huger than ordinary bytes, or even gigabytes, and therefore much more interesting.
* Note that GoogleBytes are still in beta and therefore the exact amount of storage in a single GB is yet to be determined.
picpix image polls. create - share - vote. fun!
It's not tricky, you just have to be really really fast!
No no no! It stands for Googlebytes. Each Googlebyte is approximately 1024x10^10,241,024 bytes. So as you can see, a 12 Google Byte database is quite substantial...