Document shared with you: "Edge-Native Application Design Behaviors"

[Andy Anderson (via Google Docs)]

Andy Anderson shared a document Andy Anderson (anda...@redhat.com) has shared a link to the following document: Edge-Native Application Design Behaviors Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA You have received this email because anda...@redhat.com shared a document with you from Google Docs.

[Mark Abrams]

Hoping we will talk through this at an upcoming WG meeting. When we talk about there being multiple edges, I think we may have to call those out and make design distinctions accordingly. For example, with my customers; I see HPC at the edge. I see mixed air gap and remote managed edge where the primary deployment model and runtime model is still cloud-native. I see multi-modal edge with vms living side by side with containers. I see device edge which looks like IoT but is a cloud native single node stack. 

What I don't see is a requirement for cloud backed edge. Cloud (DC) often comes in as a "requirement" because it provides means to configure and manage at scale but it's not a hard requirement.

--
You received this message because you are subscribed to the Google Groups "kubernetes-wg-iot-edge" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-wg-iot...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-wg-iot-edge/autogen-java-0960906a-4e3b-4d25-9f48-ec13ad95d353%40google.com.

[Kit Plummer]

Would love to see and support discussion about what P2P configuration and data synchronization might look like in n-node Edge topologies where cloud-backed/to-cloud connectivity is severely limited/constrained or non-existent.

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-wg-iot-edge/CAAB%2BMYQMK3njuANLXiizVLwoKHrJx%3DaAX93%3DpyS7jDnKXzo_9A%40mail.gmail.com.