spring-projects / spring-projects/spring-modulith
Investigate using the ArchUnit module APIs in favor of the slice ones
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 222
- PR merge metrics
- No merged PRs in 30d
Description
ArchUnit released a new module architecture rule API that seems inspired by the conventions of Spring Modulith. We should investigate in how far it allows us to port some of the concepts and verifications we built on top of ArchUnit can be replaced by using that API.
From a quick glance, it seems it supports:
- Modules by identified package (either naming pattern or annotations)
- Dedicated module APIs
It currently seems to lack explicit API to replace our named interfaces abstractions, in particular the ability to define dependencies to a named API.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the ArchUnit module architecture rule API and the existing slice-based concepts and verifications in Spring Modulith. Compare support for package- or annotation-identified modules, dedicated module APIs, and named interface dependencies; document which concepts can be replaced and which remain unsupported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100