InfoQ Homepage Methodologies Content on InfoQ
-
Futures Trade Flow
Ian Bond presents the development of a trade flow event-driven architecture, providing the background of futures trade, the domain and the solution, sharing some of the lessons learned along the way.
-
Putting the "re" into Architecture
Kevlin Henney promotes live architecture through refactoring, recovery, re-envisioning, retrospection, re-engineering, repair, rewriting, reduction, reuse, reaction, re-evaluation and remembering.
-
QCon Keynote: Innovation at Google
Patrick Copeland presents the first three principles of the eXtreme innovation approach based on the Pretotyping Manifesto: Innovators Beat Ideas, Pretotypes Beat Productypes, and Data Beats Opinion.
-
Searching Without Objectives
Kenneth O. Stanley considers that innovation is stifled when we are strictly following a high goal, and we would progress more when we are inclined to discovery rather than following an objective.
-
The Case for Evolvable Software
Stephanie Forrest believes in the possibility to create evolvable software through automated bug repair, optimizing or improving code and creating new combinations of existing functionality.
-
Classes Are Premature Optimization
Justin Love discusses the difference between the classic OOP programming model based on classes and prototypal inheritance built on objects as done in JavaScript, and how they affect performance.
-
Agile Does Not Guarantee Value Creation
Leonardo Mattiazzi considers that Scrum and XP are not enough, and complementary Lean principles and practices are necessary to create an Agile culture across the entire enterprise in order to succeed
-
Proving the Business Value of SOA
Anne Thomas Manes discusses SOA goals and objectives used to measure a system’s success, measuring the business value, SOA project metrics, and recommendations on proving the business value of SOA.
-
RESTful SOA or Domain-Driven Design - A Compromise?
Vaughn Vernon advocates using DDD’s strategic modeling patterns when integrating services in a RESTful SOA implementation, avoiding one of SOA’s pitfalls: focusing on services rather than the domain.
-
Introduction to Spring Roo
Rod Johnson and Stefan Schmidt introduce Spring Roo, building a sample app, unit and integration tests, AspectJ utilization, dependency injection, controller/view generation and GWT integration.
-
Abstractions at Scale–Our Experiences at Twitter
Marius Eriksen considers that leaky abstractions lead to scalability issues, while those providing narrow access to explicit resources - map-reduce, shared-nothing web apps, big table - scale better.
-
Resurrecting SOA
Anne Thomas Manes redefines SOA based on the SOA Manifesto, focusing on models, methodologies and patterns, not on technology, intended to produce the desired business and technical goals.