My team is considering using Django for a SaaS/on-premise enterprise web application. We've been happy with building with Django for SaaS, but don't have experience deploying and supporting it on-premise in enterprise Linux and Windows environments. Therefore, we'd like to get the community's perspective before going down this path.
While we appreciate all feedback, the areas we most need clarity are the following. For each, we'd like to hear: How did you address the area? What went well? What didn't go well? What do you wish you had known before starting?
- Deployment: e.g., direct, container, VM, or a packaging solution such as Replicated
- Integration: did you hook into existing services (caching, logging, etc.) or did you deploy these services alongside the application?
- Licensing: e.g., based on # of seats
- Authentication/Authorization: e.g., LDAP, AD, etc.
- Updates: bug fixes, and changes requiring migrations
Also, if you're a development shop that has experience building enterprise Django applications, we'd love to chat with you because we're looking for some extra resources on our projects.
Thanks,
Todd
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/230c508a-94ed-494a-8d99-88c89aeb9e78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment