Split API URLs to second project/settings/wsgi ?

In one small project all web requests were done by humans in the past.

We used a login form and cookie bases sessions.

Now an API gets created and automated processes access these new URLs.

These processes use a different auth backend.

Now I see two possible solutions:


Solution1: Use one project (one settings file, one wsgi endpoint). This means we need to support several auth backends in one settings file.


Solution2: Split human and API calls. This means overhead in the configuration, but has the advantage that you can influence things like
the wsgi-worker queue better. Example: If there are several thousand API requests, the requests for humans don't suffer.


I know that there is not single truth and both solutions have their advantages and disadvantages. But maybe it helps if you write what you
think and what you learned in the past.

Regards,
  Thomas Güttler

--
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 post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/0d145a53-cc24-4ea8-b8d6-5090c762912c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.