Tracking change and innovation in the enterprise software development community
Create REST
-enabled Web Apps
with Project Zero
from IBM.
Introducing the
SpringSource
Application Platform:
Next-gen Java
AppServer
Rule your SOA
with CentraSite
standards-based
registry/repository
Plan-driven dev
Environments and
Agile tutorials at the
Better Software
Conference & Expo!
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
During OOPSLA 2007, InfoQ interviewed Markus Voelter asking him about creating software architecture documentation. Many people mention UML when they are asked about software design documentation, but Markus has a different take on that. He thinks that we should be using models which can be processed with tools which can validate or invalidate them.
In this article, Alex Ruiz and Jeff Bay describe Java's suitability as a DSL-producing language, delve into the creation of internal DSLs in Java, walk through an example of a Java-based internal DSL, and give recommendations on writing DSLs in Java.
Kent Beck's new book, Implementation Patterns, is a book about writing code in Java. The patterns in this book are based on Kent's reading of existing code as well as his own programming habits. The patterns in this book are meant to be a coherent view of how to write code people can understand.
There is no silver bullet. We know it, but don't act like it. Your language, tool or process is better, right? Jay Fields says: "It depends". The right choices varies with context, people, and more. This article touches upon how a lot of things must impact a choice; learning culture, skill levels, teamwork, incomplete information, metrics - and context.
Architecture is often described non-tangible in Word documents or entirely technology-driven. Both are bad, but what can be done? Markus Völter describes how to evolve a language around your architecture, a formal language that as a side effect ends up being a good base for generating important parts of the system.
In this interview from OOPSLA 2007, Michael Stal talks about architecture refactoring. He describes what architecture refactoring is, its relationship to code refactoring and patterns, and he gives real world examples of how architecture refactorings have been done and when not to do it.
Kent Beck is interviewed at OOPSLA 2007 about his new book, "Implementation patterns", the relationship between these patterns and XP, problems when adopting agile and the current status of design patterns.
Security is all about trade-offs you make with your always limited resources, often a problem when designing a system or an after-thought. Only a few have the expertise to design good security and most development teams have no security expert. This talk focuses on Security Patterns for designing security in architectures, such as Role-based Access Control, Single Access Point, and Front Door.
Randy Shoup covers the architectural principles eBay has used to grow and evolve its infrastructure to massive scale. It covers the forces ("-ilities") needed to contend with and design for scalability, availability, manageability, etc. He outlines eBay's architectural principles which meet - and trade off - those forces and describes reusable patterns for each strategy with eBay examples.
