--- title: "Creating Contractual Service Communication" url: https://daily.dev/posts/creating-contractual-service-communication-szcd3ru50 source_url: https://engineering.monday.com/creating-contractual-service-communication type: article source: "monday Engineering" published: 2026-04-29T10:51:59.959Z updated: 2026-04-29T10:52:26.138Z tags: ["architecture", "microservices"] reading_time: 7 upvotes: 84 comments: 2 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Creating Contractual Service Communication **[monday Engineering](https://daily.dev/sources/monday)** · 7 min read · 84 upvotes · 2 comments ## Summary monday.com engineering team describes how they replaced implicit, 'stringly typed' service contracts with explicit, versioned JSON Schemas across their microservices architecture. Starting with their Reporter Service (handling ~100M daily events), they inferred initial schemas from production payloads using LLMs, iterated until achieving 100% validation rates, and centralized schemas in a Git repository. They auto-generated TypeScript interfaces and Go structs from schemas, wired compatibility checks into CI to catch breaking changes before deployment, and assigned clear ownership per schema. The result was an internal event catalogue, reduced schema-drift incidents, and a foundation for exposing internal event streams as stable public APIs. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@ntduy** · 7 upvotes > Just wonder why they don't use schema registry 🤨 --- Tags: [#architecture](https://daily.dev/tags/architecture), [#microservices](https://daily.dev/tags/microservices) [View this post on daily.dev](https://daily.dev/posts/creating-contractual-service-communication-szcd3ru50)