This page discusses the non-functional requirements and how they are met in the openIDL architecture.

Performance

Scalability

Availability defines when the system is usable. A useful metric is 24X7X365, which means it is always available.

To achieve always up, we must have a self-healing, fully redundant system.

This is achieved differrently for different parts of the architecture.

Services outside kubernetes include: MongoDB, Cognito and others.

How do we provide support for openIDL? How can users report issues? How do we track those issues and ensure resolution?