Это видео недоступно.
Сожалеем об этом.

API Platform Conference 2022 - M. Arlaud & R. Chalas - Domain-driven design with API Platform 3

Поделиться
HTML-код
  • Опубликовано: 19 окт 2022
  • At Les-Tilleuls.coop, we like to use API Platform. Mainly because it addresses a lot of questions about web API design, but also for its ease of use. This simplicity, however, comes with a cost that is generally felt when you need to get out of the box.
    Fact is that at Les-Tilleuls.coop we also enjoy working on applications with strong business constraints, and even more to get off the rails. And when appropriate, we do so based on the DDD principles.
    Hexagonal message-oriented architecture, business logic decoupled from the infrastructure, … So many precepts that become prerequisites when it comes to putting the business at the center of our applications while ensuring their good maintainability.
    _________
    More info: api-platform.c...
    Twitter: / apiplatform
    Music credits: Vanilla by Time Warp

Комментарии • 7

  • @abdelilahaassou6333
    @abdelilahaassou6333 Год назад +1

    Great presentation guys, really full of information.
    Thank you!

  • @josuenguimatio
    @josuenguimatio Год назад +2

    Hi !
    and about migration for entities ?
    in which folder , are we going to place them ?

  • @user-lv4fy5qr7c
    @user-lv4fy5qr7c Год назад +1

    Thanks for the video!
    I have a couple of questions:
    1. in github repo you've provided as example, the domain models contains Doctrine mapping annotations. don't you consider that as a violation of dependency rule?
    2. as I remember, Api-platform is trying to serialize and pre-validate mapped entities before actual validation constraints. Doesn't that means that infrastructure layer can affect the domain business logic?
    Thank you.

    • @coopTilleuls
      @coopTilleuls  Год назад

      Robin speaking:
      Hi,
      1: It’s a tradeoff, see matthiasnoback.nl/2020/09/violating-the-dependency-rule/ and matthiasnoback.nl/2022/04/ddd-entities-and-orm-entities/
      Also as Mathias said: attributes are purely declarative (code doesn’t break if doctrine is not installed) so it's "soft" coupling.
      2. Not in this case since our Api Resources aren’t entities but plain-old data objects located at the infra layer.
      Btw, here are the materials: speakerdeck.com/mtarld/api-platform-con-domain-driven-design-with-api-platform-3.

  • @oOShaoOo
    @oOShaoOo Год назад +2

    Thanks for this conf. Can you give me the GitHub repo, I can't read it at the end of the video.

    • @coopTilleuls
      @coopTilleuls  Год назад +4

      Hello, check this out: github.com/mtarld/apip-ddd

  • @issussov
    @issussov Год назад

    You got it all wrong. Both DDD and CQRS. I would advice you to rethink how you look at Infrastructure layer. Same for what is actually a domain service and its purpose.