January 20, 2008

More Google reliability woes

Google’s reliability issues are ever worse. As I previously pointed out, this is evidence against the notion that MapReduce is a replacement for established DBMS.

Please subscribe to our feed!

Share: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • del.icio.us
  • Digg
  • DZone
  • Mixx
  • Reddit
  • Slashdot
  • Sphinn
  • StumbleUpon
  • Technorati
Categories: Google and MapReduce 
Subscribe to our complete feed!

Comments

2 Responses to “More Google reliability woes”

  1. Daniel Weinreb on January 21st, 2008 11:31 am

    All you seem to be citing here is one anecdotal report that Google Analytics was slow at some particular time. Unless there’s other evidence that you didn’t allude to here, I think it’s premature to attribute any problem to MapReduce.

  2. Curt Monash on January 21st, 2008 5:10 pm

    Dan,

    As per a prior post (linked above), there are LOTS of problems with Google Analytics.

    Now, it’s a big problem, and glitches are understandable. But it’s not ringing evidence for the theory that MapReduce is a substitute for a real data warehouse.

    What’s more, the point is probably moot. I’d guess strongly that MapReduce is being used to FEED a more conventional data warehouse.

    CAM

Leave a Reply




Feed including blog about database management, data warehousing, and business intelligence Subscribe to the Monash Research feed via RSS or email:

Login

Search our blogs and white papers

Monash Research blogs

User consulting

Building a short list? Refining your strategic plan? We can help.

Vendor advisory

We tell vendors what's happening -- and, more important, what they should do about it.

Recent white paper

Pervasive PSQL Summit v10 Highlights

September, 2007

Recent webcast

What leading database vendors don't want you to know

Originally broadcast April 9, 2008

Monash Research highlights

Learn about white papers, webcasts, and blog highlights, by RSS or email.