Re: Site Architecture

On Fri, Sep 7, 2012 at 4:19 PM, Kurtis Mullins <kurtis.mullins@gmail.com> wrote:
> I would recommend not using Django to consume services over a network
> without intensive caching and safe-guards just due to the fact that it will
> hold up the connection when a user tries to access a page. Importing your
> existing project into Django (as opposed to accessing it through an API)
> would be a great approach.
>
> With that said, I have accessed many APIs through Django including some
> critical systems (such as billing systems) and have not had too much
> trouble. Again, just make sure to check for errors and time-outs properly or
> else your customers may have some weird issues that could be difficult to
> debug.
>
> If at all possible, this would be the way I'd go. Of course it depends on if
> the "Rest Services" are something you own.
>
> Database -> Django -> HTML
>
> While that may take quite a bit of initial work to re-do, the simplicity it
> would offer could pay off in dividends.
>
> Good luck!
>

At $JOB we revolve around SOA - Service Oriented Architecture. Many of
our website frontends communicate with datamart backends. Our
downloadable documents are produced by pushing data to
excel/powerpoint/doc/pdf rendering services. Our graphs are drawn by
pushing data to graph services.

Rather than making things complex, this massively reduces complexity.
Each service has clearly designated boundaries, goals and KPIs, which
increases reliability. We don't seem to have issues with latency or
hold ups; in fact, I think everything runs slightly better in this
model, as each website is no longer doing much heavy lifting
particularly.

With better encapsulation and separation of concerns comes better
reliability and an understanding of where performance gains can be
made, as well as implicitly better allowing for scale out.

So, personally, I wouldn't rule out the OP's original plan for
complexity reasons.

Cheers

Tom

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.