openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From TzuChiao Yeh <>
Subject Re: Proposing Lean OpenWhisk
Date Tue, 17 Jul 2018 14:46:48 GMT
Hi David,

Looks cool! Glad to see OpenWhisk step forward to the edge use case.

Simple question: have you considered the way that remove out docker
containers (break up isolation)?

Due to close-source, I'm not sure how aws greengrass did, but seems like
there's no docker got installed at all.

The edge computing benefits for some advantages,
1. bandwidth reduction.
2. lower latency.
3. offline computing capability (not for all scenarios, but this is indeed
aws greengrass claimed for).

We can first ignore the use cases that required ultra low-latency (i.e.
interactive AR/VR, speech language translation). But for general use cases,
cold start problem in serverless makes low latency no sense. Since there's
only about 100-200ms RTT from device to cloud, but container
creation/deletion is much higher. Besides from this, (part of) edge devices
are not provided as an IaaS service, therefore we can even care no
multi-tenancy or weaker isolation. What do you think?

Tzu-Chiao Yeh (@tz70s)

On Tue, Jul 17, 2018 at 9:43 PM David Breitgand <> wrote:

> Sure. Will do directly on Wiki.
> Cheers.
> -- david
> From:   "Markus Thoemmes" <>
> To:
> Date:   17/07/2018 04:31 PM
> Subject:        Re: Proposing Lean OpenWhisk
> Hi David,
> I absolutely agree, this should not be held back. It'd be great if you
> could chime in on the discussion I opened on the new proposal regarding
> your use-case though. It might be nice to verify a similar topology as you
> are proposing is still implementable or maybe even easier to implement
> when moving to a new architecture, just so we have all requirements to it
> on the table.
> I agree it's entirely orthogonal though and your proposal can be
> implemented/merged independent of that.
> Cheers,
> Markus

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message