Partner Issues

partner issues
    - no dev envio which means we cannot wipe staging db
        - unless we have multiple connections
    - not using oss because they dont want to create/delete/update real partners
    - multiple databases + IB
    - sync with deleted ones on one env.
    - sol1: creating partners that dont exist
        - auto increment id
            - Store an increment number centrally
                - memory local 100
                    - local 101
                    - staging 100
            - UUID
                - change the way we retrieve, update, delete
                - then we dont know which they are

(ES) <- (backend) <- (api) <- (frontend)
(ES) <- (backend) <- (frontend)

(api) - dtoIn, dtoOu, api call,

fronteND CANNOT CARRY THE PARTNER FUNCTIONALITY TO A NEW FRONTEND THAT WE MAY BUILD!!!!!!
why do we need a new frontend - because the idea(?) was to use angular or react.
We agreed to use a specific technoilogy for some reason... and david knows this.

phase 2 - OSS -> api ->
UI - OSS -> (api)
SAT - all frontends go here.
angular, vue - Goncalo wanted it.


if we need to rebuild the frontend, the fronetend wont be able to interact with partners
if we need to change the partner to use a different persistance layer