2 ms·
I haven’t done a write up, but basically I just use unison [1] with a hub and spoke model. It is pretty simple, but it works well for my use case which is all f
by danieltillett 11y ago
I haven’t done a write up, but basically I just use unison [1] with a hub and spoke model. It is pretty simple, but it works well for my use case which is all file based.
My system is dynamic, but once a user is allocated to a node it is easy to replicate their data over the network. The key was I designed the system with easy replication in mind - flat files rather than databases, etc.
1. https://www.cis.upenn.edu/~bcpierce/unison/ https://www.cis.upenn.edu/~bcpierce/unison/
- nickpsecurity 11y agoThen what's your take on my suggestion? https://news.ycombinator.com/item?id=10822904 https://news.ycombinator.com/item?id=10822904 EDIT to add: Good work on Unison btw.
- danieltillett 11y agoI think it is a good idea. It is a bit more complex than using Unison, but it should be more generalisable. I think the real key to creating a simple and low cost reliable system is to have this in mind when you design your application. I could have used a database just as easily as a flat file approach, but this would have made things much more complicated to replicate between the nodes.
- nickpsecurity 11y agoI appreciate the feedback. This... "I think the real key to creating a simple and low cost reliable system is to have this in mind when you design your application. I could have used a database just as easily as a flat file approach, but this would have made things much more complicated to replicate between the nodes." ...is a great point. It echos the comments and thinking of Bernstein in his paper on lessons learned from Qmail. http://cr.yp.to/qmail/qmailsec-20071101.pdf http://cr.yp.to/qmail/qmailsec-20071101.pdf Particularly, section 4.5 "Reusing the filesystem."