---
title: "Comment by Lavadera Ruttinger on \"Step-by-Step Approach to Use Onion Architecture in .NET\" | Hashnode"
description: "Great walkthrough of the implementation steps! When applying this to a domain with complex validation rules, do you typically keep those rules within the entity"
url: "https://hashnode.com/posts/step-by-step-approach-to-use-onion-architecture-in-net/67e98fe33beb1a0497ba6e38/comment/69d6ff5b6be3bf763e57f803"
---

[Discussion](https://hashnode.com/posts/step-by-step-approach-to-use-onion-architecture-in-net/67e98fe33beb1a0497ba6e38)

Comment [Step-by-Step Approach to Use Onion Architecture in .NET](https://hashnode.com/posts/step-by-step-approach-to-use-onion-architecture-in-net/67e98fe33beb1a0497ba6e38)

[Lavadera Ruttinger](https://hashnode.com/@ruttinger)

[Apr 9](https://hashnode.com/posts/step-by-step-approach-to-use-onion-architecture-in-net/67e98fe33beb1a0497ba6e38/comment/69d6ff5b6be3bf763e57f803)

Great walkthrough of the implementation steps! When applying this to a domain with complex validation rules, do you typically keep those rules within the entity models themselves, or do you favor a separate validation service in the application core?