Ad-hoc Django integration for fault-tolerance

[Alec Taylor]

I thought of a fun project (if it hasn't been done before).

Why don't we build a distributed fault-tolerant architecture with Django?

Currently the architecture is MVC, which is logically client-server.

The architecture I would like to build up is inspired by PKIs' CA+RA idea.

Given the use-case of an e-commerce system with integrated POS, the
following should be in place:
- In-store database distributed across devices
- In-store database uploads orders made at set intervals to the main
server's database
- Main-server sends out orders made through the website to the store

This will enable the store to continue business when there Internet
connection goes down.

You may ask, "Why not just have a server in-store?" well this would be
an added hardware+maintenance cost+effort...

So these devices whether they be Towers, Laptops or PDAs will be
linked ad-hoc or through an AP to the local network. When the link
between our main server and the store goes down, they should be able
to keep running as usual minus the website orders.

What do you think, should this kind of architecture be built into django-core?

Or am I approaching this problem from the wrong direction?

Thanks for all suggestions,

Alec Taylor

[Kenneth Reitz]

Enjoy: http://guide.couchdb.org/draft/why.html

[Alec Taylor]

Thanks, hadn't thought to go with NoSQL. :)

Quick side-note: I received 14 emails on the django-devel list between
30 and 40 minutes ago. Strange, seeing as this one is dated 10 days
ago. Google Groups problem?

On Wed, Jan 18, 2012 at 10:07 AM, Kenneth Reitz <thepyt...@gmail.com> wrote:
> Enjoy: http://guide.couchdb.org/draft/why.html
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-developers/-/vQegCKmfVvAJ.
> To post to this group, send email to django-d...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-develop...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.

[Russell Keith-Magee]

On Sat, Jan 28, 2012 at 3:47 AM, Alec Taylor <alec.t...@gmail.com> wrote:
> Thanks, hadn't thought to go with NoSQL. :)
>
> Quick side-note: I received 14 emails on the django-devel list between
> 30 and 40 minutes ago. Strange, seeing as this one is dated 10 days
> ago. Google Groups problem?

You're not the only one who got this backlog -- I got it too. I'm have
no ideas about the underlying cause.

Yours,
Russ Magee %-)

[Adam "Cezar" Jenkins]

I also got the backlog, in addition my gmail has been buggy and slow for a few days, so I'm assuming it's Google having an issue.

--
You received this message because you are subscribed to the Google Groups "Django developers" group.

[Russell Keith-Magee]

For those wondering -- I've found out the cause. Google stopped
sending notifications about messages to django-dev awaiting
moderation, so there was a backlog of messages that needed to be
moderated. Karen Tracey discovered the backlog this morning, and
approved the messages; hence the flood.

Yours,
Russ Magee %-)

[Alec Taylor]

Ah great, well at least now we know it won't happen again :D

On Sat, Jan 28, 2012 at 6:40 PM, Russell Keith-Magee