cross-app relationships and performance

Hey Andrew,

I don't think you'll find a single best practice in this case, as it'll depends on the complexity and request volume of your apps.

With that being said, we recently had major performance issues with a few cross-app relationships to the point we had to refactor and cut the relationships. We've worked with QB escalated Support to come to that decision for our use case after review and implementing many performance best practices.

When one user performed a slow action, unfortunately all our Users will wait in line … this includes bottlenecking API requests which led to script timeouts. One example is simply opening a larger app in the relationship that hasn't been accessed for awhile which requires time to load into memory.

Although, on the flip-side, I've seen cross-app relationships work well for less complex apps having fewer requests.

In my experience, even when you've followed best practices, record volume (over ~ 1 million) is the biggest performance offender. And formula queries.

Anyway, I'd try to avoid cross-app relationships whenever possible! But don't take my word for it, I suggest reaching out to Customer support for your specific app(s) after reviewing performance best practices. Use performance analysis tools, blogs posts and Empower presentations to help keep your apps running smoothly.