Deployment Strategy

Multi Deployment vs. Multi Tenancy Deployment

multi deployment

• Applications and microservices do not have to be multi-client capable

  • Advantage especially with already existing systems like CrowdNewsRoom

• Can be distributed regionally per newsroom, e.g. to host data in the respective country

• Data is strictly separated from other newsrooms, as there is no common database

• If it is to be very strict, the authentication per newsroom could also be implemented

• rolling releases are simpler due to the fact that there are only a few smaller instances in operation, as there is no need to migrate a large amount of data

• Backups can be easily separated per newsroom

• The disadvantage is an increased effort to manage the deployments. This can be done manually at the beginning, but must be automated later

• Disadvantage can be an increased resource consumption of server capacities, since an overhead is given by e.g. several web servers

• central authentication makes it possible to access several newsrooms with one login without having to access the data between them

multi deployment strategy per newsroom

Multi Tenancy Deployment

• All newsrooms use the same version of the systems

• centralised management of applications

• easier evaluation possibilities across newsrooms

• monitoring would be simpler and clearer

common resources for editorial offices across systems