• Contact Us
  • Support
  • Questions? Contact Us Today: 617.630.2800
  • Follow us on Twitter
  • Join our Facebook Group
  • Find us on LinkedIn
  • Subscribe to our RSS Feed
  • Search Site

  • Solutions
    • By Use Case
    • By Industry
    • By Delivery Model
  • Product
    • Product Architecture
    • Scale Out via Data Distribution
    • Scale Out via Read/Write Splitting
    • Admin & High Availability
    • Key Features / Benefits
    • Easing Capacity Planning
    • What is Database Sharding?
  • Resources
    • Datasheets
    • Case Studies
    • Whitepapers
    • Webinars
    • Videos
    • Scale Out Readiness Calculator
    • Database Assessment
    • Benchmark
    • Frequently Asked Questions
    • Documentation
  • Blogs
    • ScaleBase Blog
    • CTO Blog
  • Company
    • Customers
    • Management
    • News
      • Press Releases
      • Coverage
      • Events
    • Partners
    • Investors
    • Careers
    • Contact Us

You are here: ScaleBase / News / Coverage / Forbes: Outrunning The Tidal Wave: How Dangerous Is Big Data?

Forbes: Outrunning The Tidal Wave: How Dangerous Is Big Data?

13 Dec 2012 / 0 Comments / in Coverage/by Paul Campaniello

Apple did it. Amazon did. So did Pinterest.

In the past six months, all three sites went down – at the wrong time – because their databases couldn’t keep up with consumer demand. In every case, unplanned peaks in user traffic pounded the site, and brought performance to a screeching halt.

In this new world of immediate experience and gratification, the database is rapidly becoming the company. Consider Amazon and Pinterest: There’s no storefront, no customer service – they live and die based on each user’s experience. More than ever, that experience is backed every step of the way by data, which means that the dark corners of data performance risk are becoming a bet-the-company vulnerability.

If your data isn’t killing your database today, it will. Maybe next month; maybe next year.

To add a little perspective, one of the largest wireless providers in the UK – O2 – is currently spending close to $20 million in an effort to replace its database following two recent outages that impacted millions of customers. Derek McManus, COO of O2 UK wrote in a blog post that the company is, “…extremely disappointed to have let our customers down again.” He adds that O2 UK is “…not prepared to risk this happening to our customers for a third time and are implementing a proven alternative solution.”

On the flip side, you can get ahead of this chase for big data. It may mean rethinking how big databases are built for growth, because the underlying assumptions of predictable behavior are obsolete.

For just about every company, managing and exploiting the potential of ‘big data’ will be the #1 business opportunity before 2013 is out. Even if your database doesn’t seem like an under-performing asset today, it could easily become one within two or three quarters.

The biggest issue is performance – and staying ahead of the tidal wave of transactions. That’s especially challenging when the ‘conventional wisdom’ about big data points to the importance of analysis. Indeed, it’s the analysis that can be mined for sentiment, patterns, and, once you can decode it, predictability, new opportunities and money.

But it’s the transactions that underlie this intelligence. And it was the breathtaking volume of transactions that caused Amazon, Pinterest and Apple to go dark. Simply too much unexpected activity, likes, posts and uploads. And that – like it or not – is the future of big data. Peaks. Valleys. And not always when you expect them.

Avoiding this mineshaft is, surprisingly, possible. It’s not expensive, either. But it does mean toppling a few sacred cows.

For example, companies like Mozilla – which recently launched an online app store – are putting database scalability and performance systems and solutions in place before they build or launch new apps – in order to guarantee the company will be able to support its anticipated transaction volumes. 

Size matters. But not the way you think.

To read the rest of the article, click here.

 

 

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Subscribe to Blog


 

Tweet
database assessment
Popular
  • MemoryImageSeptember 6, 2011, 10:33 am
  • Backing Up MySQL With ScaleBaseSeptember 12, 2011, 8:34 am
  • Running TPC-C on MySQL/RDSJune 15, 2011, 8:45 pm
  • Can Prepared Statements Improve Your Scalability?May 23, 2011, 5:57 pm
Recent
  • Optimizing Sharding Policies to Scale Out MySQL – Part...June 13, 2013, 4:20 pm
  • TechTalk Webinar: Optimizing MySQL Shards – From Vision...June 5, 2013, 2:07 pm
  • ScaleBase Survey Finds That 59% of MySQL Users Have a Scalability...June 4, 2013, 7:27 am
  • ScaleBase presents a webinar on how to scale out MySQL on...May 29, 2013, 3:18 pm
Comments
  • [...] business model, and a strong executive. Scalebase,...February 4, 1:49 am by The Investing Edge of Enterprise IT
  • [...] Recently some customers running on Amazon EC2 asked...December 28, 3:27 pm by High Availability for your ScaleBase instance | MySQL | Syngu
  • [...] ScaleBase Releases Database TPC-C Performance Results...December 12, 2:29 pm by ScaleBase achieves 180K NO-TPM TPCC results on... | MySQL | Syngu
  • Hi Milo - I totally agree. You need to understand how you're...September 6, 10:33 am by liran
Tags
Amazon RDS application re-write Big Data Funding cloud sharding Database Availability database capacity database cloud database scalability database scalability strategy database sharding database virtualization data distribution data traffic manager Elastic Load Balancing Hadoop high availability Industry News MySQL MySQL 5.6 MySQL Clustering MySQL Scalability MySQL Scalability Issues MySQL scale out MySQL Sharding MySQL Tuning NewSQL next gen apps NOSQL scalability of databases Sharding single point of failure thread pool

Recent Comments

  • The Investing Edge of Enterprise IT on Management
  • High Availability for your ScaleBase instance | MySQL | Syngu on High Availability for your ScaleBase instance

Solutions

  • Solutions
    • Centralized Database Management & Visibility
    • Scalability
    • Database Availability
    • Delivery Models
    • Industry Solutions

Products

  • Product Overview
    • Product Architecture
    • Scale Out via Data Distribution
    • Scale Out via Read/Write Splitting
    • Data Traffic Management
    • Availability
    • Key Features / Benefits
    • Easing Capacity Planning
    • Database Sharding

Resources

  • Datasheets
  • Case Studies
  • Whitepapers
  • Webinars
  • Videos
  • Scale Out Readiness Calculator
  • Benchmark
  • Frequently Asked Questions
  • Documentation
  • Database Assessment

Company

  • Company
    • Customers
    • Management
    • News
    • Partners
    • Investors
    • Careers
© 2012 Scalebase Inc.

  • |Home
  • |Sitemap
  • |Privacy Policy
  • |Contact Us
  • |Blog