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?
Getting Started with Stratos - an Open Source Cloud Platform
Transforming Software Delivery: An IBM Rational Case Study
Agile Development: A Manager's Roadmap for Success
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Good to hear that not all have pursued the fad of storing all the business logic in the middle tier, as we've been told by many gurus. After building some significant stored procedures, and then pondered the corresponding complexity of J2EE EJBs and/or Hibernate and burying the logic in xml, and coming to the same conclusion as Andres, I will meld a couple of his points - the architecture needs to fit the organization, and simple is good.
Maybe business logic in the db is not a good fit for everybody, but we must stop blindly accepting the latest wisdom as the end-all be-all truth.
The pgQueue was very interesting idea also, especially simplifying from once-and-only-once to at-least-once. There was a post recently here on Infoq that was about a very similar idea, except it was unfortunately a little misleading in that, perhaps for fanfare, it stated that there was no need for a queue. But they were still building all the queue infrastructure, it was just a simplified queue. So the idea of a queue structure still holds and is very useful, as can be illustrated in languages like Erlang, which supports concurrency nicely, offering tremendous performance.
It would be very interesting to hear more about this design, and also the various tools available from Postgres that were mentioned.
Thanks for the interesting talk!
very nice presentation. some databases have very useful features. thank you!
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.
2 comments
Watch Thread Reply