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 06, 2007
Adobe released the Alpha of Apollo a few weeks ago and there have been many reactions to the product and Flex in general since. Additionally, Adobe updated Flex.org to make it easier to get started with Flex.
Flex.org was updated this week to provide easier access to people seeking to learn about Flex. They created pages targeted to developers from different backend languages including Java, .NET, PHP, Ruby and ColdFusion. Additionally they have integrated FlexSearch.org
The developers of Buzzword have written about choosing Flex to create a new web-based word processor. They cite the need for a WYSIWYG application as the primary reason they have not done something similar to Google Docs. They're looking forward to Apollo to offer a hybrid online/offline version of their application.
Alexander Snaps has written about some concerns he has over backwards compatibility as well as single-vendor lock-in. The comments on his post offer a comparison of how Java and Flash have both done a good job at backwards compatibility, while both have had occasional problems. Flash is generally limited to a single installed runtime while with Java you can run multiple versions concurrently, should a compatibility issue arise.
Lastly, Scott Barnes, a Microsoft Developer Evangelist for RIAs, points out some resources for .NET developers looking at integrating with Flex.
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
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
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