What is a common mistake with Service Boundaries in Microservices Architecture?

Splitting services by technical layers or database tables often creates chatty dependencies and distributed monoliths. In practice, the value of this concept comes from understanding where it belongs in the architecture, what problem it solves, and what constraints or tradeoffs it introduces.