Breaking News: Grepper is joining You.com. Read the official announcement!
Check it out

Identifying anemic domains

Pragya Keshap answered on February 19, 2023 Popularity 1/10 Helpfulness 1/10

Contents


More Related Answers

  • The anemic domain model
  • Identifying the fat domains

  • Identifying anemic domains

    0

    Microservices that do not have a sufficiently mature business layer to solve their own tasks are examples of software built on an anemic domain.

    The identification of an anemic domain can be done by making a few simple observations:

    The microservice cannot perform the tasks itself with only the data received

    The microservice needs to fetch data in more than one endpoint to perform a task

    The microservice does not have a self-sufficient entity model

    The microservice waits for the completion of a task in another microservice to follow up what you need to do

    The microservice needs to share resources with other external microservices; these resources can be cached to the sample database

    If the microservice being developed is one of those items, then it can be a weak area. If a microservice has two or more characteristics of those listed, then it is definitely an anemic domain.

    Anemic domains are very harmful to the microservices ecosystem, because they have a tendency to be multiplied in order to correct the technical debt generated by the deficiency in the composition of their respective domains.

    Popularity 1/10 Helpfulness 1/10 Language whatever
    Source: Grepper
    Tags: whatever
    Link to this answer
    Share Copy Link
    Contributed on Feb 19 2023
    Pragya Keshap
    0 Answers  Avg Quality 2/10


    X

    Continue with Google

    By continuing, I agree that I have read and agree to Greppers's Terms of Service and Privacy Policy.
    X
    Grepper Account Login Required

    Oops, You will need to install Grepper and log-in to perform this action.