InfoQ Homepage Architecture Content on InfoQ
-
Designing Systems for Testability
Testability must be explicitly designed in the system said Peter Zimmerer from Siemens AG. Test architects should drive testability and collaborate with architects, designers and testers in using good design and engineering practices. At the QA&Test 2014 conference Peter gave a tutorial about design for testability for embedded software systems.
-
Mixing Agile with Waterfall for Code Quality
The 2014 CAST Research on Application Software Health (CRASH) report states that enterprise software built using a mixture of agile and waterfall methods will result in more robust and secure applications than those built using either agile or waterfall methods alone. InfoQ interviewed Bill Curtis about structural quality factors, and mixing agile and waterfall methods.
-
Core Support for JSON in Java 9
One of the first Java 9 features to be announced is core support for JSON. We spoke to early adopters to find out more.
-
InfoQ User Survey 2014 - Participate and Get a Copy of the Results; Win a QCon Early Access Pass
InfoQ would like to better understand your information needs: the type of content you find interesting, tools & methodologies you are using, and how you interact with the site. Please help us by taking our 2014 user survey - the survey is anonymous and your replies will be kept confidential. Participate to receive a copy of the results along with a chance to win a QCon video early access pass.
-
A New Style Is Emerging in the Enterprise: Software-Defined Architecture
According to Gartner’s Yefim V. Natis, VP & Fellow, a new enterprise architectural style is rising these days: Software-Defined Architecture (SDA).
-
How to Do Just Enough Up-front Design
This article includes advice for doing enough up-front architectural design to provide the needed structure to start a project, aligning the team with the architect’s vision and assessing the possible risks.
-
The Shallot 2014 Edition Published
The 2014 Edition of The Shallot - the online magazine which conducts deep analysis of the state of the information technology industry - has been released.
-
Rebecca Parsons on the ThoughtWorks Technology Radar
In January ThoughtWorks released the latest version of their Technology Radar in which they track what's interesting in the software development ecosystem. The big themes this year are (1) early warning systems and recovery in production, (2) the tension between privacy and big data, (3) the javascript ecosystem and (4) blurring of the line between the physical and virtual worlds.
-
Advice on When to Repay Technical Debt
An exploration of recent advice from Henrik Knibert, Ward Cunningham and Hayim Makabee on technical debt, how to make the most of it and when to pay it off.
-
Modernization Is Not Optional
Most large organizations have allowed their systems to evolve without good architecture and governance. The result is a "hair ball" of systems interfaces and dependencies which greatly increase complexity, risk and the cost of change. David Sprott describes how systems modernization should be a collaboration between business management and IT.
-
Stories of Using Real Options to Take Decisions
Projects and product development is one long series of difficult decisions, says Pascal Van Cauwenberghe. Real Options can help you to take the right decision at the right time, even under difficult circumstances. At the Agile Tour Brussels conference, Pascal presented stories of his experiences with using real options in decision taking.
-
Architects: Chickens or Pigs in an Agile Development Process?
Can architects play a meaningful role in agile projects, or does their tendency to do “big design up front” make them a sideline resource? Nick Malik, an Enterprise Architect with Microsoft, recently explored this topic in a blog post and concluded that architects can absolutely play a key role in software projects that use Scrum.
-
Uncle Bob: Architecture is About Intent, not Frameworks
Architecture is about intent, we have made it about frameworks and details, Robert C. Martin, “Uncle Bob”, stated earlier at this year’s DDD Exchange Day in London. Robert refers to a book by Ivar Jacobson from 1992 and brings the original thoughts about use cases into architecture models, e.g. Hexagonal architecture and Clean architecture to improve these models.
-
Vaughn Vernon on the Actor Model and Domain-Driven Design
To take advantage of the great concurrency opportunities the new multi-core machines gives us we should use a programming model that helps us achieve this, and the Actor model gives us a number of tools for doing that, Vaughn Vernon stated at this year’s DDD Exchange Day in London.
-
Vaughn Vernon on Advanced Architecture Styles with DDD
Using the Hexagonal architecture style allows for delaying decisions for architectural mechanisms and promotes using the same internal API irrespective of type of client, Vaughn Vernon explained last week when describing different architecture styles from a DDD perspective; the classical Layered Architecture and the more advanced Hexagonal and Actor Model styles.