---
title: "Discussion on \"Where Should Request Validation Live in a TypeScript Application?\" | Hashnode"
description: "Discussion on \"Where Should Request Validation Live in a TypeScript Application?\". Explore why validation belongs at the application boundary, how pipelines separate validation from HTTP, and how Xeno.JS implements this approach."
url: "https://hashnode.com/posts/where-should-request-validation-live-in-a-typescript-application/6ac64239a72b603c8c0dbf15"
---

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

Discussion

# [Where Should Request Validation Live in a TypeScript Application?](https://xeno-js.hashnode.dev/where-should-request-validation-live-in-a-typescript-application?utm_source=hashnode&utm_medium=feed)

Explore why validation belongs at the application boundary, how pipelines separate validation from HTTP, and how Xeno.JS implements this approach.

Oct 7 · 10 min read · xeno-js.hashnode.dev  
Read the article

-   [#nodejs](https://hashnode.com/tag/nodejs)
-   [#typescript](https://hashnode.com/tag/typescript)
-   [#validation](https://hashnode.com/tag/validation)
-   [#cqrs](https://hashnode.com/tag/cqrs)
-   [#ddd](https://hashnode.com/tag/ddd)
-   [#framework](https://hashnode.com/tag/framework)
-   [#opensource](https://hashnode.com/tag/opensource)
-   [#zod](https://hashnode.com/tag/zod)

## Written by

[Mattia Carcione](https://hashnode.com/@xeno-js)

@xeno-js

  
[View profile](https://hashnode.com/@xeno-js)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
