home.social

#portsandadapters — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #portsandadapters, aggregated by home.social.

fetched live
  1. Hexagonal Architecture begegnet dir früher oder später, wenn Anwendungen größer werden und trotzdem wartbar bleiben sollen. Der Name klingt komplizierter, als das Konzept tatsächlich ist. Im Kern geht es darum, Abhängigkeiten sauber zu trennen und dein fachliches Modell vor technischen Details

    magicmarcy.de/fachlogik-zuerst

    #PortsAndAdapters #Hexagonal #Architektur #HexagonalArchitecture #Fachlogik #Service #Schnittstellen

  2. Hexagonal Architecture begegnet dir früher oder später, wenn Anwendungen größer werden und trotzdem wartbar bleiben sollen. Der Name klingt komplizierter, als das Konzept tatsächlich ist. Im Kern geht es darum, Abhängigkeiten sauber zu trennen und dein fachliches Modell vor technischen Details

    magicmarcy.de/fachlogik-zuerst

    #PortsAndAdapters #Hexagonal #Architektur #HexagonalArchitecture #Fachlogik #Service #Schnittstellen

  3. Hexagonal Architecture begegnet dir früher oder später, wenn Anwendungen größer werden und trotzdem wartbar bleiben sollen. Der Name klingt komplizierter, als das Konzept tatsächlich ist. Im Kern geht es darum, Abhängigkeiten sauber zu trennen und dein fachliches Modell vor technischen Details

    magicmarcy.de/fachlogik-zuerst

    #PortsAndAdapters #Hexagonal #Architektur #HexagonalArchitecture #Fachlogik #Service #Schnittstellen

  4. Hexagonal Architecture begegnet dir früher oder später, wenn Anwendungen größer werden und trotzdem wartbar bleiben sollen. Der Name klingt komplizierter, als das Konzept tatsächlich ist. Im Kern geht es darum, Abhängigkeiten sauber zu trennen und dein fachliches Modell vor technischen Details

    magicmarcy.de/fachlogik-zuerst

    #PortsAndAdapters #Hexagonal #Architektur #HexagonalArchitecture #Fachlogik #Service #Schnittstellen

  5. Hexagonal Architecture begegnet dir früher oder später, wenn Anwendungen größer werden und trotzdem wartbar bleiben sollen. Der Name klingt komplizierter, als das Konzept tatsächlich ist. Im Kern geht es darum, Abhängigkeiten sauber zu trennen und dein fachliches Modell vor technischen Details

    magicmarcy.de/fachlogik-zuerst

    #PortsAndAdapters #Hexagonal #Architektur #HexagonalArchitecture #Fachlogik #Service #Schnittstellen

  6. "You can draw a line around any part of your code and call it anything you like, but only when you have to maintain the tests do boundaries become real."

    “Hexagonal Architecture Explained” Alistair Cockburn & Juan Manuel Garrido de Paz

    #hexagonalarchitecture #portsandadapters #testing

  7. "You can draw a line around any part of your code and call it anything you like, but only when you have to maintain the tests do boundaries become real."

    “Hexagonal Architecture Explained” Alistair Cockburn & Juan Manuel Garrido de Paz

    #hexagonalarchitecture #portsandadapters #testing

  8. "You can draw a line around any part of your code and call it anything you like, but only when you have to maintain the tests do boundaries become real."

    “Hexagonal Architecture Explained” Alistair Cockburn & Juan Manuel Garrido de Paz

    #hexagonalarchitecture #portsandadapters #testing

  9. "You can draw a line around any part of your code and call it anything you like, but only when you have to maintain the tests do boundaries become real."

    “Hexagonal Architecture Explained” Alistair Cockburn & Juan Manuel Garrido de Paz

    #hexagonalarchitecture #portsandadapters #testing

  10. xUnit Test Patterns: Contract Test — zalas.pl/contract-test/

    Contract Tests are examples that describe the behaviour of an abstraction by expressing what cannot be encoded in the type system. These are typically helpful in testing adapters as defined in the Ports & Adapters architecture.

    Examples in #kotlin, but the pattern is universal.

    #contracttests #xunit #testing #hexagonal #portsandadapters

  11. xUnit Test Patterns: Contract Test — zalas.pl/contract-test/

    Contract Tests are examples that describe the behaviour of an abstraction by expressing what cannot be encoded in the type system. These are typically helpful in testing adapters as defined in the Ports & Adapters architecture.

    Examples in #kotlin, but the pattern is universal.

    #contracttests #xunit #testing #hexagonal #portsandadapters

  12. xUnit Test Patterns: Contract Test — zalas.pl/contract-test/

    Contract Tests are examples that describe the behaviour of an abstraction by expressing what cannot be encoded in the type system. These are typically helpful in testing adapters as defined in the Ports & Adapters architecture.

    Examples in #kotlin, but the pattern is universal.

    #contracttests #xunit #testing #hexagonal #portsandadapters

  13. xUnit Test Patterns: Contract Test — zalas.pl/contract-test/

    Contract Tests are examples that describe the behaviour of an abstraction by expressing what cannot be encoded in the type system. These are typically helpful in testing adapters as defined in the Ports & Adapters architecture.

    Examples in #kotlin, but the pattern is universal.

    #contracttests #xunit #testing #hexagonal #portsandadapters

  14. I'm searching for a new professional opportunity from February on, an earlier start is possible but I'm not in a rush!
    I bring along 25+ years of experience as a software developer, architect, team lead, learning designer (trainer).

    Please share! :-)

    Some of my skills and interests:
    #golang #dddesign #hexagonal #portsandadapters #collaboration #agile #eventsourcing #cqrs

  15. I'm searching for a new professional opportunity from February on, an earlier start is possible but I'm not in a rush!
    I bring along 25+ years of experience as a software developer, architect, team lead, learning designer (trainer).

    Please share! :-)

    Some of my skills and interests:
    #golang #dddesign #hexagonal #portsandadapters #collaboration #agile #eventsourcing #cqrs

  16. I'm searching for a new professional opportunity from February on, an earlier start is possible but I'm not in a rush!
    I bring along 25+ years of experience as a software developer, architect, team lead, learning designer (trainer).

    Please share! :-)

    Some of my skills and interests:
    #golang #dddesign #hexagonal #portsandadapters #collaboration #agile #eventsourcing #cqrs

  17. I'm searching for a new professional opportunity from February on, an earlier start is possible but I'm not in a rush!
    I bring along 25+ years of experience as a software developer, architect, team lead, learning designer (trainer).

    Please share! :-)

    Some of my skills and interests:
    #golang #dddesign #hexagonal #portsandadapters #collaboration #agile #eventsourcing #cqrs

  18. Estuve hablando sobre mis experiencias con la arquitectura hexagonal, y que pasa cuando se mal entiende/aplica.

    Me lo pasé bien la verdad 😄

    #HexagonalArchitecture #PortsAndAdapters
    youtu.be/ZlfepC5EsZM?si=-HBIKr

  19. Estuve hablando sobre mis experiencias con la arquitectura hexagonal, y que pasa cuando se mal entiende/aplica.

    Me lo pasé bien la verdad 😄

    #HexagonalArchitecture #PortsAndAdapters
    youtu.be/ZlfepC5EsZM?si=-HBIKr

  20. Estuve hablando sobre mis experiencias con la arquitectura hexagonal, y que pasa cuando se mal entiende/aplica.

    Me lo pasé bien la verdad 😄

    #HexagonalArchitecture #PortsAndAdapters
    youtu.be/ZlfepC5EsZM?si=-HBIKr

  21. Estuve hablando sobre mis experiencias con la arquitectura hexagonal, y que pasa cuando se mal entiende/aplica.

    Me lo pasé bien la verdad 😄

    #HexagonalArchitecture #PortsAndAdapters
    youtu.be/ZlfepC5EsZM?si=-HBIKr

  22. @ArmouredWizard Maybe #domaindrivendesign and therefore #PortsAndAdapters or architecture is something for you? If you a have a sufficient complex domain logic and the need of a separate UI and database model it maybe a good way. But if you have a simple app... I think its too heavy. My advice: Start simple and let space for further refactorings and model separations. Or start separated and refactor it further together. It's always simpler to move something together than to separate it later.

  23. @ArmouredWizard Maybe #domaindrivendesign and therefore #PortsAndAdapters or architecture is something for you? If you a have a sufficient complex domain logic and the need of a separate UI and database model it maybe a good way. But if you have a simple app... I think its too heavy. My advice: Start simple and let space for further refactorings and model separations. Or start separated and refactor it further together. It's always simpler to move something together than to separate it later.

  24. @ArmouredWizard Maybe #domaindrivendesign and therefore #PortsAndAdapters or architecture is something for you? If you a have a sufficient complex domain logic and the need of a separate UI and database model it maybe a good way. But if you have a simple app... I think its too heavy. My advice: Start simple and let space for further refactorings and model separations. Or start separated and refactor it further together. It's always simpler to move something together than to separate it later.

  25. herbertograca.com/2017/11/16/e… and the posts before it explore the territory of the different-or-not-so-different application layer separation architectures named by various authors "Ports and Adapters" ("Hexagonal"), "Onion" and "Clean". It also ties these into DDD and CQRS, and how the various named concepts across these methodologies overlap and correspond to each other.

    I haven't read the series from beginning to end, but it usually shows up when I want to refresh myself on the terminologies, as it has it all in one place.

    #HexagonalArchitecture #PortsAndAdapters #PortsAndAdaptersArchitecture #CleanArchitecture #OnionArchitecture #DDD #CQRS


    DDD, Hexagonal, Onion, Clean, CQRS, … How I put it all together
  26. herbertograca.com/2017/11/16/e… and the posts before it explore the territory of the different-or-not-so-different application layer separation architectures named by various authors "Ports and Adapters" ("Hexagonal"), "Onion" and "Clean". It also ties these into DDD and CQRS, and how the various named concepts across these methodologies overlap and correspond to each other.

    I haven't read the series from beginning to end, but it usually shows up when I want to refresh myself on the terminologies, as it has it all in one place.

    #HexagonalArchitecture #PortsAndAdapters #PortsAndAdaptersArchitecture #CleanArchitecture #OnionArchitecture #DDD #CQRS


    DDD, Hexagonal, Onion, Clean, CQRS, … How I put it all together