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