This question is locked. New answers and comments are not allowed.
I'm aware that Backend Services is built on top of MongoDB, so the whole concept of database relations and indexing is not the same. However, since the portal allows you to define "relations" to other types, and the volume of data will grow... what options are there for making sure your backend data service continues to be responsive as data volumes grow? Specifically, how to access data for a specific userId where new userId's will continually be added?
I've been unable to find any documentation on this subject. One of the SDK's (.Net) vaguely referenced this subject in the Querying / Filtering section, but nothing specific...
I find it hard to believe that "indexing" does NOT need to be considered in the design of a new backend service? But I don't see where we as the developer have any control over this in the current version of the portal?
Please advise - thanks
I've been unable to find any documentation on this subject. One of the SDK's (.Net) vaguely referenced this subject in the Querying / Filtering section, but nothing specific...
I find it hard to believe that "indexing" does NOT need to be considered in the design of a new backend service? But I don't see where we as the developer have any control over this in the current version of the portal?
Please advise - thanks