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 03, 2008
Microsoft has just released the Composite Application Guidance for WPF-June 2008, also known as Prism.
According to Microsoft:
The Composite Application Guidance for WPF is designed to help you more easily build enterprise-level Windows Presentation Foundation (WPF) client applications. It will help you design and build flexible composite WPF client applications—composite applications use loosely coupled, independently evolvable pieces that work together in the overall application.
The Composite Application Guidance for WPF can help you split the development of your WPF client application across multiple development teams. In this type of application, each team is responsible for the development of different pieces of the application, which are seamlessly composed together.
This guidance contains the following:
The Composite Application Guidance for WPF is intended for architects and WPF developers according to Microsoft:
This guidance is intended for software architects and software developers who are building enterprise WPF client applications from loosely coupled components developed across multiple teams. The Composite Application Library is built on the Microsoft .NET Framework and Windows Presentation Foundation, and it uses a number of software design patterns. Familiarity with these technologies and patterns is useful for evaluating and adopting the Composite Application Library.
The Composite Application Guidance for WPF is also available as a project on CodePlex, offering the source code under Microsoft Public License (Ms-PL). More detailed information about the guidance is available on MSDN.
The supported operating systems are: Windows Server 2003, Windows Server 2008, Windows Vista, Windows XP Professional Edition. Microsoft Visual Studio 2008 is necessary for development along with Microsoft .NET Framework 3.5 which includes WPF.
InfoQ covered Prism in a news post in May, and we recently interviewed Glenn Block, a Microsoft Technical Product Planner for the Client UX program at patterns & practices, on Prism.
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