I'm looking to propose python+django for a new project at work, as I
feel it will be a good fit. Generally everything is done in PHP, so
its going to be a bit of a change.
I've already gathered a list of benefits to using python (fully oo,
maintainability across developers, etc), now I just need
On Jun 2, 5:40 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> Django is the easy part. Replicating your DB is the hard part.
This isn't too much of a concern for me. The db we're using currently
will scale nicely, and we've already got replication happening for
back-up and redundency purposes.
On Jun 2, 5:10 pm, The Code Janitor <[EMAIL PROTECTED]> wrote:
> solid enterprise grade examples are
> seriously lacking.
Do you mean high-traffic'd django sites? I've not really come across
many myself. Examples of these would be good.
--~--~-~--~~~---~--~~
You
I'm looking at using django to replace our current CMS application
written in PHP. Currently we have two servers behind a load balancer,
and everything's nice and stable. We're getting a consistent month-on-
month traffic increase though and I'm looking at moving to a more
distributed model -
Has anyone used django (including its ORM system) with a non-sql db?
I'd be interested in learning how django was modified to get the best
fit.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To
5 matches
Mail list logo
