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 Feb 18, 2010
With Jscript.NET more or less abandoned by Microsoft, there is an opening for a new JavaScript compatible language on the CLR. Fredrik Holmström is trying to fill the void with IronJS. Like the other Iron languages by Microsoft and independent developers, it is based on the Dynamic Language Runtime. This includes the DLR’s hosting framework and unified object model.
While still in the early stages, IronJS currently runs CLR 2 and Mono 2.6 and can compile jQuery 1.4. IronJS is being offered on github under the Microsoft Public License.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Mobile and the New Two-Tiered Web Architecture
Agile Development: A Manager's Roadmap for Success
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
The only thing missing is Silverlight support. It currently depends upon System.Web, so some changes will need to be made to get it running on Silverlight. However, once it does, it would be theoretically possible to swap out IE's JS engine for IronJS through Gestalt [1]. Actually, I wouldn't mind seeing IE adopt the DLR as its scripting engine and use IronJS for its JavaScript runtime.
[1] gestalt.codeplex.com/
Interesting. But there's a chance IronJS + COM interop is slower when accessing the HTML DOM than poor old JScript, depending on your ratio of DOM access vs. pure JavaScript execution.
What's COM got to do with it? Silverlight can access the HTML directly, so I would think you could access the current document just fine. Am I missing something?
But how does Silverlight (.NET) access IE's DOM (exposed via COM)? I assume they're using some kind of COM interop internally. Just because you can't see it...
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.
4 comments
Watch Thread Reply