Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Architecture Evaluation Content on InfoQ

  • Modular Monolithic Architecture, Microservices and Architectural Drivers

    Kamil Grzybek thinks that too often we implement a microservices architecture because we believe it will solve all problems in a monolithic application. Instead, we should focus on architectural drivers to find the best architecture for a system. In a series of articles, he has started to describe the basic concepts of a modular monolith and the drivers leading to a specific architecture.

  • Strategies for Decomposing a System into Microservices

    A couple of years ago, Vladik Khononov and his team decided to start using microservices, but a few months later they found themselves in a huge mess. They concentrated on new cool technologies instead of thinking about how to decompose a system into microservices — finding the boundaries and where different functionalities should be located among these boundaries.

  • Community-Driven Research: Top Quality Standards for Architecture Reviews

    InfoQ's research initiative continues with an 9th question: "Top Quality Standards for Architecture Reviews". This is a new service we hope will provide you with up-to-date & bias-free community-based insight into trends & behaviors that affect enterprise software development. Unlike traditional vendor/analyst-based research, our research is based on answers provided by YOU.

  • The Open Group Releases Standards for SOA Architects, Cloud Service Providers

    The Open Group recently published three standards that aid organizations that are building infrastructure-as-a-service offerings and service oriented architectures. In concert, these standards provide expert advice in the form of best practices, questionnaires, and templates for SOA and cloud-scale infrastructure architecture.

  • Preview: 15th SPLC Conference on Software Product Lines

    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.

  • New Books on Software Architecture

    Software Architecture is one of the important topics for software engineers, because many failures of software development projects are caused by inadequate design. Thus, it is essential to learn more about architectural issues in theory and practice. Interesting new books that have been published recently or in the near future could be very helpful

  • Upcoming Conference CompArch 2011 in Boulder, Colorado

    The CompArch Conference is a federated conference that brings together researchers and practitioners interested in Component-Based Software Development and Software Architecture. This year the event is held at the University of Colorado in the United States from June 20th to June 24th. As general chairs Ivica Cnrkovic and Judith Stafford were appointed.

  • Palladio provides Version 3.2 of its Software Architecture Simulator

    Palladio Bench supports architects and developers in deriving quality of software estimations such as performance, reliability, maintainability and development costs from models. Its new version 3.2 is based on Eclipse 3.5 (Galileo) and adds several stabilizations and fixes, a reliability analysis, a new graphical editor and a new workflow engine, as well as a probe specification framework.

  • Thoughtworks is using Structure101 for Analyzing Code Bases

    ThoughtWorks, a global IT consultancy that focuses on agile development, recently announced they will leverage the software architecture management tool Structure101 for assessing the quality of code bases. Structure101 is the main product that Headway Software provides for advanced code analysis.

  • Leverage Points: places to intervene in a system

    A key decision for software architects involves where and how to introduce change into a system in order to effect a desired change. Leverage points are those places where micro changes can result in macro results. Twelve categories of leverage point are identified along with concerns about the changes.

  • Felix Bachmann on Evaluating Software Architecture

    Evaluating software architecture and identifying risks in applications is an important part of enterprise architecture (EA). Felix Bachmann of SEI recently talked about how to effectively evaluate software architecture. He hosted a seminar at SEI Architecture (SATURN) conference on this topic. He also discussed how Architecture Tradeoff Analysis Method (ATAM) framework utilizes these principles.

  • Temporal and Behavioral Coupling

    Low coupling has always been the Holy Grail of good software engineering. In his new post, Ian Robinson explores two specific types of coupling, temporal and behavioral.

  • Article: Data storage and analysis for the largest scientific instrument on the planet (LHC Grid)

    The Large Hadron Collider (LHC) is a particle accelerator that aims to revolutionize our understanding of our universe. The Worldwide LHC Computing Grid (LCG) project provides data storage and analysis infrastructure for the entire high energy physics community that will use the LHC.

  • Presentation: Lessons Learned from Architecture Reviews

    In this presentation, Rebecca Wirfs-Brock presents some practical lessons she has learned from doing architectural reviews. Many times projects are not delivered in time, or have quality problems or have an incomplete set of features due to architectural flaws. The reviews are meant to highlight existing risks and strengths of the architecture, and to reveal issues initially neglected.

  • Should your architecture focus on SOA or BPM?

    While SOA was the big name in the buzzword tag cloud, BPM is quickly getting bigger and bigger. As organizations are becoming more aware of the need to tame their processes in order to get the benefits of IT investments, BPM is gaining importance and mindshare inside and outside of IT. Is one more important for your architecture?