h2. Approach #1
It is possible to use 2 different Postgres containers. This is already done in data sync server's memeo list devl workflow: https://github.com/aerogear/data-sync-server/blob/master/docker-compose.yml
h2. Approach #2
It is also possible to use a single Postgres container but create 2 different databases in it. There can be 2 Postgres users that only have access to related databases (admin/data).
In the enterprise, it is a common thing to use a single database software which is hosted on a super computer and make apps use different databases(as in schemas) on it.
h2. APB
In the APB, we currently only create a Postgres database to store config for the sync server itself.
We don't create any other database to use as data source.
The question is, should we create any Postgres container to use as data source? The To lower the amount of work for the users, maybe we can put an option in APB's yaml to create the data source database (if something like that is possible).
But, the idea is that it is user's responsibility to create the data source and reference it in the sync server configuration. Remember: data source can be a database, and HTTP endpoint, etc.
To lower the amount I would expect most of work for the users , maybe we can put an option in APB's yaml to create the use a Postgres data source database (if something like that , but it is possible) not a requirement .
I don't think there's anything related to security. |
|
