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 Charles Humble on Nov 11, 2009
Sun's implementation of J2SE 5.0 reached its End of Service Life (EOSL) on November the 3rd 2009, which is the date of the final publicly available update of version 5.0 (J2SE 5.0 Update 22). Customers looking for support from Sun can either update to Java 6 or subscribe to Sun's Java for business program.
Sun offers a number of paid support options for Java. Java classic support covers the latest release of Java for a period of three years from product release and comes in two variations: Standard support which provides business-hour (12x5) coverage with a four hour response time SLA, and premium support which offers 24x7 support with an immediate response time. The cost of Java classic support starts at $15,000 per year. Pricing increases by the size of the organisation and for very large enterprises could be up to around $250,000 per year.
Extended support is offered for Java versions which have reached EOSL through Sun's Java for business program, which covers Java versions 1.4.2, 5 and 6. A Java for business contract extends Java support for up to 15 years, meaning that Java 1.4.2 would remain supported until September 2017. During the extended support period Sun continues to offer security patches and updates to support new versions of the OS. The Java for business program is offered in four different packages:
The approach is one way for Sun to drive revenue from customers' use of older versions of Java. Earlier this year Sun signed a deal with SAP to provide support for all SAP customers running Java 1.4.2 with NetWeaver 2004 and 7.0. Other clients include Salesforce.com and SAS.
Of course Sun will continue to offer the platform for developers in Sun's archive section, and users of other implementations, such as those from Apple and IBM, are not affected.
In this context, I would like to try and gauge what versions of Java the InfoQ community are using at work, so please vote in the poll below.
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
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
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.
No comments
Watch Thread Reply