Modular monolith rearchitecture
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3
- Forks
- 2
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 3
Description
The current microservices architecture was primarily motivated by the requirement to support externally hosted engines. This requirement has proven to be unnecessary. The architecture adds a lot of complexity to the development, maintenance, and deployment of Serval. Since the original requirement is no longer needed, it now makes sense to move to a modular monolith architecture. Rearchitecting Serval will provide the opportunity to improve Serval in other ways, such as moving from a layered to a vertical slice architecture.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Begin by mapping Serval’s current microservices and deployment boundaries, then review the proposed modular-monolith and vertical-slice scope with maintainers. Done should be a concrete, agreed rearchitecture plan with defined migration boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend, backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100