Re: Django asychronous for millions of users

Samuel,

Thank you for that tremendous insight; sad to say you are correct on me trying to plan for the future of scaling. I am so use to having to plan ahead and have a backup for my backup which has a series of more backup to the original plan. I still operate as if I am still in the Marine Corps so thank you for helping me to see that I should first start simple with a simple deployment and later scale as my users grow. The thing I am trying to plan correct for scaling is the asynchronous technology part which from the conversations thus far from Lars and the rest I have found out about load balancer and cacheing. Thank you so much

Sent from my iPhone

> On Apr 1, 2021, at 11:17 AM, Samuel Smith <django@net153.net> wrote:
>
> On 3/30/21 6:32 AM, Josh moten wrote:
>> I am creating an auction that will be hosting millions to possibly billions of users so I am trying to figure out which would be the best library to use for scalability at a rapid pace. I am positive to reach a million users in four months. What is the best library and/or package to us for over 100k+ users per second?
>> --
>> You received this message because you are subscribed to the Google Groups "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com <mailto:django-users+unsubscribe@googlegroups.com>.
>> To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/b0ed59a5-5892-4a0e-b159-adc89476da78n%40googlegroups.com <https://groups.google.com/d/msgid/django-users/b0ed59a5-5892-4a0e-b159-adc89476da78n%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
> Just being "asychronous" won't get you there. Start small and make sure you are treating your database right. Use database views to limit excessive queries and to better aggregate your data instead of trying to stuff everything into a python object. Use a CDN to host as much static files as possible and even provide limited caching.
>
> And above all, don't plan out your "scaling" problems until you actually have enough money flowing to do so. I once worked for a startup that planned out having over a million customers on one platform. This was before the days of cheap AWS instances and so we allocated the needed resources and rack space in a data center and paid for expensive licensed software that was "web scale". We were spending over 1.5 million a year on hosting and software license costs. After 5 years we had finally grown to 70,000 customers but that still did not cover the costs of running the company and after a couple more years, closed shop.
>
> If we would have just started off simple with single django instance running on a box in a closet somewhere that company would probably still exist. They had a good product and market, but planning for a hypothetical future killed it.
>
> Regards,
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "Django users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-users/7XmCZgz3XzI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to django-users+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/fb8588ae-6297-c6a9-6512-632e9876caa0%40net153.net.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/EE907634-3F23-4A97-82A1-AFB96E056EFB%40gmail.com.