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 14, 2007
Windows Home Server is essentially a stripped down version of Windows Server 2003 meant for the consumer market. While it does expose a desktop, most users access it via a special admin console. This console is accessible from both the server and remotely, even over the Internet.
The admin console is fully extensible via managed code, making it a great way to build a software appliance. Or as a user, you can extend Home Server-based software appliances written by others. Installing new add-ins for the console is literally as simple as copying the DLLs to a folder on the server.
In a Channel 9 interview, Chris Gray demonstrates using Visual Basic Express to create a new home server console add-in. Visual Basic is not needed though, any .NET language that can be compiled to a DLL could be used. He has also posted samples of both the notification infrastructure, in C#, and the admin console extension, in VB.
One use for this extensibility is for health monitoring. If an application running on the server detects a problem, it can post an alert. This alert is visible both on the server and on any client computer running the monitoring tool.
Brendan has posted a template for Visual Basic and has started a series of tips on his blog.
SOA All-In-One Guide: KPIs & Best Practices, ESB Report
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Getting Started with Stratos - an Open Source Cloud Platform
18 agile and lean practices for effective software development governance
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