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 Abel Avram on Jul 22, 2010
Serena Yeoh, a Microsoft consultant and a contributor to Microsoft pattern&practices Application Architecture Guide, has created a Layered Architecture Sample for .NET 4.0 which was later ported to Azure, showcasing various .NET technologies (WPF, WCF, WF, ASP.NET, ADO.NET EF) used in an architecture based on the Layered Architecture design pattern.
The purpose of the code sample is to show how core .NET technologies can be used together in an enterprise application by applying architectural design principles promoting healthy growth of the code and easy maintenance.
The .NET sample contains 16 applications targeting various layers: Presentation, Business, Services, and Data. The model diagram looks as following:
By porting this code sample to Azure, Yeoh has created another sample showing how .NET core technologies can be used in the context of Microsoft’s cloud platform. The sample contains 3 additional projects related to cloud:
- ExpenseSample.Cloud.Service - Main cloud service project
- WCFWebHost - WCF Web Role project to host the back-end web services.
- WebRole - contains the ASP.NET application of the sample.
The Azure model diagram looks similar with some differences:
The samples including source code for all included projects are available on CodePlex under a MS-PL license: Layered Architecture Sample for .NET, Layered Architecture Sample for Azure.
Case Study: IBM's Agile Transformation
A Guide to Branching and Merging Patterns
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
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