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.
How would you like to view the presentation?
I watched carefully the presentation here, but I think the most interesting part came at the end, but unfortunately I still don't get it: the presentation focused on navigating an object graph and creating objects/entities. What I didn't get is how was the core capability of the service being invoked - the "rate operation" talked about at the end. Does one "create" an empty rating, somehow links it with the customer and then does again a GET to see what the rating is? How do I tell the system "please rate it for me now" (or is this a "side-effect" of create/read/update of a resource)?
Another thing I was wondering about is how the initially mentioned problems were actually solved with the new solution - what happened to the MDA approach, how easy/difficult was it for the B2B consumers to use the new service, versioning etc.
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