Hey Kaan, I'm not sure I can comment on some of the colourful analogies employed in your commentary, but I can provide the advice that you can increase your quota with the Search API up to 200GB of storage by submitting a request <https://support.google.com/cloud/contact/cloud_search_api_index_size_increase_request_form>, and the documentation <https://cloud.google.com/appengine/docs/quotas?hl=en#search> also mentions that all the quotas can be negotiated by discussing with a support representative.
We certainly aim to make all our services scalable, and a general rule to keep in mind in terms of realizing this abstract statement is that it's often not the service itself which has a limit, but what customers who are willing to communicate with us have expressly communicated was of interest to them in terms of scaling potential. We have in the past, and will again in the future, "moved mountains" for customers who are interested and willing to make a foray into a larger-scale deployment of any service, once both technical and billing details have been discussed. This is of course still very abstract, and should not be taken as any kind of concrete commitment - my advice to anybody who might read this thread in future, and those in it right now is merely to get in touch with a support representative and explore your options. We are generally very flexible :) Have a great day! On Saturday, January 23, 2016 at 4:59:56 AM UTC-5, Kaan Soral wrote: > > Search API seems like "a deal with the devil" to me, for some time you get > all that you could dream for, but at one point, you suffer and die painfully > > I haven't reached the limits of Search API myself yet, I haven't seen > anyone that did either, but once you reach the limits, you can't add any > more documents, the index gets stuck - I'm guessing, at that point, one > must implement another system to start deleting unimportant documents to > make room for more important stuff, this applies to my use case, but it > might not apply to everyone's > > It would be great if Search API did this on it's own, if you reach the > limit, send in an argument at document.add's to remove the least ranked > document automatically > > Anyway, now that I've been using the Search API for some time, I regret > some of the thing that I did with "datastore", I have complex and well > calibrated indexes and filters, filled with workarounds and trade-off's > > At one point, I might re-visit them and just re-do things with Search API > using a separate index for specific use cases > > TL;DR: Search API is awesome but look out for the limitations, it's > definitely not scalable > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/c4707397-9ec0-443a-8616-51bfed129d5a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
