---
title: "Discussion on \"Modeling \"who calls this endpoint\" as a graph of teams\" | Hashnode"
description: "Discussion on \"Modeling \"who calls this endpoint\" as a graph of teams\". Teams, services and endpoints as a small graph that answers who a change affects, what a team depends on, and what nobody owns."
url: "https://hashnode.com/posts/modeling-who-calls-this-endpoint-as-a-graph-of-teams/6af8b0c07916b7b7dbc7c6e0"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Modeling "who calls this endpoint" as a graph of teams](https://graphwake.hashnode.dev/modeling-who-calls-this-endpoint-as-a-graph-of-teams?utm_source=hashnode&utm_medium=feed)

Teams, services and endpoints as a small graph that answers who a change affects, what a team depends on, and what nobody owns.

16h ago · 12 min read · graphwake.hashnode.dev  
Read the article

-   [#apis](https://hashnode.com/tag/apis)
-   [#architecture](https://hashnode.com/tag/architecture)
-   [#database](https://hashnode.com/tag/database)
-   [#microservices](https://hashnode.com/tag/microservices)

## Written by

[Graphwake](https://hashnode.com/@graphwake)

@graphwake · Vancouver, Canada

  
[View profile](https://hashnode.com/@graphwake)

Founder of Graphwake. API changes between teams.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.