From: "David Fernández" <davidfdzp@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink Digest, Vol 25, Issue 28
Date: Thu, 20 Apr 2023 14:24:52 +0200 [thread overview]
Message-ID: <CAC=tZ0qpTB7-P6eCw6ow5AG8Ca=47gM8a4UGFmTRDH06UxeoTA@mail.gmail.com> (raw)
In-Reply-To: <mailman.751.1681965188.1222.starlink@lists.bufferbloat.net>
Well, O3b MPower (MEO satellites) is offering independent one hop
dedicated access to the (Microsoft Azure) cloud as "killer
application". If the cloud is on the satellite, half-hop.
Starlink GWs are near Google Cloud datacenters.
Blue Origin is on the mission to move Amazon Cloud to orbit,
eventually, maybe, leaving the Earth as a garden to enjoy, without any
industry on the surface (in a century, maybe). Kuiper will offer one
hop access to Amazon Cloud, then half-hop.
What seems a crazy idea today will be eventually implemented later,
like Starlink (Teledesic failed, fingers crossed Starlink does not go
bankrupt, although I would expect it be saved by Department of
Defense, as Iridium was saved).
As we were discussing recently, maybe starting with anycast DNS
servers on satellites is a first step to consider, before embarking
any other type of cloud servers.
Regards,
David
> Date: Thu, 20 Apr 2023 04:33:00 +0000
> From: Ulrich Speidel <u.speidel@auckland.ac.nz>
> To: "tom@evslin.com" <tom@evslin.com>, 'Michael Richardson'
> <mcr@sandelman.ca>, 'starlink' <starlink@lists.bufferbloat.net>,
> "e-impact@ietf.org" <e-impact@ietf.org>
> Subject: Re: [Starlink] DataCenters in Space (was Re: fiber IXPs in
> space)
> Message-ID:
> <SY4PR01MB697983BB5DEB1B2AA0B2690BCE639@SY4PR01MB6979.ausprd01.prod.outlook.com>
>
> Content-Type: text/plain; charset="windows-1252"
>
> Where do I even start? The lack of substantial bandwidth between space and
> ground? The extra latency between ground and space compared to terrestrial
> cloud, especially as terrestrial cloud edge can move much closer to
> customers when space can't? The fact that every LEO satellite is both a few
> 100 km from every customer and out of the customer's range depending on when
> you look? That low temperatures in space don't mean superconductive chips
> that produce zero heat, and that that heat is difficult to get rid of in
> space? That generating power in space is orders of magnitude more expensive
> than on the ground?
>
> Just because Starlink can provide a service somewhere between DSL and low to
> medium grade fibre to a few million around the globe it's not "done". Even
> with 10x the number of satellites and a couple of times the current capacity
> per satellite, Starlink isn't going to supply more than a couple of 100
> million at best, and that's not even accounting for growth in demand from
> IOT...
>
> --
>
> ****************************************************************
> Dr. Ulrich Speidel
>
> School of Computer Science
>
> Room 303S.594 (City Campus)
> Ph: (+64-9)-373-7599 ext. 85282
>
> The University of Auckland
> ulrich@cs.auckland.ac.nz<mailto:ulrich@cs.auckland.ac.nz>
> http://www.cs.auckland.ac.nz/~ulrich/
> ****************************************************************
next parent reply other threads:[~2023-04-20 12:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.751.1681965188.1222.starlink@lists.bufferbloat.net>
2023-04-20 12:24 ` David Fernández [this message]
2023-04-20 16:14 ` Michael Richardson
2023-04-20 16:20 ` David Lang
2023-04-20 21:34 ` Eugene Chang
2023-04-20 22:07 ` Spencer Sevilla
2023-04-20 22:11 ` David Lang
2023-04-21 0:03 ` tom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC=tZ0qpTB7-P6eCw6ow5AG8Ca=47gM8a4UGFmTRDH06UxeoTA@mail.gmail.com' \
--to=davidfdzp@gmail.com \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox