How to scale many records in Google App Engine

Question

I am going to write an application that should store a small number of entries per user (<300), but hopefully there will be many users (→ 1000). I did some research for a platform that lets you start small and scale if you need to, and got stuck in App Engine, but I'm not sure if this is the right tool for it, especially for data storage.

How can I get it for scaling if I have a user object and a message object and all users and messages are stored in these objects? I think that the number of entries in entities will grow very large and filtering, that is, for all user messages will be expensive. Is this a problem or will Google handle this? Should I introduce multi-user work and create a namespace for each user, so I see only entries in objects related to the user? Is there a limit to the number of namespaces? What would be the right approach for modeling data in a data warehouse?

I have no idea how to handle the App Engine datastore, and if this is the right tool for me.

Answer 1

The App Engine data warehouse is specifically designed for this scalability. Requests are fulfilled over time in proportion to the number of records returned, so the selection of all user messages will be performed equally regardless of the number of users in the system.

Answer 2

I think that with such numbers you are probably good in terms of scalability. 300,000 to millions of records are easily handled by any serious data warehouse.

Answer 3

. / ... . /, , . //, , , !!! . ...

I'm not trying to de-moralize you, but trying to help you focus where you should be ... Thanks for reading and good luck with your application! Perhaps you need to scale, and, as Toby said, even the most basic App Engine configuration is good enough to handle several hundred thousand entries ...