t10d/kingdom-python-server

Structure improvements

Opened this issue · 0 comments

Issue

Right now, concerns are split into src/ in an heterogeneous fashion: We place both aggregates (auth, sales, etc) and entrypoint facilities (server, serverless, etc). It also is not extendable to support a distribution package properly.

Proposed solution

Requirements disclaimer

  1. Support multiple services under one repo
  2. Docker-compose should be aware of all those services and coordination
  3. Effectively insulate commons (currently core) to enable proper packaging

Directory-tree change

This is a very initial draft without much consideration to it. Two grains of salt needed here.

docs
tests
kingdom
 |- template
    |- aggregates
        |- access
             |- domain
             |- service
             |- adapters
             |- routes
    |- entrypoint
 |- core
 |- contrib

This issue blocks #9.