My last post focused on the ScaleBase Use Cases we saw during our beta phase. In this post I’d like to detail additional popular use cases that we’ve seen.
Although categorized as “social networks”, social network applications are actually a set of independent applications that have strong integration between them. Each application has different needs. Friend suggestions require traversing the social graph – a very complex query to execute.
Wall applications, and status applications, usually have massive write operations (depending, of course, on the number of users who use them). Some of those status updates are rarely viewed. Some are viewed by many users. Latency is critical, but data consistency is usually a strong requirement as well, since many sites connect status updates to ad displays.
Social Network customers use ScaleBase to improve their write latency (reads are executed from a caching layer), and scale the database to support hundreds, thousands, or tens of thousands of write operations per second.
Magento is a very popular e-commerce platform. An open source technology, it’s being used by sites such as Oakley, Nokia, Lenovo and many more. Many face database scaling issues when their online stores get more popular – and this is where ScaleBase fits in.
Customers report major performance improvements when using Magento with ScaleBase under heavy load – and of course, unlimited scalability.
In this category I’m including quite a few solutions that monitor web sites – for security, performance, governance etc. These solutions typically deal with massive write ratios (sometimes even higher than 50% – meaning some data is never read), sometimes online and sometimes batch, usually at bursts. It’s incredibly difficult to support these massive write operations without a sharding solution – so ScaleBase was a perfect fit for quite a few customers who can now run their business without worrying about scale.