Comments (3)
bslota
commented on August 23, 2024
1
Hi! Thanks @yami12376 for your question! Could you please elaborate on what do you mean by "(...) direction your example packaging expand in the future?". Just like @shuraa wrote, we follow packaging by component, to get screaming architecture, minimizing architecture code gap. Currently, each component package encapsulates the "features" in the form of queries or applications. The key in understanding the reasoning behind it is that there are aggregates that create the heart of their own package - in other ones, they are just projections (read models), or they are not even known (event-based communication). Thanks to this, we get clear separation of concerns. Does this description help you?
from library.
shuraa
commented on August 23, 2024
Packaging by Components looks more straightforward to me. Component is term
from C4 model.
вт, 1 окт. 2019 г. в 10:55, yami12376 <[email protected]>:
Hey,
I am wondering is it better approach to use packaging by feature instead
of packaging by layers using DDD.
In what direction your example packaging expand in the future?
Just by looking at the package structure:
└── library
├── catalogue
├── commons
│ ├── aggregates
│ ├── commands
│ └── events
│ └── publisher
└── lending
├── book
│ ├── application
│ ├── infrastructure
│ └── model
├── dailysheet
│ ├── infrastructure
│ └── model
├── librarybranch
│ └── model
├── patron
│ ├── application
│ ├── infrastructure
│ └── model
└── patronprofile
├── infrastructure
├── model
└── web
Does it start to use packaging by feature?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#41?email_source=notifications&email_token=AAGK4DM252VG5GZXROYP4KLQMMF65A5CNFSM4I4GQ6VKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HOY5XHA>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGK4DIPOFT6IQ3DDGONUB3QMMF65ANCNFSM4I4GQ6VA>
.
--
Best regards,
Alexander Morozov
from library.
yami12376
commented on August 23, 2024
each component package encapsulates the "features"
I meant if you can make package by feature inside of packaging by component?
I do not see it yet in code - is it possible?
If not, what are benefits of using packaging by features instead of packaging by components?
from library.
Related Issues (20)
- Read only link to Miro board in readme HOT 1
- Not all tests are deterministic HOT 2
- Test MeteredDomainEventPublisherSpec is not running during build. HOT 3
- GroovyTemplateAutoConfiguration - Cannot find template. HOT 2
- Architecture hexagonal ? HOT 3
- Remove findBy from save at BookRepository.save(Book book)
- Data consistency HOT 4
- Why are there 3 same events ? Is this a mistake ? HOT 1
- Is the picture wrong ? HOT 2
- Patron definition HOT 1
- [Question] hold_database_entity and overdue_checkout_database_entity table not used? HOT 2
- [Question] What factors affected your design decision? HOT 1
- Is the storage of the Book attributes redundant? HOT 1
- Wrong domain abstractions HOT 1
- Food for thoughts about extensions HOT 1
- Question about aggregates
- MY PROJECT
- Hack, placeholder or mistake?
- Update to spring boot 2.7.5 and Java 17
- Question about DB schema
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from library.