diff --git a/docs/en/Domain-Driven-Design-Implementation-Guide.md b/docs/en/Domain-Driven-Design-Implementation-Guide.md
index ab8fe8cdad..d405ceb0ac 100644
--- a/docs/en/Domain-Driven-Design-Implementation-Guide.md
+++ b/docs/en/Domain-Driven-Design-Implementation-Guide.md
@@ -1919,4 +1919,12 @@ However, **being important is not sufficient** to consider a code as a Core Busi
 * An admin user can use a Back Office Application to create a new organization without any payment.
 * A background-working data import/integration/synchronization system may also need to create organizations without any payment operation.
 
-As you see, **payment is not a necessary operation to create a valid organization**. It is a use case specific application logic.
\ No newline at end of file
+As you see, **payment is not a necessary operation to create a valid organization**. It is a use case specific application logic.
+
+## Reference Books
+
+If you seriously interest in the Domain Driven Design and building large scale enterprise systems, the following books are suggested as reference books;
+
+* "*Domain Driven Design*" by Eric Evans
+* "*Implementing Domain Driven Design*" by Vaughn Vernon
+* "*Clean Architecture*" by Robert C. Martin
\ No newline at end of file