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 Dec 18, 2007
I’ve been concerned a bit that it may appear as though Joe joining SitePen may carry with it the perception that the Dojo Foundation is an arm of SitePen in some way or that DWR will now need to become Dojo-centric. Luckily neither is the case, although reading assurances to that effect on this blog should be taken with a grain of salt. The Foundation has an open door for deserving projects which need a good legal umbrella and don’t want a lot of process or formality, and we’ve extended personal invitations to many non-Dojo-centric projects over the years to join (including direct competitors).The move to the Dojo Foundation is progressing, but will not be immediate. Along with the code itself, there are also a whole set of organization issues to consider:
DWR 2.0 has been out for 6 months or so. At the time, I swore that the next release would be a small one, called 2.1. However it appears that I’m not good at swearing because there is lots in the next release - I think we’re going to have to call it 3.0.So what's in DWR 3.0?
We're doing some Pub/Sub work, so DWR can be a Hub which can be used on it's own or plugged into JMS on the server-side or the OpenAjax Hub on the client. We're allowing file upload/download and some image management over DWR and adding support for JSONP and the Bayeux protocol. Another really cool feature is fairly complete version of the TIBCO GI API as a reverse ajax proxy, and I'm hoping that we can get Gears support for automatic off-line support and maybe to allow transactional remote calls. I'll be blogging about all this in more detail in a few days over at http://getahead.org/blog/joe.
Mobile and the New Two-Tiered Web Architecture
18 agile and lean practices for effective software development governance
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
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!
Perhaps a link to DWR, or a definition of what DWR stands for. What is DWR?
(D)irect (W)eb (R)emoting
DWR means Demon Wielding Rakes
The promised post: getahead.org/blog/joe/2007/12/20/dwr_state_of_t...
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.
4 comments
Watch Thread Reply