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 Rob Thornton on Apr 13, 2007
Howard Lovatt, the author of the C3S proposal for closures in Java, has written a detailed comparison of the four best known proposals (C3S, FCM, CICE, and BGGA). At the same time the authors of the FCM proposal have released a new position paper building on FCM for control abstraction. Ricky Clarkson thinks that CICE is insufficient and wonders if internal politics at Google are affecting it.
Lovatt walks through the four proposals and compares each in terms of eleven features:
His goal in writing is to separate out the inner class / closure part of the proposal from any other extras that might come with it. On the heels of this comparison, Stephen Colebourne, Stefan Schulz, and Ricky Clarkson have built upon FCM with a position paper (they clarify that it is not a proposal and thus not complete) for Java Control Abstraction. They motivate the need for JCA because there are places closures are not applicable. Such a place is where an API exists that is used very similarly to a built in keyword.
Lastly, Ricky Clarkson wonders if politics at Google have affected the advancement of BGGA proposal. There are restrictions on who is able to contribute to the JCP, specifically if your employer is a member, you cannot be. Clarkson suggests that Josh Bloch, Google's contact on the JCP, may be uninterested in creating a JSR for as he has already proposed CICE. Bob Lee, one of the co-authors of CICE responds to Clarkson saying this is an unfair suggestion and that there is no rush to get closures into Java.
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
Monitor your Production Java App - includes JMX! Low Overhead - Free download
That's the first time I've been called Clarkson since school.
Josh Bloch recently replied to a blog post somewhere to remind us of his solution to many of the use cases that CICE alone misses out on - docs.google.com/View?docid=dffxznxr_1nmsqkz - I still think with CICE and ARM blocks he's likely to miss some use cases, but I haven't identified any yet.
Cheers.
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