Digital Transformation with Didgah

In designing Didgah's technical infrastructure, the focus has been on creating a structure that can simultaneously meet the diverse needs of Iranian organizations and be compatible with on-premises environments. This structure is based on the Monolith architecture, which, by utilizing patterns such as Onion Architecture and the Dependency Inversion principle, allows the design of independent modules with minimal interdependencies.

In this pattern, each module (or Domain) is designed separately and the communication between them is done through specific interfaces. This internal separation allows developers to design, develop, or revise different parts of the system without affecting other parts. The use of tools such as Dapper also makes data access fast and controlled.

The goal of this architecture is to maintain simplicity in installation and maintenance in environments that typically lack cloud infrastructure and DevOps teams. At the same time, features such as testability, internal scalability, and extensibility are added to the structure, without imposing the complexities of microservice architecture on the system.

Didgah’s UI design follows a React-based approach and Microfrontend architecture. This model allows development teams to develop different modules independently, while in the final output, these modules are implemented in a unified way, creating a continuous and homogeneous experience for the end user.

Chargoon has designed a set of UI components (Component Set) that, when generating the output, puts all the modules together in the form of final files with a coherent structure. This has led to visual coordination between the sections and also increased loading speed in the browser. The central platform layer (Kernel) is also responsible for coordinating and executing these components.

On the other hand, by replacing server-side rendering (SSR) with client-side rendering (CSR), the processing load has been shifted from the server to the browser and resource consumption has been reduced. In this approach, instead of sending ready-made pages, only structured data is transferred, which improves response speed and overall performance.

In the new Didgah design, the relationship between the user interface and the business logic has been redesigned and is based on the Humble Object pattern. In this model, interfaces are only responsible for displaying and receiving data, and no business decisions are made in them.

All business rules and policies are centralized in a central layer that is called in the same way by all clients - from mobile applications to the web version and public APIs. This structure allows for rapid development, easier management of permissions, and seamless coordination between different versions.

This makes it possible to add new features without interfering with other components, and ensures system stability even at larger scales. This logical separation is one of the key strengths of the Didgah architecture.

Security in the Didgah suite is considered one of the main pillars of the design. The use of encrypted APIs with private keys and a separate design for each module have effectively neutralized threats such as data leakage or unauthorized access.

The Context-based authorization model and the application of restrictions at different levels - from the Actor level to the data and field - have enabled precise monitoring. The combination of Gateway layers and the Backend for Frontend pattern act as a protective wall for modules and prevent external intrusion.

In the PublicAPI section, a dedicated authentication system is used that provides security and flexibility at the same time by issuing JWT tokens and enabling Impersonation. This architecture has been able to cover the diverse needs of organizations in the field of security with precision and detail.

Didgah has used advanced technologies in its technical design to increase performance and scalability. The use of a two-tier cache based on Redis, the use of read clusters in the database, and the elimination of the need for Sticky Session are among the things that have increased speed and reduced server load.

For heavy computing activities such as reporting, the processes have been moved to independent services, which has increased the stability of the system. Also, the logging service supports multiple databases and performs the Audit process without affecting the main performance.

At the adaptability level, Workflow and BPMN engines have been developed so that complex processes of organizations can be designed and implemented with simple and intuitive flowcharts. Tools such as DDM also allow organizations to extend their forms and information entities without the need for hardware development.

Didgah’s user interface has been redesigned based on the Human-Centered philosophy to put users at the center of the experience. This approach has made designing forms and pages simpler, more understandable, and more customizable, resulting in significantly increased user productivity and satisfaction.

Form Designer and Render Engine are tools that allow end users to design and modify forms without the involvement of the technical team. This independence plays a key role in making the organization agile, especially in environments with changing needs.

Finally, the migration to the new .NET version has brought the Didgah system to a higher level in terms of performance, resource consumption, and stability. These changes show that the Didgah design not only meets today's needs, but will also be usable in the future.