Thanks - I intentionally left it vague, as I'd like to better understand the space of options when working with Python + Django and where headaches might arise. I suspect there are aspects that seem straightforward, but end up being a headache for certain environments.
The main application is CRUD with analytics and visualization over relatively small data. It will have a small number of geographically diverse users. No scalability issues, though the application may benefit from splitting across geographies. Therefore, we'd be primarily looking to optimize for ease of deployment, integration, licensing, updating, and support. For example, we'd ideally have to make minimal changes to accommodate each new enterprise client and environment. "Hook into existing services" means whether you ended up deploying associated infrastructure (caching, logging, task queue) in the deployment, or whether you integrated into the enterprises services. For example, if you're deploying via VM, would you just go ahead and package Memcached in that VM, or take a different route? Similarly, have you run into problems using the migration framework for some enterprise clients? Mudassar, what in particular should I look at on that site? It looks like it's a service for migrate on-premise infrastructure to the cloud? On Monday, December 26, 2016 at 12:34:47 PM UTC-6, Todd Schiller wrote: > > 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+unsubscr...@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/a142e6e8-9781-450a-9c54-3c6469e92e7c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
