Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Screaming Architecture #40

Open
qrhfz opened this issue May 9, 2023 · 0 comments
Open

Screaming Architecture #40

qrhfz opened this issue May 9, 2023 · 0 comments

Comments

@qrhfz
Copy link

qrhfz commented May 9, 2023

I'll quote from the book. Chapter 21. Screaming Architecture:

So what does the architecture of your application scream? When you look at the top-level directory structure, and the source files in the highest-level package, do they scream “Health Care System,” or “Accounting System,” or “Inventory Management System”? Or do they scream “Rails,” or “Spring/Hibernate,” or “ASP”?

Looking at the domain package's src directory. We'll see these directories:

  • annotation
  • exception
  • model
  • repository
  • usecase

It screams "Blogger's Clean Architecture". It doesn't scream what this app does. Is it a note app? Is it a blogging app? It does have owner and contributor in model. The top directory separate by types not by features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant