Update README.md

Author: Amitpnk

README.md

@@ -39,12 +39,13 @@ If you like or are using this project to learn or start your solution, please gi
   <!-- * [Built With](#built-with) -->
 * [Getting Started](#getting-started)
 * [Features available in this project](#Features-available-in-this-project)
-* [Project description](#roadmap)
+* [Project description](#project-description)
 * [Design patterns Used](#roadmap)
 * [Class diagram](#roadmap)
 * [Contributing](#contributing)
 * [Licence Used](#Licence-Used)
 * [Contact](#contact)
+* [Support This Project](#Support-This-Project)
 <!-- * [Acknowledgements](#acknowledgements) -->
 
 ## Onion Architecture
@@ -157,14 +158,55 @@ Below features will be implemented in infrastructure layer. You can plug and pla
 - [ ] Hangfire
 - [ ] Advanced Pagination
 
-<!-- - [ ] SignalR -->
+## Project description
+
+we can see that all the Layers are dependent only on the Core Layers
+
+<details>
+  <summary><b>Domain layer</b></summary>
+  <p>
+    Domain Layers (Core layer) is implemented in center and never depends on any other layer. Therefore, what we do is that we create interfaces to Persistence layer and these interfaces get implemented in the external layers. This is also known and DIP or Dependency Inversion Principle
+  </p>
+</details>
+<details>
+  <summary><b>Persistence layer</b></summary>
+  <p>
+    In Persistence layer where we implement reposistory design pattern. In our project, we have implement Entityframework which already implements a repository design pattern. DbContext will be UoW (Unit of Work) and each DbSet is the repository. This interacts with our database using dataproviders
+  </p>
+</details>
+<details>
+  <summary><b>Service layer</b></summary>
+  <p>
+    Service layer (or also called as Application layer) where we can implement business logic. For OLAP/OLTP process, we can implement CQRS design pattern. In our project, we have implemented CQRS design pattern on top of Mediator design pattern via MediatR libraries
+  </p>
+  <p>In case you want to implement email feature logic, we define an IMailService in the Service Layer.
+  Using DIP, it is easily possible to switch the implementations. This helps build scalable applications.
+  </p>
+</details>
+<details>
+  <summary><b>Infrastructure Layer</b></summary>
+  <p>
+    In this layer, we add our third party libraries like JWT Tokens Authentication or Serilog for logging, etc. so that all the third libraries will be in one place. In our project, we have implemented almost all important libraries, you can plug & play (add/remove) based on your project requirement in StartUp.cs file.
+  </p>
+</details>
+<details>
+  <summary><b>Presentation Layer</b></summary>
+  <p>
+    This can be WebApi or UI.
+
+  </p>
+</details>
 
 ## Licence Used
 [![MIT License][license-shield]][license-url]
 
 See the contents of the LICENSE file for details
 
 
+## Contact
+
+Having any issues or troubles getting started? Drop a mail to amit.naik8103@gmail.com or [Raise a Bug or Feature Request](https://github.com/Amitpnk/Onion-architecture-ASP.NET-Core/issues/new). Always happy to help.
+
 ## Support This Project
 
 If you have found this project helpful, either as a library that you use or as a learning tool, please consider buying me a coffee: