home.social

#hexagonalarchitecture — Public Fediverse posts

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

fetched live
  1. Frameworks change. Databases change. Messaging changes. Your business logic shouldn't have to. Marek Dominiak & Vadzim Prudnikau explain how #HexagonalArchitecture helps isolate infrastructure concerns while keeping apps easier to evolve & test: javapro.io/2026/07/14/do-you-s

    #Java

  2. Frameworks change. Databases change. Messaging changes. Your business logic shouldn't have to. Marek Dominiak & Vadzim Prudnikau explain how #HexagonalArchitecture helps isolate infrastructure concerns while keeping apps easier to evolve & test: javapro.io/2026/07/14/do-you-s

    #Java

  3. Still debugging business logic spread across controllers, services & repositories? That’s how maintainable systems turn into spaghetti code. @quiquemmonte shows how #HexagonalArchitecture keeps #Java systems decoupled & testable.

    Read now: javapro.io/2026/05/27/from-spa

    #DDD @ArchUnit

  4. Still debugging business logic spread across controllers, services & repositories? That’s how maintainable systems turn into spaghetti code. @quiquemmonte shows how #HexagonalArchitecture keeps #Java systems decoupled & testable.

    Read now: javapro.io/2026/05/27/from-spa

    #DDD @ArchUnit

  5. A lot of #CleanArchitectures collapse once frameworks, persistence & business rules leak into each other. Refactoring gets expensive fast.

    @quiquemmonte breaks down pragmatic #HexagonalArchitecture for real-world #Java systems:
    javapro.io/2026/05/27/from-spa

    #DDD @ArchUnit

  6. A lot of #CleanArchitectures collapse once frameworks, persistence & business rules leak into each other. Refactoring gets expensive fast.

    @quiquemmonte breaks down pragmatic #HexagonalArchitecture for real-world #Java systems:
    javapro.io/2026/05/27/from-spa

    #DDD @ArchUnit

  7. Still debugging business logic spread across controllers, services & repositories? That’s how maintainable systems turn into spaghetti code. Enrique Medina Montenegro shows how #HexagonalArchitecture keeps #Java systems decoupled & testable,.

    Read now: javapro.io/2026/05/27/from-spa

    #DDD @ArchUnit

  8. Still debugging business logic spread across controllers, services & repositories? That’s how maintainable systems turn into spaghetti code. Enrique Medina Montenegro shows how #HexagonalArchitecture keeps #Java systems decoupled & testable,.

    Read now: javapro.io/2026/05/27/from-spa

    #DDD @ArchUnit

  9. Warum brechen Änderungen in klassischen Layer-Architekturen bis ins UI durch? @quiquemmonte erklärt Ports, Adapter & den „Kern nach innen“-Ansatz, der genau das verhindert.

    Stoppe den Cascade-Effekt: javapro.io/de/von-spaghetti-zu

    #HexagonalArchitecture #DDD #Java @springframework

  10. Warum brechen Änderungen in klassischen Layer-Architekturen bis ins UI durch? @quiquemmonte erklärt Ports, Adapter & den „Kern nach innen“-Ansatz, der genau das verhindert.

    Stoppe den Cascade-Effekt: javapro.io/de/von-spaghetti-zu

    #HexagonalArchitecture #DDD #Java @springframework

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

  12. Un gros merci à @sroccaserra pour son article sur les terminologies d'architecture hexagonale, clean architecture, layers, DDD, etc.

    blog.octo.com/application-doma

    La distinction entre "domaine", "business logic", "service" et "application" m'a toujours rendu confus car à chaque fois, les gens parlaient d'autre chose.

    Le passage par l'historique rend les choses plus claires et précises.

    #ddd #HexagonalArchitecture #SoftwareCraft #code #dev

  13. Un gros merci à @sroccaserra pour son article sur les terminologies d'architecture hexagonale, clean architecture, layers, DDD, etc.

    blog.octo.com/application-doma

    La distinction entre "domaine", "business logic", "service" et "application" m'a toujours rendu confus car à chaque fois, les gens parlaient d'autre chose.

    Le passage par l'historique rend les choses plus claires et précises.

    #ddd #HexagonalArchitecture #SoftwareCraft #code #dev

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

  15. Warum brechen Änderungen in klassischen Layer-Architekturen bis ins UI durch? @quiquemmonte erklärt Ports, Adapter & den „Kern nach innen“-Ansatz, der genau das verhindert.

    Stoppe den Cascade-Effekt: javapro.io/de/von-spaghetti-zu

    #HexagonalArchitecture #DDD #Java @springframework

  16. Warum brechen Änderungen in klassischen Layer-Architekturen bis ins UI durch? @quiquemmonte erklärt Ports, Adapter & den „Kern nach innen“-Ansatz, der genau das verhindert.

    Stoppe den Cascade-Effekt: javapro.io/de/von-spaghetti-zu

    #HexagonalArchitecture #DDD #Java @springframework

  17. I really, really like Alistair's pragmatic presentation on Hexagonal Architecture. 4m30s – everything that makes up its core in one slide: interfaces to separate technical code from business logic, connected via dependency injection. A model Spring application developers have followed since the time HA was described without explicitly calling it that. youtube.com/watch?v=ChUlRa0xsWo #hexagonalarchitecture

    1/4

  18. I really, really like Alistair's pragmatic presentation on Hexagonal Architecture. 4m30s – everything that makes up its core in one slide: interfaces to separate technical code from business logic, connected via dependency injection. A model Spring application developers have followed since the time HA was described without explicitly calling it that. youtube.com/watch?v=ChUlRa0xsWo #hexagonalarchitecture

    1/4

  19. "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

  20. "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

  21. I had an extremely good refactoring session yesterday in our Scala code base, breaking a big chunk of mangled logic into the pure logic, its supporting IO/effects, and a data structure describing the commands from the first to the second.

    Basic practice (#hexagonalArchitecture , #effectManagement, etc), but it worked out very well and it's always astonishing how much it simplifies and bring clarity to complex code, and make it testable

    #scala

  22. I had an extremely good refactoring session yesterday in our Scala code base, breaking a big chunk of mangled logic into the pure logic, its supporting IO/effects, and a data structure describing the commands from the first to the second.

    Basic practice (#hexagonalArchitecture , #effectManagement, etc), but it worked out very well and it's always astonishing how much it simplifies and bring clarity to complex code, and make it testable

    #scala

  23. I will be leading a hands-on workshop at dddeurope.com on June 4th!

    Implement core DDD concepts including Aggregates, Repositories, Value Objects, and use Hexagonal Architecture for loose coupling. In Java and Python.

    #DomainDrivenDesign #HexagonalArchitecture #DDDEurope

  24. I will be leading a hands-on workshop at dddeurope.com on June 4th!

    Implement core DDD concepts including Aggregates, Repositories, Value Objects, and use Hexagonal Architecture for loose coupling. In Java and Python.

  25. Nobody want to be a shitty programmer. The question is: Do you do anything not to not be one?
    Reading blogs or social media and watching YouTube videos is fun. After them, your code may be a little better, of course. But you need a lot. You need to study! Read good books and study the code of other programmers, for example. Maybe work with a new language, architectures and paradigms. You need break the routine.

    If you know Object-oriented programming, you learn functional programming.
    If you know Model-View-Controller, you learn Model-View-ViewModel.
    If you don't know anything about architectures, you learn Clean Architecture, Hexagonal Architecture, etc.
    If you know Python, you learn Ruby or Go.
    If you know Clojure or Lisp... you don't need to learn anything else. You are already a good programmer. Just kidding. You can learn Elixir or Scala.

    Be a good programmer my friend.

    #Programmin #OOP #FunctionalProgramming #MVC #MVVM #CleanArchitecture #HexagonalArchitecture #Python #RubyLang #Golang #Clojure #Lisp #ElixirLang #Scala

  26. Nobody want to be a shitty programmer. The question is: Do you do anything not to not be one?
    Reading blogs or social media and watching YouTube videos is fun. After them, your code may be a little better, of course. But you need a lot. You need to study! Read good books and study the code of other programmers, for example. Maybe work with a new language, architectures and paradigms. You need break the routine.

    If you know Object-oriented programming, you learn functional programming.
    If you know Model-View-Controller, you learn Model-View-ViewModel.
    If you don't know anything about architectures, you learn Clean Architecture, Hexagonal Architecture, etc.
    If you know Python, you learn Ruby or Go.
    If you know Clojure or Lisp... you don't need to learn anything else. You are already a good programmer. Just kidding. You can learn Elixir or Scala.

    Be a good programmer my friend.

    #Programmin #OOP #FunctionalProgramming #MVC #MVVM #CleanArchitecture #HexagonalArchitecture #Python #RubyLang #Golang #Clojure #Lisp #ElixirLang #Scala

  27. What is hexagonal architecture, and how can it help to make your code more testable? In this Making Tech Better podcast episode, I spoke to @jitterted about the benefits and principles of hexagonal architecture, and how it enables you to keep your domain logic independent from the outside world.

    You can listen here: youtube.com/watch?v=zpITtO-5d-

    #CSudberyRecordings #HexagonalArchitecture

  28. What is hexagonal architecture, and how can it help to make your code more testable? In this Making Tech Better podcast episode, I spoke to @jitterted about the benefits and principles of hexagonal architecture, and how it enables you to keep your domain logic independent from the outside world.

    You can listen here: youtube.com/watch?v=zpITtO-5d-

    #CSudberyRecordings #HexagonalArchitecture

  29. 🥁📢 #jMolecules 2023.3.0 (API 1.10, Integrations 0.25) is out! Improved #HexagonalArchitecture verification and persistence code generation. See the release announcement for details. github.com/xmolecules/jmolecul ☕️⚗️

  30. 🥁📢 #jMolecules 2023.3.0 (API 1.10, Integrations 0.25) is out! Improved #HexagonalArchitecture verification and persistence code generation. See the release announcement for details. github.com/xmolecules/jmolecul ☕️⚗️

  31. 1) Understand the domain
    2) Domain modelling (#ModelInCode)
    3) Let a test drive us (#TDD)
    4) Implement the controller
    5) Drive the core implementation by a test (TDD again)
    6) Extend the business logic facade (#HexagonalArchitecture)
    7) Implement the command
    8) Implement the event projection (#EventSourcing)
    9) Implement the database access (#OnionArchitecture)
    10) Release it (#CI_CD)
    11) See your changes at work (#REPL #FSI)

    With code samples in #dotnet

  32. I just finished Alistair Cockburns book on #HexagonalArchitecture – I'm convinced that this pattern is highly applicable to my future projects and that fully capturing it will make me a better dev.
    Maybe you too?
    store7710079.company.site/Hexa