Principles
Architectural principles of the platform
Motivation
There are variations in how judicial systems function at the national, state and local levels. The design aims to capture these variations as configuration to enable scalability. For example, workflows, master data, roles etc.. are modeled as configuration. These can be customized per implementation.
Integrations with third-party systems are variable. These components need to be swappable according to implementation needs.
The lack of a unified, single source of truth for data across the case lifecycle is a barrier to delivering effective and timely justice. By reducing data duplication and ensuring data integrity in registries, the design aims to improve access to quality data that can be used to monitor and improve downstream processes.
The design aims to enable interoperability with other systems by easing access to registry data via APIs while ensuring security/privacy. Freeing up data can catalyze ecosystem players to innovate on top of the platform.
Design Principles
The DRISTI platform adheres to DIGIT's platform principles and builds on top of it. It is built on core principles designed to enhance usability, security and interoperability:
Single Source of Truth - Utilises shared data registries to ensure reuse of data without redundancy. Offers standard API access for multiple service providers, eliminating data duplication.
Interoperable - Ensures seamless data exchange and system compatibility with an API-first approach to design and adherence to Open Standards.
Security and Privacy - Built with security as a priority with configurable role-based access. It guarantees the encryption of Personally Identifiable Information (PII), which remains off-limits to analytical systems.
Scalability - Employs an event-driven, asynchronous, microservices architecture capable of handling millions of service requests efficiently.
Flexible - Offers high configurability to meet various judiciary needs. Courts can tailor their master data and workflow processes, while integrators can develop and deploy custom service versions.
Modular - Designed with modular microservices and interoperable APIs, the platform allows for independent scaling, updating and deployment of services.
Open - The platform is cloud-agnostic and can be implemented across private data centres or cloud providers. It is MIT-licensed and built with open-source tools and technology to prevent vendor lock-in.
Last updated