Design consideration for indexes / Querying

4 posts, 0 answers
  1. Craig
    Craig avatar
    2 posts
    Member since:
    Nov 2012

    Posted 30 Mar 2014 Link to this post

    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
  2. Anton Dobrev
    Admin
    Anton Dobrev avatar
    539 posts

    Posted 31 Mar 2014 Link to this post

    Hello Craig,

    Thank you for your question! You are right, that indexing is a central part of a backend design. In addition, all the specifics of the NoSQL data stores demand to be handled design-time in order to ensure the best performance of the data store and the apps that are using it. Unfortunately, our documentation is somewhat scarce on this topic and it is in our plans to enhance it.

    Telerik Backend Services ensures automatically the index on the Id of an item. So, in terms of querying, a search on an Id would work as it is expected to work on indexed fields. Though we are aware that our customers would like to implement a diverse searching functionality in their apps, we are still evaluating the option to allow developers to create indexes on additional fields.

    In general, queries using '$where', '$nin' and '$neq' operators are slow and should be avoided (even in the presence of an index on this field).

    Please, let us know if further questions occur.

    Regards,
    Anton Dobrev
    Telerik
     

    Build cross-platform mobile apps using Visual Studio and .NET. Register for the online webinar on 03/27/2014, 11:00AM US ET.. Seats are limited.

     
  3. Greg Galipeau
    Greg Galipeau avatar
    13 posts
    Member since:
    Jul 2009

    Posted 02 May 2015 in reply to Anton Dobrev Link to this post

    Seeing as how this is over a year old and I am still having issues finding documentation on this subject - did Telerik ever implement the ability to index fields? I am about to build a fairly large implementation kn this platform and would like to index a column I know we will be querying off of quite regularly.

     

     

  4. Anton Dobrev
    Admin
    Anton Dobrev avatar
    539 posts

    Posted 05 May 2015 Link to this post

    @Greg

    Thanks for your input. We do understand the need for creating custom indexes, but however, this is still not exposed as a functionality to the developers that use Telerik Backend Services. The information above is still relevant and the only indexed field remains the Id.

    Please, let me know if you have further questions or suggestions.

    Regards,
    Anton Dobrev
    Telerik
     
    Everlive is now Telerik Backend Services, and is part of the Telerik Platform.
     
Back to Top