@codewith55 Design A for internal apps.
B is textbook REST but a debugging nightmare. 4xx/5xx makes frontends freak out and pollutes logs.
Returning 200 + error code in body stops infra layers from blocking you and gives precise control over business routing.
Stability > looking pretty.
@perelin@codewith55 RESTful is great in an ideal setup. Real dev rarely is. Requirements are messy and keep changing, so sticking to REST no matter what is a time bomb waiting to go off.
@MikeTreit@codewith55 Yep. REST looks elegant on paper, but actually use it and it falls apart in a ton of real-world scenarios. RPC just works—pretty much anywhere.