Database sharding, used by Facebook, Tumblr and Mozilla, is an incredibly powerful way to ensure MySQL systems scale-out and drive consistent, fast app performance to handle more users, more data, and more workloads.

Nowadays sharding can be automated, but how do you choose the right sharding rules to ensure optimal MySQL scalability and performance for your applications?

In this TechTalk webinar, Doron Levari CTO at ScaleBase, discusses how to:

- Determine if sharding is right for your organization
- Choose the best sharding policy for your applications
- Avoid sharding policy lock-in and data silos

Learn from ScaleBase’s experience automating the MySQL sharding process.

Register today and  how to cost-effectively scale growing MySQL databases without disrupting your existing infrastructure.

Growth comes with success and we love to see it — and as your business expands, so does your database, increasing both concurrent connections and transactions. In previous blog entries, we’ve discussed a few MySQL database scaling strategies and how database sharding solves scalability issues, and how easy it is with ScaleBase automation.

One Server or Many?

With database sharding, the individual shards — a.k.a horizontal partitions of data — are typically created with the vision of being placed on multiple machines for massive parallelization of data processing and storage. But, there are also valuable benefits from running a sharded database where all shards are on a single server.

Read More

Let’s say you’ve recently moved your application to the cloud. You’re probably thrilled to no longer worry about hardware upgrades, maintenance, or backups. In fact, having your data in the cloud can (and should) make your life easier.

But with a flourishing company, your database will likely grow rapidly with more users and more transactions. Can your cloud service provider meet the demand? Will your database scale?

Read More

So, your application is growing, you’re serving more data, more users, and more transactions — congratulations, you must be doing something right! With this increase in information, however, can your MySQL database scale to handle it all? If not, how can you scale out your MySQL database?

There are several MySQL scalability approaches you might investigate including; read/write splitting, clustering, and putting your database on bigger hardware. Each of these approaches can be helpful, but we believe the ultimate scalability benefits come from deploying a technique called database sharding. Read More

There are many popular websites that are powered by MySQL — including Facebook, Twitter and Zynga — the best evidence that large applications with millions of users can be built and scale well with MySQL. MySQL provides a Thread Pool in its Enterprise Edition which is sometimes mistakenly touted as one of the prime tools for better performance and scalability. Although the thread pool is able to reduce overhead in managing client connections and statement execution threads; it will not improve performance and scalability of an overloaded MySQL instance.

Scalability is NOT in a Thread Pool

Fact is, MySQL thread pools do little for scalability. With thread pools, your database continues to stay alive even in times of excessive load but they alone do nothing to increase the actual data throughput when your business applications demand it. Read More

ScaleBase is a silver sponsor of the Percona Live MySQL Conference & Expo at the Santa Clara Convention Center. ScaleBase will be exhibiting at booth #102.

MySQL is the world’s most popular open-source database, powering web-scale applications such as Facebook, YouTube, and Twitter. MySQL continues to evolve rapidly, reaching more markets and powering more applications every day. Read More

Database sharding, used by Facebook, Tumblr and Mozilla, is an incredibly powerful way to ensure MySQL systems scale-out and drive consistent, fast app performance to handle more users, more data, and more workloads. But home-grown sharding is hard, full of caveats, and very often ends up as non-cost effective.

ScaleBase provides an easy to use platform to scale-out MySQL databases. It gives all the benefits of MySQL sharding, while eliminating the biggest challenges associated with sharding.

In this TechTalk webinar, Doron Levari CTO at ScaleBase, explains:
- MySQL scale-out without embedding code and re-writing apps
- Successful sharding on Amazon and private clouds
- Single vs. multiple shards per server
- Eliminating data silos
- Creating a redundant, fault tolerant architecture with no single-point-of-failure
- Re-balancing and splitting shards

Register today and learn how to cost-effectively scale MySQL to handle an infinite number of users, with no disruption to the existing infrastructure.

With MySQL 5.5 deployed all over the world, many MySQL administrators have anxiously awaited the recent release of 5.6. Since Oracle released version 5.6, many of us are wondering not only about the much-touted scalability benefits, but the limitations as well. This article will discuss the benefits and how to overcome the limitations to ensure your database is ready to grow with your business.

Scalability Enhancements

MySQL 5.6 has three new scalability enhancements:

1. Partitioning Enhancements
There are two partitioning enhancements in version 5.6 including explicit partition selection and the ability to import and export partitioned tables. Read More

If you ask database developers from Facebook, Tumblr or Mozilla for an effective way to drive more consistent and faster app performance, they might all reply in unison, “scale out your MySQL database”. Each company has effectively scaled out their MySQL systems by using home-grown sharding to handle more users, more data, and more workloads. We’ll discuss the pros and cons of home-grown MySQL scale out versus platform-based MySQL scale out in an upcoming post.

But, how do you determine if you’re pushing the boundaries of MySQL’s scalability limits?

Gathering Data

To calculate if your existing infrastructure can benefit from a MySQL scale out solution, you need to gather some data and make some predictions. Specifically, you would gather the following MySQL systems environment data points: Read More

One of the main responsibilities of any database administrator is to keep a close eye on how database performance is impacting size and storage. Decisions will have to be made on whether or not to make changes within the database structure or application itself, or to make the changes on the storage and resource side instead.

Here are two key indicators that your MySQL Database is getting too large: Read More