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 Boris Lublinsky on Jan 17, 2009
This week Prentice Hall has announced the publication of "SOA Design Patterns", a comprehensive catalog of 85 design patterns for service-oriented architecture that documents the most proven and successful design techniques for succeeding with modern-day SOA. In conjunction with the release of the book, the new SOAPatterns.org community site has been launched, providing an open forum for the on-going development and expansion of the patterns.
"SOA Design Patterns" received enthusiastic participation throughout IT communities. Contributors included David Chappell and Clemens Utschig from Oracle, Mark Little from Red Hat, and Jason Hogg from Microsoft. Furthermore, Dennis Wisnosky, Chief Architect and Chief Technical Officer at the U.S. Department of Defense, contributed a chapter that explains how these design patterns (together with the design principles originally documented in Erl’s previous book, SOA Principles of Service Design), are being successfully applied within the U.S. Department of Defense as part of their SOA adoption initiatives.
The 85 patterns identified in the book include:
Canonical Schema Bus, Composition Design Patterns, Enterprise Service Bus, Inventory Design Patterns, Policy Enforcement, Reliable Messaging, Service Design Patterns, Service Grid, Three-Layer Inventory, and Transformation.
The manuscript was also reviewed by distinguished members of the patterns community, such as Grady Booch, Martin Fowler, and Ralph Johnson, one of the original members of the Gang of Four. Grady Booch, IBM Fellow and co-developer of the Unified Modeling Language (UML), provided the foreword for the book, in which he states:
SOA Design Patterns is an important contribution to the literature and practice of building and delivering quality software-intensive systems.
More industry responses can be found at the book web site
The enthusiasm surrounding the release of the book suggests that the rumors about SOA death are not quite true yet.
Free Gartner Cloud Services Brokerage Report
Agile Development: A Manager's Roadmap for Success
A practical guide to choosing the right agile tools
SOA All-In-One Guide: KPIs & Best Practices, ESB Report
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.
No comments
Watch Thread Reply