DiNo is a digital notary platform that required multiple backend architecture improvements to support scalable workflows, integrations, and flexible data structures.
Problem
- The client needed a notification system to inform stakeholders when new client requests are submitted.
- The existing system lacked a flexible way to subscribe to events or messages.
Solution
- Developed a configurable notification system.
- Implemented event subscriptions so users can subscribe to specific system events.
- Designed the architecture so new notifications can be added with minimal configuration and without deep code changes.
Problem
- The existing system lacked a consistent and scalable data structure.
- Legal transactions and relationships vary significantly between cases.
- Each new process required additional database structures and code updates.
- This slowed down development significantly.
Solution
- Implemented an Entity-Attribute-Value (EAV) schema.
- Allowed new mandate types and processes to be added without backend changes.
- Created a fully configurable and extensible data model.
Problem
- Multiple notary software providers exist, each using different systems.
- The client needed to exchange data between platforms.
Solution
- Built middleware enabling synchronization between different notary software systems.
- Developed a custom ORM to support legacy databases such as Gupta SQL Base.
- Optimized synchronization performance to handle thousands of records without affecting system performance.