BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Methodologies Content on InfoQ

  • Benefits of Agile Transformation at Barclays

    Increased throughput, reduced code complexity, less production incidents, shorter deployment cycles and higher happiness in teams; these are some of the benefits that the agile transformation at Barclays has delivered. Within the first year of the transformation, which is based on Disciplined Agile, more than 800 teams adopted agile making this one of the largest agile implementations.

  • Data is the Hard Part Working with Microservices

    One of the hardest problem when creating and developing microservices for an enterprise is their data. Analysing the business domain using Domain-Driven Design (DDD) and reason about what your data represents will help in achieving a microservices architecture, Christian Posta claims in one of a series of blog posts about microservices implementations.

  • Vaughn Vernon on Microservices and Domain-Driven Design

    Although a monolith can be modeled in a respectable way, often they are turned into a big ball of mud. This is caused by multiple domain models becoming entangled within the monolith, and in Vaughn Vernon's experience this can happen within a few weeks or months, he claimed in a presentation at the Scala Days conference earlier this year.

  • C++17 Feature List is Now Complete, Enters Review

    During the last meeting in Oulu, Finland, the ISO C++ committee completed the definition of the C++17 feature list. At the meeting, a number of new language and library features were approved, including constexpr if, template <auto>, structured bindings, and others.

  • Experiences Using Event Storming

    In the context of Domain-Driven Design (DDD), Event Storming is incredibly useful and valuable, Dan North claimed in his presentation at the recent DDD eXchange conference in London, explaining the basic mechanics of Event Storming and sharing his experiences from modelling different systems during the last few years.

  • Eric Evans: Is Domain-Driven Design Beneficial for Software Development?

    The last couple of years the interest in Domain-Driven Design (DDD) has increased, Eric Evans noted in his keynote at the recent DDD eXchange conference in London. He thinks that we are in a time when developers care more about design, partially because we are working more with distributed systems where models have a higher value.

  • Working with Domain Experts in a DDD World

    Conversations with domain experts and the language used are central in Domain-Driven Design (DDD), but often this is hard because we don’t speak the same language, explained Cyrille Martraire in his presentation at the Domain-Driven Design Europe conference earlier this year when sharing his experiences working with domain experts in DDD-driven environments.

  • Vaughn Vernon: Challenges in Software Development of Today

    Projects and development teams are struggling with poorly designed systems, with many developers dedicated to patching systems just to keep them alive. Largely the software development culture is broken, Vaughn Vernon claimed in his presentation at the Domain-Driven Design Europe conference earlier this year, talking about problems he has encountered but also about solutions to these problems.

  • Using Domain-Driven Design When Creating Microservices

    Microservices and Domain-Driven Design (DDD) are not only about Bounded contexts, although a fundamental tool for defining granularity of microservices there are other important concepts as well. Correspondingly DDD is just not about entities and repositories, Michael Plöd claimed in his presentation at the recent microXchg conference in Berlin showing how DDD can be used creating microservices.

  • “It’s Not Just Microservices”: Fred George Discusses Technology, Process and Organisation Inhibitors

    At the microXchg 2016 conference, Fred George presented “It’s Not Just Microservices”, and argued that microservices can enable an organisation to ‘go faster’ and rapidly deliver business value. However, the implementation of microservices alone will not lead to success, and inhibitors to increasing business agility within the context of technology, process and the organisation must be removed.

  • Road Mapping Your Way to Agile Fluency

    Kelsey van Haaster will give a talk at 1st Conference about how to develop a road map to agile fluency for teams and organisations. InfoQ interviewed her about the possible ways to do an agile fluency assessment, example of findings and improvement opportunities that came out of the assessments and things that she learned, and advice for readers who want to use the agile fluency model.

  • Software Industry Pioneer Ed Yourdon Dies

    Software industry pioneer, prolific author, researcher, consultant and photographer Edward Yourdon died on January 20, 2016

  • Combining User Story Mapping with Domain-Driven Design

    User Story Mapping can be a simple yet valuable pattern when adopting Domain-Driven Design (DDD) in projects dealing with complex domains. It can help creating shared domain knowledge among developers and domain experts, Eriksen Costa claims in a blog post discussing advantages combining User Story Mapping with Domain-Driven Design (DDD).

  • Moving from a Monolithic to a Microservices Architecture

    Moving from a monolith to microservices the only value business stakeholders care about is reducing cost. It will not increase or protect revenue and neither scaling nor distribution are good reasons that will convince the business, Ian Cooper claimed in his presentation at this year’s Microservices Conference in London describing guidelines moving from a monolith to a microservices architecture.

  • Scaling Without Blueprints and the Agile Scaling Cycle

    InfoQ interviewed Stefan Roock about adding XP practices to Scrum, why using an agile framework as a blueprint for designing the organization is a premature optimization and why culture and principles are more important than practices. Roock also explains the agile scaling cycle with examples of how it can be used, and talks about the benefits and pitfalls of this approach for agile scaling.

BT