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 Miko Matsumura on Jul 18, 2006
Tooling for SOA projects is certainly a work in progress with specifications like SCA and JBI under development.
When it comes to good old fashioned SOAP, a few good tools come to mind like XML Spy, NetTool, SOAPScope and others. I'm sure every developer has their favorite tool.
One tool in the open source community, called soapui seems to be undergoing some rapid updating with a new "dot rev" (not a major revision) available on a monthy basis. That tool is soapui, available under the LGPL license.
For those not familiar with LGPL, it's the non-viral variant of GNU Public License, and is generally considered a reasonably business friendly license, being used most famously by OpenOffice.org. The LGPL is also the license through which the majority of JBoss Inc. (a subsidiary of RedHat Software) is distributed. According to the JBoss web site "The LGPL is the most business-friendly license for enterprise IT organizations, independent software vendors, and the open source community itself."
The soapui tool is a Java 1.5 based desktop application for inspecting, invoking, developing and functional/load/compliance testing of web services over HTTP. It is mainly aimed at developers/testers providing and/or consuming web services (java, .net, etc). Functional and Load-Testing can be done both interactively in soapui or within an automated build/integration process using the soapui command-line tools.
Major improvements in this release include:
I also like the fact there's an integration mechanism with Groovy that lets you build more complex scenarii for testing all your SOAP Web Services.
--
Guillaume Laforge
Groovy Project Manager
JSR-241 Spec Lead
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