Skip to content

My personal opinion on the Clean Code Architecture in the context of Domain Driven Design (DDD), yet i adopted some terms from the Onion Architecture such as domain to avoid any misleading interpretations with the Entity in DDD

Notifications You must be signed in to change notification settings

yauritux/clean-code-architecture

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

19 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Run on Repl.it

clean-code-architecture

My personal opinion on how the Clean Code Architecture implementation looks like in Go within the context of the Domain Driven Design (DDD), yet i adopted some terms from the Onion Architecture such as domain in order to avoid any misleading interpretations with the Entity in Domain Driven Design.

I'm using in-memory repository for the current implementation, however... will be adding another sample for other repository implementations such as database and web services. The client is also provided as a CLI application at this moment merely to show how this kinda architecture works. Absolutely, will be updating with other infrastructures and adapters such as REST APIs, gRPC services, etc.

Here's what the code architecture looks like in the components level:

JANIO HUB Backend Code Architecture

Usage

Run all Unit Tests

From the terminal, execute this following command:

go test ./...

Test using CLI App

From the terminal, execute this following command:

go run cmd/cli/main.go

Further Read

About

My personal opinion on the Clean Code Architecture in the context of Domain Driven Design (DDD), yet i adopted some terms from the Onion Architecture such as domain to avoid any misleading interpretations with the Entity in DDD

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages