Architecture question
86 views
Skip to first unread message
Rajesh Gupta
Mar 17, 2016, 8:03:05 AM3/17/16
to google-a...@googlegroups.com
Hi,
We are using java appengine. We have already using 160 indexes.
We plan to expand further with more functionality, but we will hit the 200 index limit.
Our current architecture is servlets/jsp, with several GWT modules.
What are my architecture options to add more functionality, with out hitting the 200 index limit.
Can I use another new appid, and do the remote-api from the serverside java code?
Rajesh
Accounting/Inventory/Orders on Google Cloud Platform and Mobile
Nick (Cloud Platform Support)
Mar 18, 2016, 2:00:27 PM3/18/16
to Google App Engine
Hey Rajesh,
Only somebody intimately familiar with both your code-base and the problems you want to solve, and the future directions you might want to move (adding functionality) could give an answer which is appropriately concrete. However I can give general advice in line with the general nature of the question. You can look at ways to restructure your data, or determine which indexes may not be needed by running analysis of how often different indexes are used. You could also potentially file a Public Issue Tracker request with many details if you absolutely need to have more indexes without restructuring, but it's usually possible to restructure.
Here are some articles which might help you to make some concrete decisions:
Only somebody intimately familiar with both your code-base and the problems you want to solve, and the future directions you might want to move (adding functionality) could give an answer which is appropriately concrete. However I can give general advice in line with the general nature of the question. You can look at ways to restructure your data, or determine which indexes may not be needed by running analysis of how often different indexes are used. You could also potentially file a Public Issue Tracker request with many details if you absolutely need to have more indexes without restructuring, but it's usually possible to restructure.
Here are some articles which might help you to make some concrete decisions:
Best wishes,
Nick
Cloud Platform Community Support
Nick
Cloud Platform Community Support
Janne Savukoski
Mar 19, 2016, 2:31:10 AM3/19/16
to Google App Engine
Hi Rajesh,
I'd suggest to consider moving some queries over to Search API (https://cloud.google.com/appengine/docs/java/search/). For example, we use the custom datastore indexes (indices) primarily only for queries which have strong consistency requirements.
After we adopted this approach of focusing all “non-strict” queries to Search API, our custom index count stopped increasing quite effectively. As an added bonus, you also gain the much more versatile query capability of the Search API. And save the trouble of keeping track what kind of queries need to be supported by custom indices.
Cheers,
Janne, Swap.com
Nick (Cloud Platform Support)
Mar 21, 2016, 11:13:56 AM3/21/16
to Google App Engine
Good points, Janne, yeah, that's a great alternative way to cut down on indexes.
Reply all
Reply to author
Forward
0 new messages