Rails in the Large: How Agility Allows Us to Build One Of the World's Biggest Rails Apps
Neal Ford shows what ThoughtWorks learned from scaling Rails development: infrastructure, testing, messaging, optimization, performance.
Tracking change and innovation in the enterprise software development community
Posted by Abel Avram on Jan 22, 2009
In this article, Kjell-Sverre Jerijærvi presents with enough detail Microsoft’s SOA Maturity Model (SOAMM) which can be used to evaluate the maturity of a SOA implementation.
Read: SOA Contract Maturity Model
SOAMM has four levels of increasing maturity:
Each level is evaluated considering the following 3 perspectives:
Service Implementation
This model perspective describes capabilities of an enterprise to implement efficient best practices, patterns in building and providing services. Achieving this capability strengthens and optimizes the design and development of enterprise business and system services.
Service Consumption
This model perspective describes capabilities of an enterprise to effectively adopt and promote use of services. This capability provides foundation for support and enhancement the consumption of enterprise services by others.
Service Administration
This model perspective describes capabilities of an enterprise to support the cross-organization governance and operational aspects of services.
Kjell-Sverre explains each maturity level, how one qualifies for it and what are the benefits. While most companies, 82% to be more precise, are at Basic level, there is no need to jump from start to the highest level in order to achieve results with SOA. One can start with the Basic level and gradually advance to the Dynamic one which provides the best results for a SOA investment.
Comparing WebLogic, WebSphere, Oracle, and Open Source Application Servers
Lean development governance whitepaper by Scott Ambler and Per Kroll
Intel® SOA Expressway Performance Comparison to IBM® DataPower XI50
The XACML Enabled Gateway -- The entrance to a New SOA Ecosystem
Neal Ford shows what ThoughtWorks learned from scaling Rails development: infrastructure, testing, messaging, optimization, performance.
Stuart Halloway discusses Clojure and functional programing on the JVM in depth, and touches on the uses of a number of other modern JVM languages including JRuby, Groovy, Scala and Haskell.
Orion Henry and Blake Mizerany talk about the technology behind Heroku and the benefits of the new add-on system.
Chris Riley presents security issues threatening service based systems, examining security threats, presenting measures to reduce the risks, and mentioning available security frameworks.
This talk investigates technical issues encountered when moving to an Agile process.
Don Box and Amanda Laucher present “M”, a declarative language for building data models, domain models or external DSLs. Don Box's demos show some of M’s features and latest changes of the language.
It is four months since the SOA manifesto was announced; InfoQ interviewed the original author’s to get insight into the motivations and the process behind the initiative.
This article explains the impact memory barriers, or fences, have on the determinism of multi-threaded programs.
No comments
Watch Thread Reply