Does anyone else build SPAs with multiple lists and libraries? I've built many with single lists or libraries. My task is to build an app which would allow users to enter data about a project, upload documents related to the project, and add multiple daily updates for the project. My idea is to use 1 list for information about the project, 1 list for the daily updates, and 1 library for docs. The SPA allows users to select their project from a drop down and then display everything about the project on the page including buttons to add daily updates and upload documents.
I have implemented the example above as a proof of concept and it works as expected. I am passing the Project ID along with the document uploads and daily updates to use as a primary key for each Project.
My concern is that the actual proposed app contains many more components that will be broken out into separate lists like tasks for different departments. I'm already up to 6 AJAX calls and will need many more.
At what point would performance start to degrade?
Are there any tips or best practices from those who have created similar SPAs before?
Limitations: SP 2013 On-Prem, Front-End and CSOM only. Cannot use JS frameworks that require node. Currently using JavaScript, jQuery, MomentJS, Bootstrap.