primary goal: provide filesystem and ordbms services with continual replication (~1sec) at two other geographical locations.
secondary goal: provide filesystem and ordbms high availability (failover) services.
.. more to come!
secondary goal: provide filesystem and ordbms high availability (failover) services.
.. more to come!
proposal 1:
users can access a master postgresql server via the provided web application or directly. this master server is replicated on at least two other geographic locations. (meets g1, not g2)
proposal 2:
users can access three postgresql servers only via the provided web application. the web application prepares complete transactions on each remote database server, and then commits the transactions. (meets g1, g2)
--
then, the question is: will users appreciate their own access to storage resources, or would a web interface be sufficient?
users can access a master postgresql server via the provided web application or directly. this master server is replicated on at least two other geographic locations. (meets g1, not g2)
proposal 2:
users can access three postgresql servers only via the provided web application. the web application prepares complete transactions on each remote database server, and then commits the transactions. (meets g1, g2)
--
then, the question is: will users appreciate their own access to storage resources, or would a web interface be sufficient?
decision: use postgresql with slony-i (http://slony.info/).
what's this for?
my next-level distributed web application...
i'm looking at afs, but it uses fcrypt, which is too weak. i want people to trust this system so much that they won't hesitate to store all of their financial information in it.
i'm looking at afs, but it uses fcrypt, which is too weak. i want people to trust this system so much that they won't hesitate to store all of their financial information in it.
baaaallin
the reason i've gotten into ssl lately is because this project requires it. and i'm beginning to work on it. i have completed the infrastructure design finished.
it will use s3 for storage, but it will not encrypt stored files. i trust the amazon infrastructure enough to keep strangers away. it will use ssl everywhere, though, so all data will be protected in transit.
each user will have to provide her own s3 bucket and s3 credentials. relational data will be stored in the bucket using sqlite. non-relational data will be stored in the bucket raw.
ideas for winged leopard life applications
wine tasting notes (beer, coffee, tea, ...)
catalogue (books, records, ... , maybe even kitchen ingredients?)
gtd (todo lists, next action, priorities, timelines, goals)
calendar
finances (ledgers, events)
it will use s3 for storage, but it will not encrypt stored files. i trust the amazon infrastructure enough to keep strangers away. it will use ssl everywhere, though, so all data will be protected in transit.
each user will have to provide her own s3 bucket and s3 credentials. relational data will be stored in the bucket using sqlite. non-relational data will be stored in the bucket raw.
ideas for winged leopard life applications
wine tasting notes (beer, coffee, tea, ...)
catalogue (books, records, ... , maybe even kitchen ingredients?)
gtd (todo lists, next action, priorities, timelines, goals)
calendar
finances (ledgers, events)
this post has been archived.