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 Al Tenhundfeld on Jun 25, 2008
Jeff Wilcox, primary developer of the Silverlight unit test framework, has posted several entries on writing unit tests for Silverlight 2. In addition to step-by-step instructions, Jeff has provided updated test project templates and repackaged Silverlight.Testing assemblies. The updated test framework allows testing against Microsoft's recently released Beta 2 of its upcoming Silverlight 2.0 rich-client browser plugin. The current Silverlight testing framework is not yet integrated into the Visual Studio test runner, but the framework leverages the same types and attributes used by MS Test and should be familiar to developers who are writing traditional unit tests in Visual Studio. Even if a development team does not practice test-driven development, having programmatic tests exercise UI code is valuable for regression and integration testing.
Jeff sums up the value in his tutorial:
Having unit tests is extremely useful because the more test scenarios you create, the more confidence you'll have when adding features and fixing bugs, especially if you're working with a team of developers. Since the test projects are packaged like any other Silverlight application, there's no special installation process to run the tests. On the Silverlight controls team we've built thousands of these tests!
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
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