Hi everyone,
I am currently working on a custom web application project using Wix Velo and running into a performance bottleneck while handling dynamic data binding and high-frequency dataset queries.
Current Setup:
-
Wix site utilizing custom Velo backend modules, routers, and connected database collections handling active user data.
-
Complex client-server interactions fetching filtered items dynamically on page load, similar to how media streaming apps like cloudstream apk
handle dynamic content loading and smooth streaming resources.
The Challenge: As the number of records in our custom collections scales up, initial page load times and data query execution speeds have started lagging during peak traffic windows. It’s becoming tricky to optimize data retrieval limits and handle asynchronous backend hooks smoothly without causing frontend delays.
What best practices, caching strategies, or query optimization patterns does this community recommend for keeping Velo-driven data operations fast and scalable?
Would love to hear any tips, code structuring approaches, or performance tuning methods from your production experiences. Thanks!