Page History

eco system - block centered

The two possibilities of hosting environments allow slightly different deployments. In the cloud (the hosted environment) is built as a self replicating system as a multitenant solution with strict separation of tenants.

...

Current state of discussion is, that I reached out to Microsoft and they would be willing to sponsor the creation of the prototype. So we assume now azure as the platform to implement the POC for the data exchange platform.

Cloud setup

In any cloud you need to setup an environment that allows you to run applications within the cloud (a so called azure landing zone). It contains:

...

For a productive environment its is not easily to be described generally since existing environments (as f.e. data stores) influence what is be required.

Application Landing zone

In the application landing zone, as the name suggests, are the applications hosted. The number of applications is not clear and need definition over time. But based on current user stories we require:

...

All services should follow the bounded context principle to make them as independent as possible. This suggests a microservice architecture because the system will benefit from their scalability, extensibility. Such a microservice follows a pattern as well and they need connections to interact with each other. Additionally for productive workloads also security measures are to apply. But let's start simple too. We will have microservices with or without storage. The services need to follow the shared-nothing principle otherwise the dependencies increase to a not-maintenable state. Therefore if a service requires a storage, it defines its datamodel, protects it's data but offers an API to enable access to the data. The service who owns the data is the only one to write in the data store. There is the possibility to have multiple synchronized, read-only copies of a data store. For more on microservices read Martin Fowlers work on it.

µ-service templates

Such a template defines how to create such a microservice in the eco-system. The figures are using azure components to depict it. As this is a reactive system per nature, we recommend azure functions for compute and managed services for databases, API management. This allows the least possible costs for the price of some latency in the interaction.

...