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 May 31, 2007
In the past there have been many complaints about Visual Basic being a second-class citizen to C# and that Microsoft never uses it internally. Those complaints are being addressed by SilverLight in numerous ways.
First of all, C# won't be fully supported in Silverlight. Unlike VB, Python, Ruby, and JavaScript, C# does not support the Dynamic Language Runtime and cannot be hosted for runtime compilation in Silverlight.
In more recent news, it was revealed that Visual Basic 10 would have a compiler written in Visual Basic. While Mono has a self-hosting compiler for VB, this is the first time in the history of Visual Basic that Microsoft released a VB compiler written in VB.
Even more interesting, the next version of Microsoft's JavaScript compiler, known by the brand name JScript, was also written in Visual Basic.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Agility at scale, become as agile as you can be
18 agile and lean practices for effective software development governance
Getting Started with Stratos - an Open Source Cloud Platform
I'm not sure I understand this part about C# not being available on Silverlight... does that mean the C# compiler doesn't run on Silverlight? LINQ and other libs are available for Silverlight, so I'm a bit confused;
Silverlight can certainly use libraries compiled with C#.
What Silverlight cannot do is grab a block of C# source code and compile it in the browser at runtime using the DLR. How important this is remains to be seen, but if you are a fan of code that writes itself (e.g. LISP, JavaScript) it is a consideration.
OK, that clears that up. Thanks.
Of course, as long as it ships with the CodeDOM (I think that's their name) libraries, then generating code is still possible (see vistasmalltalk.wordpress.com/ for an impressive example of that).
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.
3 comments
Watch Thread Reply