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 Dec 01, 2008
The feature list for Huagati DBML/EDMX Tools reads like a defect report for the related Microsoft products. There is no bloat here, everything is a must have for many shops.
LINQ to SQL Features
First up is a no-brainer, updating LINQ to SQL diagrams when the underlying database changes. One would think Microsoft would provide this out of the box, but since they didn't this alone makes this product worth its price.
Huagati's tool is also more intelligent about honoring default constraints such NewID and GetDate. Exclusion rules to prevent unwanted tables and columns from being repeatedly suggested round out this feature.
Since developers might not want to apply the changes right away, the tool can generate a report showing the differences, a comparison report is also available.
Naming Standards
A major problem for both LINQ to SQL and ADO.NET Entity Framework is that it does not handle naming standards. Using Huagati's tool, developers can specify rules such as when to strip off prefixes, how to case property names, and whether to remove underscores.
Documentation
The final feature is again something Visual Studio should have had but does not. The tool can automatically create or update an application's XML documentation using the table and column descriptions from the database.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
A Guide to Branching and Merging Patterns
Getting Started with Stratos - an Open Source Cloud Platform
18 agile and lean practices for effective software development governance
Monitor your Production Java App - includes JMX! Low Overhead - Free download
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