This will work. Concurrency is Oracle's problem. Each Django is a client, and gets a separate connection to Oracle. Transaction management is bread and butter to the big databases.
That said, you may not need apache. This sounds like a group of cooperating users with a very low request rate, so even the development server may be enough. Also, if you have a box amongst you that is always up, it might be easier to manage a scheme with Django on just that system, so long as the intranet allows all of you to route to the one box (corporate enforced per system firewalling could be an issue here). The downside of running your own PostgreSQL (or MySQL if you must) is that corporate backup procedures applied to the Oracle server may not be applied to your data, giving you something else to manage. On the other hand, you need to be sure that you have table creation, etc., permissions, of which IT may be jealous. On Fri, Oct 29, 2010 at 3:33 AM, Victor Hooi <victorh...@gmail.com> wrote: > Hi, > > This is a bit of a strange scenario. > > We have a simple Django application used to maintain a database of > newspaper/journal articles. We're extensively using the django-admin > as part of this app. > > Currently, we're having issues getting a production environment with > Python provisioned (corporate environment, locked technology roadmap > etc.), however, we will have access to a Oracle database instance. > > One possibility raised was that for each of the clients (fairly small, > under 5), we install a local instance of Django and Apache, which they > access with their browser, and each of these instances communicates > with a single Oracle DB instance. > > I know on the Rails side, there was a product by Joyent called > Slingshot (http://joyeur.com/2007/03/22/joyent-slingshot/), which > allegedly did something similar (packaged up a RoR app into a desktop > application). > > Are there any particular issues we need to be aware of if we decided > to go down this path? > > In particular, I wasn't sure how multiple instances of Django would > handle concurrency if they were communicating with a single database. > Any advice there? > > Any other possible drawbacks/roadblocks? > > Cheers, > Victor > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
