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 Nov 18, 2008
The Singularity project was started in 2003 as a fundamental redesign of how operating systems work. From the ground up everything is based on the concepts of isolation and verifiability.
Processes are highly isolated from one-another. Communication is done strictly via type-safe channels, shared memory of any form is not allowed. Processes are "sealed", meaning they cannot dynamically load or generate code. This has the advantage of making virus injection virtually impossible, at the cost of not being able to use dynamic link libraries or meta-programming techniques.
Other than a small part of the kernel, the bulk of Singularity is written in the type-safe language Sing#. Instead of platform specific assembly languages, Singularity uses .NET's IL as the lowest common denominator. Singularity will not even try to load unmanaged applications.
The first 2.0 release includes the full source code tree and a bootable CD image. A Virtual PC file is also available in this release.
In an unusual move by Microsoft, Singularity is soliciting patches and offering full developer rights on CodePlex.
We're also looking to increase community participation in the RDK 2 - so if you're using the RDK for something cool, let us know on the Discussions tab, and submit Patches on the Source Code tab. Patches will be integrated into the codebase, so that other RDK users can take advantage of your work. We will grant Developer permissions to frequent contributors to help streamline their contributions and let the users drive the future of the RDK.
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
it's not quite OSS: www.codeplex.com/singularity/license
Microsoft Research License Agreement
Non-Commercial Academic Use Only
And I think that "at the cost of not being able to use dynamic link libraries or meta-programming techniques" is a harsh misinterpretation. First, in .NET all libaries are DLLs, even if they are statically referenced. I'd assume that it's the same in Singularity, so this would just prevent us from loading add-ins at runtime in the same process. Second, meta-programming is probably just requiring setting up new processes too, which Singularity should be good at (static verification makes memory boundaries unnecessary, leading to faster process launches and context switches).
I hope MS is following this path. In a world of virtualization, there might be a sensible, practical path to a new OS paradigm.
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