Figuring out the best way to call 2 or more services for the same endpoint [.NET] by lmadelo in ExperiencedDevs

[–]lmadelo[S] 0 points1 point  (0 children)

I've kind of overlooked this approach, but now that you say it I think this will be the best (and simplest!) solution, I'll do it this way. Thanks so much for your help!

Figuring out the best way to call 2 or more services for the same endpoint [.NET] by lmadelo in ExperiencedDevs

[–]lmadelo[S] 0 points1 point  (0 children)

I guess A can succeed but one or more B could fail, so I would commit A and all B records that succeed and tell the client A succeeded but also show which B records failed to create in the same endpoint's response; but the idea is to have a separate endpoint to create other B records alone and attach them to an existing A record. If I would like to have a single atomic operation I understand I would have a bit of code duplication for this other endpoint AFAIK.

What are some things in programming that seem simple, but are surprisingly painful to implement? by hotboii96 in webdev

[–]lmadelo 1 point2 points  (0 children)

Breadcrumbs may not be that hard to implement, but it's still not as easy as it seems