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 Stefan Tilkov on Jan 29, 2008
Not a big deal, but my posse and I aren't able to watch this video at work. If you threw it on youtube we'd be able to.
Jeremy
FireFox cannot connect, but controls are there. IE can play, but no controls.
We hear you loud and clear. A better solution for video streaming is coming to InfoQ Real. Soon. Now. Promised.
works fine in epiphany
great presentation btw :)
Great presentation, very thoughtful.
I have a question though. I'm trying to think through one of the advantages I think you can get with an ESB architecture. If all messages go via an ESB then features such as security, logging, routing, transformations can be:
1. Managed centrally .. so no need for individual services to implement these features.
2. New features, and updates to old features, can be managed seperately from the services themselves.
This strikes me as positive things becuase it means that different aspects of services can be managed/deployed/changed seperately.
Maybe the features I'm talking about are just technical services? You very, very briefly touched upon technical services in your presentation.
Any thoughts? Or should I just buy the book?
Great presentation, very charismatic guy.
Though I'm a bit worried that he goes over the technical issues with SOAP and WS-* in general, and federated transactions in particular, a bit too quick.
In my experience, most of WS-* simply doesn't work. That's not so bad, as most of it doesn't have any value to me, too, but still ;-).
Distributed transactions in particular have been dismissed by many experts that have worked on the topic for ages. There are highly plausible arguments that they might never work at all.
There is still a lot of work to be done, and at I'm very sceptical if all the WS-* stuff is actually helping to get stuff done or just an impediment.
what about downloading?
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.
7 comments
Watch Thread Reply