Hello there, I am creating an application that will require a detailed backend service. I am browsing to compare the advantages of using a system such as UserGrid over building something from scratch.
I looked through your documents and became confused about Connections/Relations and Items, which brought me here. My application may potentially become large quite quickly, therefore I am looking for a system that is highly scalable. My database will require more information than your list of Collections provide, for example: The User table is going to need relations to other tables for things such as profile pictures, in-app messaging and locational information. My questions are: - Can you create a collection with any number of properties (within limits of disk space etc)? - Can you create relations / joins between multiple collections and narrow the response time by making queries on top of this join / relation? Your docs claim there is a way of creating new collections that link via certain 'verbs' such as 'following' or 'likes'. This is where I became confused, in order create a relation between 2 sets of information would I create collections for Profile Pictures, Locations, Messages etc and link them to User using a structure like (using the verb 'links-to'): GET https://api.usergrid.com/my-org/my-app/users/fred/links-to/pictures Please let me know if this defeats the point of relational verbs Kindest Regards Chris Rogers Digital Developer [email protected] @portchris <https://twitter.com/SamJohnAllen> www.zeta.net 01202 237137 @ZetaAgency <https://twitter.com/ZetaAgency>
