One API per dashboard, and why a short TTL beats a long one
Nine dashboards, data owned by another system, and a frontend that shouldn't have to care. Here's how an aggregation endpoint and a short-lived cache keep them fast and current.
Built the Qualification Certificate workflow end to end: an investor applies, an admin reviews, an approver decides, and an approved QC is reported to an external system and announced.
Pick a step to replay it
A QC application passes through three roles and can be sent back more than once, but has to end the same way every time: a decision on record, and an issued certificate the external system knows about.
Stack.NET 9, ABP.io, Angular, DDD and HyperPay
Nine dashboards, data owned by another system, and a frontend that shouldn't have to care. Here's how an aggregation endpoint and a short-lived cache keep them fast and current.
Nine dashboards, 4 for investors and 5 for admins, draw their data from another system's APIs. I centralised those calls in our ABP.io backend, so each dashboard makes one call, with a short-TTL cache in front.
Built with.NET 9, ABP.io, Caching and Angular
Read case studyOpen to product, full stack & backend roles.