https://github.com/andrewgodwin/deps/blob/async/draft/0009-async.rst#the-orm

On Sat, Jan 25, 2020 at 4:50 PM Motaz Hejaze <[email protected]> wrote:

> They talking about making django asynchronous nature by the version 3.3 ..
> i can see that asynchronous model is high speed and performance like in
> node.js
> i don't know if that will be applicable to django
>
>
> On Sat, Jan 25, 2020 at 4:08 PM Nick Sarbicki <[email protected]>
> wrote:
>
>> As far as I'm aware the performance difference between gunicorn and uwsgi
>> is minimal. I prefer gunicorn but I have no real rationale for why.
>>
>> For ASGI Vs WSGI, WSGI is the historical standard most things are built
>> on so is by far the easiest to start with. ASGI requires a fundamental
>> change in how you think about your web services and whilst Django does
>> support ASGI nowadays it is still only experimental support. As a starting
>> point I'd stick with WSGI, ASGI has some benefits but early on the learning
>> curves make WSGI the logical choice.
>>
>>
>> On Sat, 25 Jan 2020, 11:41 Motaz Hejaze, <[email protected]> wrote:
>>
>>> Guys thank you all for all your answers ..
>>>
>>> I think i'll go with Nginx rather than Apache , Apache seems to have
>>> more options , but also seems old , complicated and heavy !
>>>
>>> Now i want to consider which layer of integration with web server to use
>>> , i.e should i user Nginx/Gunicorn or Nginx/uwsgi ?? are there any
>>> performance gain ?
>>>
>>> What about running Django in an Asynchronous way , i mean using django
>>> with Asgi rather than Usgi ?? any performance gain too ??
>>>
>>> On Sat, Jan 25, 2020 at 1:09 PM Nick Sarbicki <[email protected]>
>>> wrote:
>>>
>>>> I've used nginx+gunicorn/uwsgi, Apache+modwsgi, Google app engine flex,
>>>> Google app engine standard, heroku, kubernetes on various cloud platforms,
>>>> elastic beanstalk deployments and various others.
>>>>
>>>> Realistically I don't think there is a "best" way. It all depends on
>>>> your environment, what you're working with and what you know.
>>>>
>>>> If you're new to deploying Django I'd just follow the digital ocean
>>>> guide with nginx and gunicorn here:
>>>> https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-16-04
>>>>
>>>> It teaches you the basics of what you want to know.
>>>>
>>>> In the end every style of deployment has its ups and downs so I'd just
>>>> use whatever works best for you. If you don't know what that is then try
>>>> whatever seems simplest (in my opinion that digital ocean guide) and feel
>>>> free to evolve and adapt from there.
>>>>
>>>> One thing I would say though is to avoid app engine flex. It's just a
>>>> wrapper around Google compute engine for 6x the price. It promises
>>>> scalability but realistically the latency in bringing up new machines voids
>>>> that. Luckily the latest standard engine supports python 3 and Django and
>>>> is much faster so is ok to use (with a lot of work around connecting to
>>>> databases).
>>>>
>>>> On Sat, 25 Jan 2020, 08:06 Motaz Hejaze, <[email protected]> wrote:
>>>>
>>>>> I found this comparison on a blog ..
>>>>>
>>>>> Apache vs Nginx
>>>>>
>>>>> https://www.hostingadvice.com/how-to/nginx-vs-apache/
>>>>>
>>>>> --
>>>>> 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 [email protected].
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/django-users/8fdeda69-15ad-4997-9806-31c437ee2416%40googlegroups.com
>>>>> .
>>>>>
>>>> --
>>>> 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 [email protected].
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/django-users/CAGuvt91tse6MUmO3XhPL4iQVCzw44QzMQOA%3D-qAXMLjnmZBPOg%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/django-users/CAGuvt91tse6MUmO3XhPL4iQVCzw44QzMQOA%3D-qAXMLjnmZBPOg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> --
>>> 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 [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-users/CAHV4E-ec7ODpS-MTE1dxyNoVSTY2ROamqCDeDHddLR4Xk1NT2g%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/django-users/CAHV4E-ec7ODpS-MTE1dxyNoVSTY2ROamqCDeDHddLR4Xk1NT2g%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
>> 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 [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/CAGuvt90%3DtN4b8P%2B595X0FeXpp78bqg--aagqQ4ivo2wDJFkX0A%40mail.gmail.com
>> <https://groups.google.com/d/msgid/django-users/CAGuvt90%3DtN4b8P%2B595X0FeXpp78bqg--aagqQ4ivo2wDJFkX0A%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAHV4E-eJCs6ggAYBeH5nNrJjjAQJjXQ%3DNJA-mvsKPc2WUXRY0g%40mail.gmail.com.

Reply via email to