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

  • Eric Evans Says Domain-Driven Design (DDD) Isn't Done

    During his keynote at Explore DDD, Eric Evans said "DDD isn't done." Over the past fifteen years since Domain-Driven Design was published, DDD hasn't stood still, and there is still much to do to keep DDD evolving.

  • 13th Annual State of Agile Survey is Open

    The 13th annual State of Agile survey has been announced by CollabNet VersionOne. This yearly survey explores the worldwide adoption of agile.

  • How No and Low Code Approaches Support Business Users and Professional Developers

    No code approaches aim to support business users in developing and maintaining their own applications, where low code simplifies the developer’s work and makes them more productive. Both approaches enable faster development at lower costs. As the distinction between these approaches is becoming smaller, business users and developers can team up and use them together.

  • Business Processes, Long-Running Services and Microservices

    During recent years domain events are increasingly being discussed, but we should be discussing commands just as much, Martin Schimak explained at the recent DDD eXchange 2018 conference, where he covered events, command and long-running services in a microservices world, and how process managers and similar tooling can help in running core business logic.

  • 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.

  • Designing Reactive Systems Using DDD, Event Storming and Actors

    Domain-driven design (DDD) is often used for finding boundaries (bounded contexts) around microservices. But everything in domain-driven design (DDD) is not good for microservice, Lutz Huehnken claimed in a presentation at microxchg 2018 in Berlin where he discussed how DDD, Event Storming and the Akka-based Lagom framework can be used to build reactive systems.

  • QCon London: Asynchronous Event Architectures with or without Actors

    Synchronous request-response communication in microservices systems can be really complicated. Fortunately, asynchronous event-based architectures can be used to avoid this, Yaroslav Tkachenko claimed in a presentation at QCon London 2018, where he described his experiences with event-driven architectures and how Actors can be used in systems built on this architecture.

  • Notes From the DDD Europe 2018 Conference

    The recently held DDD Europe 2018 conference in Amsterdam was the third in order and saw almost 700 attendees. The conference has a focus on Domain-Driven Design (DDD), and included four keynotes, 19 presentations, one track for open space and 17 sessions focused on live coding or hands-on. Notable speakers included Eric Evans, Dave Snowden, Rebecca Wirfs-Brock and Cyrille Martraire.

  • Finding Bounded Contexts Using Domain Storytelling

    When working with Domain-Driven Design (DDD), bounded context is a core concept. Domain storytelling is a way of finding how people and systems work together within a domain which then can be used to identify the bounded contexts and how they are interconnected, Stefan Hofer and Henning Schwentner explained at the recent DDD Europe 2018 conference in Amsterdam.

  • Retroactive and Future Events in an Event Sourced System

    When Thomas Pierrain started a new project with an asset management company, one important requirement was the ability to go back in time to understand why they took decisions that today look strange. At the recent DDD Europe 2018 conference in Amsterdam, Pierrain discussed his experiences when building an event sourced system that included some temporal challenges.

  • Evolving CQRS and Event Sourced Systems

    After talking with people about upgrading of CQRS and event sourced systems, Michiel Overeem came to the conclusion that many working with event sourced systems lack an understanding and don’t know how to approach the problem. At the recent DDD Europe 2018 conference in Amsterdam he described how this was a trigger for him to do an exploratory research on how to evolve this kind of system.

  • Eric Evans: Practicing Domain-Driven Design

    For Eric Evans, who gave a keynote at the recent DDD Europe 2018 conference in Amsterdam, it’s important to explore and practice building software. He enjoys working with strategic patterns in Domain-Driven Design (DDD), but what he finds really interesting is taking a difficult domain and reason about it differently; breaking out of the mental box trying to find new concepts.

  • Firefox Quantum Commits to Cross-Browser Extension Architecture

    With the Firefox 57 “Quantum” release, Firefox now only supports extensions based on the WebExtensions API, joining Chrome and Edge in supporting extension development with pure HTML, CSS, and JavaScript based on a cross-browser shared extension architecture.

  • Selecting an Event Architecture

    When designing a distributed system, maybe based on microservices, and you are considering an event architecture, there are several models and technologies available. When choosing how to implement the architecture the non-functional requirements are a main factor, David Dawson claims when describing different styles of event architectures in a recent blog post.

  • First Annual Retrospective Report Published

    The First Annual Retrospective Report provides a deeper understanding of how retrospectives are used in the real world. The results indicate that retrospectives lead to improved team communication and productivity and help to create an environment of trust. Major challenges are that topics discussed cannot be solved by the team and people do not feel comfortable speaking up.

BT