How to Implement REPR Pattern in ASP NET Core Web API

[@CodeMaze]

Thank you all for watching and for your support. ►► If you want to check out all our courses you can do that here: bit.ly/cdmz-courses

[@Skwerzmernerpl]

REPR lends itself to vertical slice architecture very well; it makes more sense to have your request/response records defined in the same file as the endpoint they pertain to since they should be used anywhere else and they'll be immediately visible when working within the endpoint file.

[@CodeMaze]

I really don't kike having multiple classes/records in the same file, especially when those records are DTOs. If for example you have a client Blazor apo consuming your API, I would even place them in a separate project and share that project with a Blazor client app in order to avoid double file creation both on the client and the server.

[@lexNwimue]

Thanks for sharing. Simple and straight to the point

[@CodeMaze]

You are very welcome.

[@novaploca2080]

Interesting, thanks for this. :)

[@CodeMaze]

You are very welcome. Thank you too for watching the video.

[@TeemoPwnstar]

I really dislike the repr pattern personally. Thank you for the video though - it was well presented (even for a subjectively 'bad' pattern :D)

[@CodeMaze]

Well, it is kind a interesting for me, but currently, I don't think I would go this way unless asked for... but again, it is not something I will just throw away, it looks interesting enough. Thank you very much for watching the video and the comment.

[@k2an]

I trhink i am the one hate clean arch. and like clean arch approaches. you arent make things ez maintainable just 1 entity you create alot of folder files bla bla . btw thanks for your time

[@CodeMaze]

First, you are welcome and thank you for watching the video. Second, you are not the only one, trust me on that :) If you watched the video untill the end, you probably have seen me asking the same question. But I must admit, I like architectural approaches :)

[@k2an]

@@CodeMaze I like architectural approc. also but nowadays everyone starts projects with this like patterns. these all microservices fault :) after this everyone starts ms for their basic applications. again thanks for video

[@CodeMaze]

Overengineering was always a problem in software development, I completely understand your point there :)