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 Ian Roughley on Aug 12, 2008
Unveiled at the O'Reilly Open Source Convention (OSCON) by Brian Aker (MySQL Director of Architecture), Drizzle can be described as a "what if" project for creating a database specifically tuned for a particular subset of applications.
Brian outlines this best in his blog:
The goal right now is to target a certain class of applications/developers and see if this is useful. As an example:
What are the bigger differences in philosophies?
- Web based apps.
- Cloud components.
- Databases without business logic (aka stored procedures).
- Multi-Core architecture.
Adopt external libraries, use open source mechanics for contributions, keep to an open style of communication, and remove the line between internal and external development. Essentially do what I have been referring to as "Organic Open Source". We have focused on C99, POSIX and autotools based systems. We have taken to a very micro-kernel design where code is being removed from the center and pushed out to the edges via interfaces. We are taking a Linux/Apache tightly coupled design for modules.
More formally, Drizzles features are:
Currently Drizzle is in alpha (with major new changes being introduced daily), with no stable release or binary release. For more information, or to download and experiment, visit the Drizzle website.
Getting Started with Stratos - an Open Source Cloud Platform
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Some more thoughts on Drizzle here:
zwadia.com/?p=26
Cheers,
Zubin Wadia
CTO
www.imagework.com
"Business Acceleration through Process Automation."
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.
1 comment
Watch Thread Reply