Skip to content

Split in to service | client architecture  #65

@thewillyhuman

Description

@thewillyhuman

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[x] Feature request
[ ] Documentation issue or request

Description

Both client and service are implemented as a monolith instead as a distributed services as the other modules. For that it is needed to split in to two repositories, one for the client and another for the service. Look the following scheme where the whole architecture is described.

aws-gestusers - new page 1

You can take as an example the agents_service.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions