kingdom-python-server
                                
                                
                                
                                    kingdom-python-server copied to clipboard
                            
                            
                            
                        Structure improvements
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
- Support multiple services under one repo
 - Docker-compose should be aware of all those services and coordination
 - Effectively insulate 
commons(currentlycore) 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.