@disqus_GtEeIZUUDN:disqus thank you. Great news, I’ve learned the Mutations and added them to my project. Way awesome! Thank you for your guidance and coaching. I’ll post a link to my blog post when I publish it.

Best regards,

Karl

Hello Karl. First of all, I am so glad you are enjoying our book, we really invested a lot of time and knowledge into it. So, hearing something like that from the reader is always the best thing.

About your question. My personal opinion is if you don’t have to use more than one request to accomplish something, don’t do it. That said, if you are using Web API to handle these POST and PUT requests, I would create required DTOs and send them back in a same request. Again, this is what I would do if I had to mix GraphQL and Web API logic (but I never did that 😀 ).

All POST and PUT operations need to be handled by Web API controllers because our business logic and workflows are super complex, which is why we don’t want to use GraphQL Mutations. Actually, we will be using MediatR for all commands.

What is your recommendation for POST and PUT operations that would typically return an update object back to the caller after the database insert or update has taken place.

I’m asking because GraphQL removes the need for many DTO objects in the code base. So we would have to create DTO objects for each POST and PUT to return. Or, do you recommend that after a POST or PUT, the Angular application use GraphQL to requery the data if required.

Thank you very much. Really like the Ultimate ASP.NET Core 3 Web API.

Karl

You are very welcome. I’m glad you enjoyed it. I hope you will find more good stuff on our site. Best regards and see you again 🙂

Thank you too mate. Have a great day. Best regards.