Hi Aman, Thank you so much for your feedback and for raising those points. I really appreciate the focus on scalability, it’s a perspective I'm still learning to navigate in a system as large as Fineract.
I completely agree that for heavy analytical data or long-term auditing, an ETL or background-process approach is much more robust. My initial thought process for a real-time API was primarily centered on the "operational" side specifically for mobile dashboards where a user might expect to see their standing update immediately after a transaction. I just wanted to share this point of view as a potential use case for the community to consider. I am not at all fixed on this specific implementation; I’m mostly curious about how we, as a community, prefer to handle the balance between real-time data needs and system performance. If the community feels that moving toward an ETL-based or pre-computed pattern is the better path for Fineract’s long-term health, I would be more than happy to pivot and explore how to implement this using the project's preferred architectural patterns. I’m looking forward to hearing more of your thoughts and learning from the community's experience on this! Best regards, Nidhi Bhawari >
