SOA Governance: An Enterprise View
Michael Poulin explains the necessity for SOA governance to ensure an Enterprise SOA's success, relying on concepts from the OASIS SOA Reference Model and Reference Architecture.
- SOA,
Tracking change and innovation in the enterprise software development community
Posted by Ben Hughes on Apr 11, 2008 09:45 AM
On April 15th Thoughtworks will release Mingle 2.0, nine months after the initial release of Mingle. InfoQ got some time with product manager Adam Monago to talk through the new functionality provided by Mingle 2.0. Amongst a plethora of fixes and new functionality in the release the most notable are:Scaling Agile on large teams & Being Agile every day Tracks @ QCon SF Nov 19-21
The Agile Business Analyst: Skills and Techniques needed for Agile
It will be interesting to see if they have reduced the memory footprint from 1GB RAM.
When Mingle first came out I was disappointed in a lot of ways, and especially felt it was not worth the per-user license fee they were charging. Mingle 2.0 might have me reconsider this product. I've always liked the philosophy behind the product, but didn't feel 1.0 was ready for prime-time. My team actually voted it down (we tried it out). The new features in 2.0 are huge improvements, and I think finally now it's "ready." I still do not agree with their pricing model.
Michael Poulin explains the necessity for SOA governance to ensure an Enterprise SOA's success, relying on concepts from the OASIS SOA Reference Model and Reference Architecture.
This article covers setting up a RichFaces portlet using JBoss Portlet Container and JBoss Portlet Bridge, deploying a RichFaces portlet, and RichFaces capabilities.
This article discusses scalability worst pratices including The Golden Hammer, Resource Abuse, Big Ball of Mud, Dependency Management, Timeouts, Hero Pattern, Not Automating, and Monitoring.
Obie Fernandez shares his experience selling consulting services for both Thoughtworks and Hashrocket and give tips how Ruby developers can work with clients.
Jeffries and Hendrickson derive Agile practices from the natural laws of software development. They don't just say "Be Agile!", but they explain why Agile practices make perfect sense.
Jinesh Varia talks about the architecture of one of Amazon's web services called Alexa. Jinesh explains how Amazon has reached scalability, performance and reduced costs for the Alexa service.
David Douglas and Robin Dymond discuss about companies adopting Agile, but don't go all the way, resulting in failure and rejection of it, and predictably having a negative impact on Agile's future.
Kenji Hiranabe talks about Toyota's development process of a new car. Kenji shares his experience meeting Nobuaki Katayama, former Chief Engineer at Toyota, and the lessons he learned from him.
2 comments
Reply