title: Appengine Search API vs Datastore
body: <p>I am trying to decide whether I should use App-engine Search API or Datastore for an App-engine Connected Android Project. The only distinction that the google documentation makes is</p>
  
  <blockquote>
    <p>... an index search can find no more than 10,000 matching documents.
    The App Engine Datastore may be more appropriate for applications that
    need to retrieve very large result sets.</p>
  </blockquote>
  
  <p>Given that I am already very familiar with the Datastore: Will someone please help me, assuming I don't need 10,000 results?</p>
  
  <ul>
  <li>Are there any advantages to using the <code>Search API</code> versus using Datastore for my queries (per the quote above, it seems sensible to use one <strong>or</strong> the other)? In my case the end user must be able to search, update existing entries, and create new entities. For example if my app is a bookstore, the user must be able to add new books, add reviews to existing books, search for a specific book.</li>
  <li>My data structure is such that the content will be supplied by the end user. Document vs Datastore entity: which is cheaper to update? $$, etc.</li>
  <li>Can they supplement each other: Datastore and Search API? What's the advantage? Why would someone consider pairing the two? What's the catch/cost?</li>
  </ul>