Re: Experiences/tips for deploying and supporting on-premise in enterprises?

Todd,

This is django presenting complete Cloud architecture to end user connected to the core hardware structure at backend. You get registered for example and spin up a VM, so the signals will get your site session connected to the core datacenter implementations to complete the task. I remember for the first three year it was not even million dollar investment on development side and still the team was able to get it in to the market. Even though cloud structure built on KVM with mix of VMware had few challenges on industry level but it was easy to come around things with very little R&D. 

Still the information you provided is pretty generic as for now to explain how would it work for you. But as we call Django battery loaded framework, so yes it is pretty helpful to work with such framework by keeping your focus on main logic. But no platform is perfect and there are always challenges to go around things to satisfy your goal. 

If I were you I would build it on paper for at least MVP and would double check with docs if Django satisfies the core requirements. For instance if you like to go with Saas model then there are a lot considerations to work on.

If you like we can have discussion about it with as much knowledge I would be able to present. I am currently building industry scale django based application as side project for apparel manufacturers, designers, suppliers and few other variants and I was surprised to see things going that smooth comparatively while I was working with PHP.

All your requirements above pretty much satisfied by default but I am not sure what challenges you may have on implementation level for Saas model.

Regards,

Mudassar

On Tue, Dec 27, 2016 at 11:00 AM, Todd Schiller <todd.schiller@gmail.com> wrote:

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+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/a142e6e8-9781-450a-9c54-3c6469e92e7c%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
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/CANoUts43iu2Ru%3DSLP3n7bNv3YyaxO%3DgA1WD0zKS1vhaaKJuvoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.