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 James Kao on May 17, 2007
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
Hi, I´m part of a 84 people team and we are currently using JDev 10.1.3.2 to support our process. All these new features seem to be interesting, but our feeling is that Oracle could invest more on stabilize current functionalities of JDev instead of putting more features into an IDE that already does hundreds of things, but does bad most of them. Among all the problems of JDev, here we extremely serious problems with JDev´s UML modelers and CVS integration.
Is this still tied to Oracle DB and Oracle Application Server
The largest problem I see is that you’re tied to Jdev once you go down the ADF faces road. Maybe I am mistaken, but all the features to do databinding to controls are only in Jdev and not in other IDEs. It seems that the tooling is built for ex Oracle Forms developers or as some of the marketing lingo goes “people who don’t have to know java” (Controls are reusable). Although Jdeveloper 11 does provide some fancy xml editors over these databinding xml files, you become extremely depend on the IDE. I think JBoss Seam got it right, ability to use the framework with or without tooling.
What makes you say that JDeveloper has ever been tied to only the Oracle Application server and database? This is not the case.
ADF provides a productivity layer, but of course it's only an optional thing. The IDE and the New Faces components don't force you to use ADF, you could build in Seam if you're happier doing that (and have the time to spare)
this blog from oracle, what I was referring to is #3
blogs.oracle.com/duffblog/2007/05/29#a437
Serge, That blog does not state anything about lock-in to JDeveloper, and is not referring to the Trinidad or ADF Faces components. It is talking about the ADFm layer, which is implementing JSR 227. I agree with Brian that we could reduce the number of .xml files in certain cases when Generics were used and the back-end service was Java, but this has nothing to do with you using the ADF Faces components. We have customers using them who do not use JDeveloper at all.
Ted your right about the ADF faces components. You can use them in any other IDE. What I should have said was that it would be very nice to see an approach that uses less XML in the data-binding department. As a person who uses and recommends Oracle products often, this is one area that I would be happy to see change. Will the Web beans JSR have an impact this area?
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.
8 comments
Watch Thread Reply