News for hackers. Stuff that matters.
Re:Starlink – SpaceX’s broadband internet system by stcredzero on Friday May 24, 2019 @02:01PM (#20003880)
Can't be served a warrant. Arguably superior physical security. Can have line of sight comms with the entire region, which are both more direct and have faster signal speeds than fiber.

For certain global applications, a low orbit cloud consisting of many datacenters has some advantages. The virtual servers could virtually migrate to "hover" wherever they are needed, or to wherever would minimize latency.

Re:Starlink – SpaceX’s broadband internet system by isostatic on Friday May 24, 2019 @02:26PM (#20004067)
Do you have any idea how orbits work?
Re:Starlink – SpaceX’s broadband internet system by stcredzero on Friday May 24, 2019 @02:45PM (#20004211)
Do you have any idea how orbits work?

Yes. But your reading comprehension is spotty. Look at the cousin comment:

The way the "hovering" would work, is that the entire state of one virtual server would be serialized, then sent via line-of-sight high bandwidth comms to the next satellite to go over the region of interest. This way, the entire application's server cluster could incrementally migrate to remain over one geographic area, but do so at a much lower altitude than geosynchronous orbit.

Re:Starlink – SpaceX’s broadband internet system by rladd on Friday May 24, 2019 @02:32PM (#20004118)
That's not how orbits work.
Re:Starlink – SpaceX’s broadband internet system by stcredzero on Friday May 24, 2019 @02:44PM (#20004203)
That's not how orbits work.

You're not understanding the proposal. The way the "hovering" would work, is that the entire state of one virtual server would be serialized, then sent via line-of-sight high bandwidth comms to the next satellite to go over the region of interest. This way, the entire application's server cluster could incrementally migrate to remain over one geographic area, but do so at a much lower altitude than geosynchronous orbit.

Re:Starlink – SpaceX’s broadband internet system by rladd on Tuesday May 28, 2019 @12:59PM (#20031998)
So wait, we're sending entire server states from one satellite to another every few seconds, rather than routing the data to the satellite when needed? Seems like it would be a trade-off that would be worthwhile only for a small number of edge cases where there's a small server size, a fast start-up time, and a huge amount of very local traffic. In which case, put the server on the ground near the traffic? Or alternatively, move just a bit of the data (caches and some processing) around.