{
  "code": null,
  "collection": "tension",
  "href": "https://banes-lab.com/ontology/schema#tension-consistency-microservices",
  "id": "consistency-microservices",
  "kind": "tension",
  "layer": null,
  "name": "Microservices / Consistency",
  "ref": "tension:consistency-microservices",
  "relations": [
    {
      "links": [
        {
          "href": "https://banes-lab.com/ontology#architecture-microservices",
          "json": "https://banes-lab.com/json/records/architecture/microservices",
          "label": "Microservices",
          "markdown": "https://banes-lab.com/records/architecture/microservices.md",
          "ref": "architecture:microservices"
        },
        {
          "href": "https://banes-lab.com/ontology#architecture-consistency",
          "json": "https://banes-lab.com/json/records/architecture/consistency",
          "label": "Consistency",
          "markdown": "https://banes-lab.com/records/architecture/consistency.md",
          "ref": "architecture:consistency"
        }
      ],
      "relation": "tensions-with"
    },
    {
      "links": [
        {
          "href": "https://banes-lab.com/ontology/schema#vocabulary-resolution-mechanism-irreducible-tradeoff",
          "json": "https://banes-lab.com/json/records/vocabulary/resolution-mechanism-irreducible-tradeoff",
          "label": "irreducible-tradeoff",
          "markdown": "https://banes-lab.com/records/vocabulary/resolution-mechanism-irreducible-tradeoff.md",
          "ref": "vocabulary:resolution-mechanism-irreducible-tradeoff"
        }
      ],
      "relation": "mechanism"
    },
    {
      "links": [
        {
          "href": "https://banes-lab.com/ontology#architecture-category-codebase-system-architecture-styles",
          "json": "https://banes-lab.com/json/ontology/principles/architecture-category-codebase-system-architecture-styles",
          "label": "Codebase / System Architecture Styles",
          "markdown": "https://banes-lab.com/ontology/principles/architecture-category-codebase-system-architecture-styles.md",
          "ref": "chapter:/ontology#architecture-category-codebase-system-architecture-styles"
        },
        {
          "href": "https://banes-lab.com/ontology/schema#the-vocabulary-resolution-mechanism",
          "json": "https://banes-lab.com/json/ontology/schema/the-vocabulary-resolution-mechanism",
          "label": "Resolution mechanisms",
          "markdown": "https://banes-lab.com/ontology/schema/the-vocabulary-resolution-mechanism.md",
          "ref": "chapter:/ontology/schema#the-vocabulary-resolution-mechanism"
        }
      ],
      "relation": "linked-from"
    }
  ],
  "summary": "\"microservices\" (structural-core layer) is traded against \"Consistency\" (atomic-boundary layer) — a principle cannot be scope-separated from a quality, metric, or cost it competes with; resolve by measuring \"Consistency\" and choosing an explicit operating point.",
  "siblings": {
    "next": {
      "href": "https://banes-lab.com/ontology/schema#tension-monolith-architecture-team-autonomy",
      "json": "https://banes-lab.com/json/records/tension/monolith-architecture-team-autonomy",
      "label": "Monolith Architecture / Team Autonomy",
      "markdown": "https://banes-lab.com/records/tension/monolith-architecture-team-autonomy.md",
      "ref": "tension:monolith-architecture-team-autonomy"
    },
    "previous": {
      "href": "https://banes-lab.com/ontology/schema#tension-microservices-operational-complexity",
      "json": "https://banes-lab.com/json/records/tension/microservices-operational-complexity",
      "label": "Microservices / Operational Complexity",
      "markdown": "https://banes-lab.com/records/tension/microservices-operational-complexity.md",
      "ref": "tension:microservices-operational-complexity"
    }
  },
  "up": {
    "href": null,
    "json": "https://banes-lab.com/json/api/records/tension",
    "label": "Tensions",
    "markdown": "https://banes-lab.com/api/records/tension.md",
    "ref": "api:records/tension"
  }
}