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 Feb 21, 2007
Excelsior has commented on a major change coming in v5 of their Java SE 5 implementation, Excelsior JET. To reduce the download size of applications, developers will be able to exclude parts of the JDK from the application.
Excluded components will be packaged as a single downloadable file that will be placed on the server where your application is available. While the application is running, if it attempts to access the excluded components, the JET Runtime will pull the bundle down from the server. Excelsior describes the situation:
The key idea is to select a few components of the entire Java SE API, which the developers could optionally exclude from the installation if the application does not use them.
For example, if your application does not use any of AWT, Swing, CORBA or, say, JNDI API, you will be able to exclude them from the installation created with the JetPackII tool.
No word yet on how big of an impact this can end up being for a typical application nor when we can expect to see a preview of the functionality.
Monitor your Production Java App - includes JMX! Low Overhead - Free download
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
18 agile and lean practices for effective software development governance
We have posted the download size figures for a few applications. Version 5.0 will also offer substantial application performance improvements, especially for floating-point intensive code
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