Best of Domain-Driven Design2023

  1. 1
    Article
    Avatar of syscolabsslSysco LABS Sri Lanka·3y

    The Art of Micro Frontends

    The Art of Micro Frontends is a modular architecture design for web. The concept of micro frontends is an extension of the micro services used in backend. Companies such as Netflix, Zalando and Capital One have pushed the pattern to the front, preparing the groundwork for micro-frontends.

  2. 2
    Article
    Avatar of discdotDiscover .NET·3y

    Why is Clean Architecture so Popular?

    Clean Architecture is a way to manage coupling between software modules ISO/IEC/IEEE 24765:2010 Systems and software engineering — Vocabulary There are two forms of coupling Clean Architecture addresses. In.NET, projects were used in the template above to force the separation. However, you do not need separate projects.

  3. 3
    Article
    Avatar of codemotionCodemotion·3y

    What Are Microservices Design Patterns?

    Microservice architecture is an organizational approach to software development where the programmer has to use a collection of small autonomous services. As autonomous services, they are able to complete certain functions independently from other services with which it interacts. Microservices use two types of load-balancing architecture, and these are server-side load balancing.

  4. 4
    Article
    Avatar of towardsdevTowards Dev·3y

    Microservice decomposition Patterns

    Learn about different microservice decomposition patterns, such as Domain-Driven Design (DDD), API Gateway, and Backend for Frontend (BFF). Each pattern has its own advantages and disadvantages, and the best pattern(s) to use will depend on the specific requirements of your application.

  5. 5
    Article
    Avatar of discdotDiscover .NET·3y

    "Clean Architecture" and indirection. No thanks.

  6. 6
    Article
    Avatar of cloudnativedailyCloud Native Daily·3y

    Microservices Patterns: Business Service Patterns

    Hexagonal Architecture is an architectural pattern used in software architecture design. It aims at creating loosely coupled application components that can be easily connected to their software environment by means of ports and adapters. In this blog, I will try to emphasize those differences by revisiting some of the core design patterns and principles built into each architecture.

  7. 7
    Article
    Avatar of communityCommunity Picks·3y

    Domain Driven Design

    Domain Driven Design is an approach to software development that focuses on understanding and modelling the core domain of a business or problem space. The main goal of DDD is to create software systems that closely align with the complex, evolving needs of domain experts and stakeholders.

  8. 8
    Article
    Avatar of sitepenSitePen·3y

    Software & Data Architecture: Part 1

    The definitions of 'information architecture' and 'data architecture' are pretty broad. They cover many areas of systems engineering and are applicable across several disciplines, including the design of business processes, user experiences, and software implementations. This article focuses on a few areas that often get overlooked as to their value.

  9. 9
    Article
    Avatar of communityCommunity Picks·3y

    Getting Used To Microservices

    Microservices have built their software as many separate services, communicating through well-defined networked interfaces. With the service-based design, - The data is all over the place; - It is difficult to diagnose functionality that spans many services. - Refactoring system design becomes expensive; and - There is dead code nobody knows is dead.

  10. 10
    Article
    Avatar of communityCommunity Picks·3y

    In a nutshell: What are DDD and CQRS (Domain Driven Design and Command Query Responsibility Segregation)?

    Domain-Driven Design (DDD) is a software development approach that involves close collaboration between developers and domain experts. The goal is to design software that is well-suited for the business domain it will be used in. DDD introduces concepts and techniques, such as domain models, bounded contexts, and context maps.

  11. 11
    Article
    Avatar of discdotDiscover .NET·3y

    Domain Modeling Gone Wrong

  12. 12
    Article
    Avatar of discdotDiscover .NET·3y

    CRUD can be Terrible. Start capturing INTENT!

  13. 13
    Article
    Avatar of itnextITNEXT·3y

    Decouple your Laravel code using Attribute Events

    Learn how to decouple your Laravel code using Attribute Events. By using events, you can easily handle data modification and initiate processes after a modification, resulting in scalable and maintainable code.

  14. 14
    Article
    Avatar of discdotDiscover .NET·3y

    Essence of Domain-Driven Design (DDD)

    Domain-driven design (DDD) aims to tackle the inherent complexity of business rules and processes in software development. It focuses on understanding the domain and its language, and provides tools and techniques to model the behavior of the system. Event storming is a popular technique used in DDD to map out business processes and identify boundaries and handoffs. Implementing DDD requires considering the specific language, frameworks, and team dynamics, and understanding the context and value of applying patterns.

  15. 15
    Article
    Avatar of discdotDiscover .NET·3y

    DDD is just giving a $h!t about your Domain

  16. 16
    Article
    Avatar of discdotDiscover .NET·3y

    Events are an API. Treat them that way!

  17. 17
    Article
    Avatar of colkgirlCode Like A Girl·3y

    Ports and adapters in Python-Domain Driven Design patterns

    Ports and Adapters in Python-Domain Driven Design patterns are an architectural pattern for building loosely coupled and maintainable applications. The application core consists of the business logic, which can be tested independently of the infrastructure. The adapters provide the interfaces to connect the core with the external world.

  18. 18
    Article
    Avatar of hackernoonHacker Noon·3y

    A Comprehensive Guide to Approaching Package Organization in Go

    This post provides different project layout types for organizing code in Go. It discusses the flat structure, grouping by function (anti-pattern), grouping by module (anti-pattern), and grouping by context using Domain Driven Design (DDD) and Hexagonal Architecture. The post recommends considering the specific requirements of the project and maintaining consistency while organizing code in Go.