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 Jonathan Allen on Jun 01, 2007
While Silverlight promises a future where rich client applications written in .NET work seamlessly in all web browsers, many developers cannot afford to wait. And that means using proven deployment technology that is already available.
Currently there are three ways to deploy rich client .NET applications. The simplest is to just offer the executable, possibly wrapped in a zip file with its dependencies. Unfortunately, this does not lead to a very rich user experience. Installation activities like creating shortcuts do not occur, and automatic updates are not even a consideration.
The next option is to offer a MSI package. While this does support installation activities like COM registration and shortcuts, it also lacks automatic update support.
This is where ClickOnce comes into play. Once installed, ClickOnce offers automatic updates based on declarative rules and/or an API. Other features include the ability to partially install applications, downloading other components as needed, and the ability to launch applications from URLs. One can even pass startup parameters to the application in this manner.
Unfortunately, until recently ClickOnce was not supported on non-IE browsers. When it came out in 2005 this may have been acceptable, but with Firefox continuing to gain market share it is no longer appropriate to require users to run IE.
This is where James Dobson picks up the slack. Via an extension he is calling FFClickOnce, Firefox users can now install and launch ClickOnce applications without switching to IE.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Case Study: IBM's Agile Transformation
SCM best practices for multiple processes, releases & distributed teams
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