New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by R.J. Lorimer on Sep 21, 2008
Aster nCluster is built on a unique, multi-tiered nCluster architecture which consists of three separate classes of nodes: Queens, Workers, and Loaders. The three-tier design encapsulates a clean separation of roles for analytic processing. Each tier can be independently and incrementally scaled in response to the workload characteristics – adding more capacity (Workers), loading bandwidth (Loaders), or concurrency (Queens) on an as-needed basis.The MapReduce implementation provided in Aster nCluster allows for the execution of MapReduce calculations within the database, using this same architecture:
Just like its massively parallel execution environment for standard SQL queries, Aster nCluster now adds the ability to implement flexible MapReduce functions for parallel data analysis and transformation inside the database. Aster nCluster In-Database MapReduce functions are simple to write and are seamlessly integrated within SQL statements. They rely on SQL queries to manipulate the underlying data and provide input. The functions can procedurally manipulate such input data and provide outputs that can be further consumed by SQL queries or be written into tables within the database.SQL/MR is a special SQL MapReduce function library introduced by Aster that can be used to invoke map-reduce algorithms within the nCluster platform. Aster supports polymorphic functions and dynamic typing, and MapReduce calculations may be developed in languages such as Java, Python, C++ and others.
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
No comments
Watch Thread Reply