James Governor from RedMonk has written about how immutable infrastructure approaches are applicable to microservices. In his view, all microservices must be immutable and developers will observe the same benefits which others are already seeing in lower layers of the software stack.
Reuse has been a watch word for almost everything that has happened in system development during the last thirty years, but reuse is like cyanide; in really small portions it can be healthy, using it too much it starts doing a lot of damage, Udi Dahan claimed in his presentation giving a different perspective on business logic at this year’s DDD Exchange conference in London.
Enterprises that are adopting agile organizational-wide will at some time have to scale their agile practices. In a session at the Agile Methods in the Finance Sector and Complex Environment conference, attendees shared their experiences with scaling agile in enterprises.
After many years of working in the SOA field, Jean-Jacques Dubray has written down what he believes are four principles for helping to achieve successful SOA.
The International Software Product Line Conference (SPLC) is the most important event that covers the full range of Product Line Engineering in software-intensive products. Its 15th incarnation will take place in the Munich City Center from August 21st to August 26th.
Is service reuse a valid metric for determining the success of SOA? Richard Watson from Burton believes that we are too fixated on reuse and could lose sight of the real benefit: service use.
Planning reusability is hard, designing for unforeseen reuse might be even harder. In this QCon London 2008 talk, Steve Vinoski presents some of the barriers to reuse found in typical distributed systems development approaches, and discusses how REST not only helps overcome some of these barriers, but also leads to potentially significantly increased chances for achieving serendipitous reuse.
We interviewed Immo Landwerth of the open source project Clone Detective for Visual Studio. This project leverages ConQAT to analyze C# code for duplication.
Susan Hall spoke with Gartner analyst Roy Schulte, a specialist in service-oriented architecture and co-author of the 1996 Gartner report that introduced the term SOA to the industry. The interview tries to answer the question, is it time to realign our expectations about SOA?
Managing commonality and variability is the core of product line engineering. In this presentation, Markus Völter illustrates how model-driven and aspect oriented software development help addressing the challenge of managing variability in product line engineering.
Naked Objects is an architectural pattern and a framework for developing applications where domain objects takes a central role. Naked Objects recently released version 3.0 with support for Java 1.5, injection, an alternate UI, Hibernate object store, integrated security and contributed actions. InfoQ took the opportunity to speak with Richard Pawson, inventor of the Naked Objects pattern.
According to Bob Warfield, at least 70% of code is wasted because it’s written to build components which would add no competitive differentiation to the final product. To reduce this "waste", programmers should practice code reuse instead of repeatedly building the same components. However, to facilitate code reuse it is necessary to move away from exclusive use of OOP and Curly Brace Languages.
Code reuse has been the holy grail of software development for a long time. Historically we've tried to achieve code reuse through abstractions and frameworks, which came with their own technical debt. There is now a novel approach that leverages the power of search tools and automated developer tests to search open-source code for matches against interface and behavior.
A new project aims to increase collaboration among JVM based languages. The Java Language Runtime aims to collect code that is common among languages targeting the JVM and prevent duplication among the providers of JRuby, Jython, Groovy, and many others.
Dennis Forbes bucks the conventional wisdom that has caused the industry to trend toward architectures focused on asset reuse, asserting that code reuse is highly overrated and rarely pans out as advertised.