I guess if we could just use multiple databases, and also easily change the default database, this kind of heartbreak would be prevented
As I see, I made a mistake by choosing the Native option, my approach is to have scalability, and from experience, that 10,000/s limit just makes the native mode a good fit for highly agile / practical but small apps, rather than anything that processes data or scales For example, one could create 10 firestore databases, and just use them to broadcast data to 10 million people, for that use case, it's very practical But for an actual heart of a project, it will just result in a heart attack and early death Since my databases are empty, I hope I can easily fix the mistake, I guess I'll open a ticket, maybe delete/re-create the apps etc. On Saturday, January 9, 2021 at 5:25:38 PM UTC+3 Kaan wrote: > I probably originally read this article, and since it's always best to use > new technologies, I picked the native mode: > https://cloud.google.com/datastore/docs/firestore-or-datastore > > In the above article, you can't see the 10,000/s limit, which is basically > a *MAJOR* bottleneck, I mean, even in my 10 year old app, I do more than > 10,000/s writes throughput-wise, with mapreduce-like tasks ... > > On Saturday, January 9, 2021 at 5:20:00 PM UTC+3 Kaan wrote: > >> In this age, 1,000,000 concurrent connections is the dream, so let's >> ignore that >> >> But, *10,000/s writes per second to the entire database* - what kind of >> a funny limit is that? >> >> I mean it's really agony having to make binding database decisions like >> this, and after making these decisions, discovering (or in my case, I >> assume re-discovering, I don't recall seeing this absurd limit when I first >> selected Cloud Firestore) these limits >> >> For get 1,000,000 concurrent users, with 100,000 active >> users/players/clients-whatever - that *10,000/s* limit just takes App >> Engine from infinitely scalable to a joke >> >> We can't horizontally scale either, not possible to create more >> databases, but even if you could, the 10,000/s limit would need you to >> scale everything horizontally, even just authenticating the users etc. >> >> Also there's the attack possibilities, just 2,000 people could come >> together, just make regular requests to your service, and they've >> essentially brought your entire project down >> >> Is this something that will be removed/solved in the future, or did I do >> a dire mistake of choosing the Native mode? >> > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/42107567-3d2e-4086-9ae5-7444b0767355n%40googlegroups.com.
