Akiban Use Cases - Social Context

Social context means a richer behavioral context for users - more engaging with dynamic views of changing data, more user participation and instant gratification. What’s trending today? Who do I know that's online? Where's the vote I just cast? Servicing this social context means manipulating sets of aggregated results, often in real-time over relational, transactional data. It requires significant CPU and memory resources. As data gets big and user volume increases, competition for these finite resources quickly bottlenecks relational databases:

SELECT      order_id
            ,Sum(i.unit_price * i.quantity)
             AS order_total
FROM        Customer c
INNER JOIN  Addresses a
       ON   c.customer_id = a.customer_id
INNER JOIN  Orders o
       ON   c.customer_id = o.cusotmer_id
INNER JOIN  LineItems i
       ON   o.order_id = i.order_id
WHERE       c.payment_status = 'paid'
      AND   a.address_type='4'
GROUP BY    order_id		 Columns define data elements required by the application
 
 
Tables are joined to assemble the object.
 
 
Predicates (filters) are applied.
 
Results are aggregated.

 

Akiban versus Traditional Relational Systems

As traditional relational systems process the 3 joins in this query, they create a temporary table that needs to be sorted and then scanned for distinct values before the results can be projected. This is a slow process, especially under heavy concurrency conditions: 

AkibanVsMySQLExplainPlan_GroupByAnnotated.png

Akiban Server eliminates the expensive join, sort and scanning operations. Instead, Akiban Server simply probes a single ordered group index and then sequentially reads from its table-group, which is a blisteringly fast operation by comparison.

Business Value In Context

More dynamic and engaging content

More competitive features

Higher page views, conversions and retention

Focus IT on growing the business

Better, more consistent hardware utilization

Akiban table grouping brings game changing query acceleration and scalability to SQL queries. By decreasing your customers’ time to interaction, and in providing them valuable real-time context, your business yields significant benefits. The graph reflects it. In this example, MySQL executed the query in 3.3 seconds. Akiban Server was able to execute the same query in 30 milliseconds. An acceleration of 100x!