elijah-cloudlet

> home automation' core/aggregation box Deeper than that, even. It seems like this is intended as a local-network cloudlet[1] substrate. Launch an app on your phone that needs a companion frontend server instance to talk to? One gets launched "in the cloud"—specifically, in a virtual cloud owned by the app author. But where is that instance, physically? Usually a provider like AWS... but with a cloudlet peering arrangement, that instance could instead end up running on your router. (Not as crazy as it sounds if your app has an N:M frontend-backend server topology.) [1] https://github.com/cmusatyalab/elijah-cloudlet

There are simple and compelling reasons penned by the creator[0]. I ain't an expert in security, although the key idea of a local backend with P2P activities makes intuitive sense to secure data from eavesdropping. Ideas from a related project[1] like de-centralization, self-management of small servers (as opposed to server farms) distributed around the globe could be leveraged in cryptosphere? Diagram explaining interactions in Elijah[2] [0] http://tonyarcieri.com/the-cloud-isnt-dead-it-just-needs-to-... [1] http://elijah.cs.cmu.edu/ [2] https://github.com/cmusatyalab/elijah-cloudlet/blob/master/d...