Non functional

The solution should follow current principles and best practices for a cloud native application. This implies the following:

Security

The solution will deal with millions of car owners and other individuals. So it is imperative to build security in right from the start to protect the data.

Reliability

Users of the system rely on the data to perform actions. These actions could be life saving or preventing harm. Therefore the system should deliver its services reliably and need to be built to do so.

Resiliency

Nothing is 100% secure against threats or defects. Even a part of the system is affected, the remaining parts should deliver the services as expected or throw meaningful responses.

Cost efficiency

The solution shall run on multiple nodes worldwide from multiple operators. Therefore the overall cost impact is affected by scaling effects and therefore prohibitive for exzessive spending.  Cost scaling to zero, if not used, is admired. 

Operational efficiency

Running systems incur cost by running them. A model is not defined how operation is governed in the future, but the ground thruth is minimizing the operational costs is always wanted. The system should run highly automated to prevent human error and allow fast development cycles.

Flexibility

The world is very complex and changing. To accomodate it, the system must be designed in a way, it can respond to changes. This implies, extensibility and the possibility of change. Methods of phasing out functions must be supported.

Scalability

The system will run on multiple nodes worldwide and nodes may be added/removed when required. The system must seamless integrate new nodes, functions and also scale up and down on workload needs.