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 Oct 21, 2006
John Lam, the creator of RubyCLR, has accepted a position at Microsoft. While he hasn't yet revealed his new duties, he has stated that he will not leave the Ruby community.
First released in January of 2006, RubyCLR is a "high performance bridge between Ruby and .NET". The current version is only available as source code and will need to be compiled using VS 2005. Currently the project's wiki site is down, so documentation is hard to come by.
With his January 2007 start date fast approaching, Mr. Lam has already started looking for people to help drive the RubyCLR project. Interested people can find his contact information on his web log.
This isn't the first time Microsoft has tapped a dynamic programming language expert. It wasn't too long ago that Jim Hugunin of IronPython fame joined Microsoft.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Agile Maturity Model Applied to Building and Releasing Software
agility@scale eKit: 10 Principles, Scaling Model, Metrics, Collaboration
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
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