NOTE: California has been released. See the release page for details of this release.
Table of Contents
Delivery: ~June 2018
The main theme for the California release of EdgeX is to provide a solid open source foundation for commercialization and deployment in a wide variety of IoT edge use cases.
...
- Convert all core and supporting services to Go Lang. Many of the services have been refactored since the California Preview so as to align better with Go Lang patterns and practices.
- Upgrade of Consul (from 0.7 to 1.0)
Export Service Tasks and Notes
...
The target is to run all of EdgeX (all the services to include the virtual device service) on a Raspberry Pi 3 (1 GB RAM, 64bit CPU, at least 32GB storage space, running Raspbian Linux distro)
This is not an endorsement of the platform as our favorite or otherwise endorsed platform
It only suggests the general characteristics of a “developer community” target platform
This may not be entirely feasible without all Go replacements, but is the target and the development community will report back when/where this is not possible
For example, it is unlikely the target security implementation will fit on this size platform
Additional “developer community” targets
Startup in 1 minute or less (post OS boot – from micro service start to all services up and available)
Throughput for one piece of data (with one IP device connected by hard wire – versus WiFi) from data ingestion at the Device Service layer, through Core Data, to Rules Engine and back down through Command Service finally to Device Service for actuation will be < 1 second
· Institute an OS reverse proxy (Kong) to protect the micro service APIs from unauthorized outside requests.
o This will be for HTTP/S only (meaning security for MQTT and other protocols will not yet be provided)
o With no (or very few) changes to existing micro services at this time
· Data Protection Services via HashiCorps’s Vault is integrated with EdgeX
...