m
Our Mission Statement
This is Photoshop's version of Loremer Ipsn gravida nibh vel velit auctoregorie sam alquet.Aenean sollicitudin, lorem quis bibendum auci elit consequat ipsutis sem nibh id elit.
Follow Us
Top
Fast Data Recipe: Integrate Streaming Aggregations and Transactions - VoltDB
8146
post-template-default,single,single-post,postid-8146,single-format-standard,mkd-core-1.0,highrise-ver-1.0,,mkd-smooth-page-transitions,mkd-ajax,mkd-grid-1300,mkd-blog-installed,mkd-header-standard,mkd-sticky-header-on-scroll-up,mkd-default-mobile-header,mkd-sticky-up-mobile-header,mkd-dropdown-slide-from-bottom,mkd-dark-header,mkd-header-style-on-scroll,mkd-full-width-wide-menu,mkd-header-standard-in-grid-shadow-disable,mkd-search-dropdown,mkd-side-menu-slide-from-right,wpb-js-composer js-comp-ver-5.4.4,vc_responsive
VoltDB / Fast Data  / Fast Data Recipe: Integrate Streaming Aggregations and Transactions

Blog

Fast Data Recipe: Integrate Streaming Aggregations and Transactions

In the VoltDB ebook, “Fast Data: Smart and at Scale,” Ryan Betts and I outline what we have found, through years of work and collective experience, to be tried-and-true design patterns and recipes for fast data.

High-speed transactional applications or operational applications that process a stream of incoming events are being built for use cases including real-time authorization, billing, usage, operational tuning, and intelligent alerting. Writing these applications requires combining streaming analytics with transaction processing on live data feeds.

Transactions in these applications require real-time analytics as input. Recalculating analytics from base data for each event in a high-velocity feed is impractical. To scale, it’s much more effective to maintain streaming aggregations that can be read cheaply in the transaction path. Unlike periodic batch operations, streaming aggregations maintain the consistent, up-to-date, and accurate analytics needed in the transaction path.

This pattern trades ad-hoc analytics capability for high-speed access to analytic outputs that an application needs. This trade-off is necessary when calculating an analytic result from base data for each transaction is infeasible.

For more on streaming aggregations and transactions, and additional, specific design patterns, download the eBook: “Fast Data: Smart and at Scale”.