Why do we use DTOs in our APIs?

แชร์
ฝัง
  • เผยแพร่เมื่อ 25 พ.ย. 2024

ความคิดเห็น • 21

  • @donmikkodanm.olmillo8154
    @donmikkodanm.olmillo8154 3 ปีที่แล้ว +1

    Thank you for this video. It really helped me cleared about why we need to map it into DTOs. To put it on simple words, DTOs are much more flexible, and it is towards more on the client-side where the end user will modify or get the data. I've also heard from my mentors that you can also combine two domain models into one DTO but that is more on advanced one.

    • @Codewrinkles
      @Codewrinkles  3 ปีที่แล้ว +2

      Tes, on the DTO you can combine what ever you want. A DTO is basically an aggregate of different data that will be consumed by the clients of the API. Id doesn't have to match 1 to 1 with your domain model classes.

  • @fadidib8516
    @fadidib8516 2 ปีที่แล้ว +1

    Great Channel, I love the deep dive of information.

  • @juliancavallo
    @juliancavallo 3 ปีที่แล้ว +1

    Thank you for this video man, I always had doubts about DTOs and now it's all clear. Keep up the good work!

    • @Codewrinkles
      @Codewrinkles  3 ปีที่แล้ว +1

      I'm glad it helped you clear up the reasons why we use DTOs.

  • @alfonsdeda8912
    @alfonsdeda8912 ปีที่แล้ว

    Hi, nice video!
    Two questions:
    -I created the service class that access the database with ef core, service's methods work with entities db, this service is called from the controller in api, so should i do mapping in service or controller?
    -if i want different dtos of same object from the same controller should i do two different endpoints?
    Thanks in advance.

  • @arunbm123
    @arunbm123 2 ปีที่แล้ว

    really amazing informative Video..Thank u

  • @shaileshkuswaha1126
    @shaileshkuswaha1126 2 ปีที่แล้ว

    Such a Amazing tutorial. Thank you

  • @godfather7695
    @godfather7695 10 หลายเดือนก่อน

    11:50 you may initialize ICollection by emty List or array and there is no possible nullref ex anymore

  • @steve-o2198
    @steve-o2198 ปีที่แล้ว +1

    Using linq/list projection would be better and cleaner solution to mapping entities to dtos instead of doing loops.

  • @royvethanayagam5888
    @royvethanayagam5888 3 ปีที่แล้ว +1

    Superb.

  • @ahmedalhallag3338
    @ahmedalhallag3338 2 ปีที่แล้ว

    The cleanest video on DTOs! A sub from me

    • @Codewrinkles
      @Codewrinkles  2 ปีที่แล้ว

      I'm glad. I'm not sure why but it seems there is a lot of confusion and misunderstanding regarding DTOs. I'm happy this video cleared up some aspects for you.

  • @abdullokh_tolibjonov
    @abdullokh_tolibjonov 2 ปีที่แล้ว

    thanks a lot :) was vey useful dont stop :)

  • @abdulwahabkhan4316
    @abdulwahabkhan4316 2 ปีที่แล้ว

    very well explained :)

  • @vu5700
    @vu5700 2 ปีที่แล้ว

    Great video sir :)

  • @krisztianistvancsato5940
    @krisztianistvancsato5940 2 ปีที่แล้ว +1

    Nicely structured. Very clear. Great stuff. Thanks a lot!
    Just one question: Is there a way to connect my domain models and my dtos?
    So let's say, that I need to change some properties, for example in one of my domains.
    I'd like, if it automatically changed it in the related dto or it offered me the option. Thanks in advance.

    • @Codewrinkles
      @Codewrinkles  2 ปีที่แล้ว

      AutoMapper mapping is a one-off action. If something changes automatically in your domain model after the mapping, the change will not automatically be replicated into your DTO. If you want to achieve something like that you might need to work with evens and re-do the mapping when certain events are raised. I am not aware of anything else to achieve your goal.

    • @krisztianistvancsato5940
      @krisztianistvancsato5940 2 ปีที่แล้ว +1

      @@Codewrinkles I guess that can be an idea for a personal project, right? ;-)
      Once again, thank you very much for the excellent video.

  • @TheNefelin
    @TheNefelin 7 หลายเดือนก่อน

    is this project on GitHub?