Skip to content

split into microservices instead #7

@balupton

Description

@balupton

so before we had several different helpers in their own repo, however it was hard to keep them updated and consistent, so we merged them all into the current repo

however, if one service goes down, then they all go down - and - if we need to deploy one service, we have to deploy everything

instead, we should move to a microservice infrastructure now that now.sh is a thing, so still have a mono repo, but have each service deployed and tested individually, with the main helper as a proxy service to the individual services

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions