Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    If we're designing the API to interact with our domain as per our use cases.. Why not to design things in such a way that Sagas are not required at all? Maybe I'm missing something but by reading your response I truly believe REST is not a good match with DDD and it's better to use remote procedures (RPC). DDD is behavior-centric while REST is http-verb centric. Why not to remove REST from the picture and expose the behavior (commands) in the API? After all, probably they were designed to satisfy use cases scenarios and prob are transactional. What's the advantage of REST if we own the UI? Commented Dec 2, 2019 at 8:41
  • "anti-corruption layer" is supposed to be between domains, right ? not between technical layers Commented May 19, 2023 at 8:58
  • Not necessarily? "We need to provide a translation between the parts that adhere to different models, so that the models are not corrupted by undigested elements of foreign models." "[Anticorruption layer] is a mechanism that translates conceptual objects and actions from one model and protocol to another". -- Evans 2003. I believe translating to/from the resource model to the domain model is in the spirit of this definitions. Commented May 19, 2023 at 13:17