Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 33 Next »



The below is a snapshot of where the existing projects under LF Edge currently sit. Updates to the taxonomies should be requested through the Project's TAC representative. The Glossary Project will further define the terminology as outlined below.



Last Updated:

  • Akraino (May 16, 2019)
  • EdgeX (June 3, 2019)
  • Fledge (FogLAMP) (June 27, 2019)
  • Home Edge
  • OpenEdge (July 22, 2019)
  • Project EVE (June 3, 2019) Align center

Existing Projects by Function (Provide, Consume, Facilitate, or N/A; Add context as needed)

FunctionsAkrainoEdgeXFledgeHome EdgeOpenEdgeProject EVE
APIsProvideProvideProvide, Consume, Facilitate - Microcontroller Example - South Microservice (esp8266)
ProvideProvide
Cloud ConnectivityProvideProvideProvide, Consume and Facilitate - North repos, GCP, OSI-OMF
Provide, not only Baidu CloudProvide
Container Runtime & OrchestrationProvideConsumeConsume - (debian, rpm, docker, Project Eve)
ConsumeProvide for Edge Container
Data GovernanceNA
Provide and Facilitate - Auditing logs and asset tracking.
Provide
Data ModelsProvide
Provide, Consume and Facilitate
N/AProvide for Edge Container (not app data)
Device ConnectivityProvideProvideProvide, Consume and Facilitate
Provide, MQTT protocolProvide (incl LTE, WiFi, serial)
Filters/Pre-processingProvideProvideProvide and Facilitate
Provide
LoggingProvideProvideConsume
ProvideProvide for its own runtime
Management UIProvideFacilitateProvide, Consume and Facilitate
Provide, not determined yetProvide for its own runtime
Messaging & EventsProvideProvideProvide, Consume and Facilitate
Provide
Notifications & AlertsProvideProvideProvide, Consume and Facilitate
Provide, under developing
SecurityProvideProvideProvide, Consume and Facilitate
ProvideProvide
StorageProvideProvideProvide, Consume and Facilitate - Buffering
ProvideProvide (local virtual disks)

Existing Projects by Deployment & Industry Verticals (Support, Possible, N/A; Add context as needed)

Deployment TypeAkrainoEdgeXFledgeHome EdgeOpenEdgeProject EVE
Customer Devices (Edge Nodes)SupportSupportSupport
SupportSupport
Customer Premises (DC and Edge Gateways)SupportSupportSupport
SupportSupport
Telco Network Edge (MEC and Far-MEC)SupportPossiblePossible
SupportPossible
Telco CO & RegionalSupport
Possible
Support
Cloud Edge & CDNsSupportPossiblePossible
Support
Public CloudSupportPossibleN/A
Support
Private CloudSupportPossibleN/A
Support

Existing Projects by Deployment & Industry Verticals (✔ or X; Add context as needed)

Directly applicable Industry/Verticals use casesAkrainoEdgeXFledgeHome EdgeOpenEdgeProject EVE
Automotive / Connected Car
X

Chemicals

X
Facilities / Building automation

ConsumerX
X
Manufacturing✔ - Production deployments
Metal & Mining
✔ - PoCs

Oil & Gas✔ - PoCs
Pharma✔ - PoCs
X
Health Care

X
X
Power & Utilities✔ -  Production deployments
Pulp & Paper

X
Telco Operators
X

Telco/Communications Service Provider (Network Equipment Provider)
X

Transportation (asset tracking)X

Supply Chain
X

Preventative Maintenance
✔ -  Production deployments (Not a vertical)

Water Utilities
✔ - PoCs
X
Security / Surveillance
 X
Retail / Commerce (physical point of sale with customers)
 X
X
Other - Please add if not listed above (please notify TAC-subgroup@lists.lfedge.org when you add one)






Deployments (static v dynamic, connectivity, physical placement) - (✔ or X; Add context as needed)

Use CasesAkrainoEdgeXFledgeHome EdgeOpenEdgeProject EVE
Gateways (to Cloud, to other placements)
NFV Infrastructure
X
X
Stationary during their entire usable life / Fixed placement edge constellations / Assume you always have connectivity and you don't need to store & forward.X
Stationary during active periods, but nomadic between activations (e.g., fixed access) / Not always assumed to have connectivity. Don't expect to store & forward.X
Mobile within a constrained and well-defined space (e.g., in a factory) / Expect to have intermittent connectivity and store & forward.
Fully mobile (To include: Wearables and Connected Vehicles) / Bursts of connectivity and always store & forward.
X

Compute Stack Layers (architecture classification) - (Provide, Require, or N/A; Add context as needed)

Compute Stack LayersAkrainoEdgeXFledgeHome EdgeOpenEdgeProject EVE
APIsProvideProvideProvide
ProvideProvide
ApplicationsDeployedProvideProvide
Provide
FirmwareUpdate and Configure
Require
Provide, OS as a Firmware
HardwareProvision and ConfigureRequireRequire
RequireRequire
OrchestrationRequire
N/A
RequireProvide
OSRequireRequireRequire
ProvideProvide
VM/ContainersRequireProvideRequire
Require, vm is optionalProvide

Cloud Stack Layers (architecture classification) - (Provide, Require, or N/A; Add context as needed)

Cloud Stack LayersAkrainoEdgeXFledgeHome EdgeOpenEdgeProject EVE
ApplicationsProvide (services can live in cloud layer)N/A
Yes
Configuration (drive)
N/A
Yes
Content (management system)
N/A
Yes
IaaS
N/A
NoProvide (at Edge but not cloud)
PaaS
N/A
Yes
Physical Infrastructure
N/A
No
SaaS
N/A
No
  • No labels