Difference between revisions of "Mesh/Distributed Services"

→‎Services: Fuller description in intro; remove unneeded header
(→‎Services: Fuller description in intro; remove unneeded header)
Line 1: Line 1:
=Services=
The [[mesh]] network should provide communication services, so that it offers value to its users beyond mere connectivity to the Internet. What can be done to help it strengthen ties among Oakland residents, and to benefit the community? This wiki page is here to collect ideas about what services could/should be offered.


The network ''should'' provide secure communication services (email, contacts, calendar, phone) to create more incentive to be on the network. The services can be integrated into a user account distributed database with master-master replication and low latency (ex. [http://www.datastax.com/resources/whitepapers/benchmarking-top-nosql-databases Cassandra]). These services will use existing open source projects.
(email, contacts, calendar, phone). The services can be integrated into a user account distributed database with master-master replication and low latency (ex. [http://www.datastax.com/resources/whitepapers/benchmarking-top-nosql-databases Cassandra]). These services will use existing open source projects.


==Storage / File Systems==
==Storage / File Systems==