Hi everyone! 👋

It's been another packed week for Edge. I've said it before and I'll say it again: I'm amazed by the volume and quality of the work that is being produced by the team.

The engineering team have been cracking on with work on the front end to our publishing tools, specifically working on mobile compatibility for collection and documents views.

They also released CDN v4.0.0 RC1, which is currently being tested under test.network on the network.

Alongside this, updates were made to the current release candidate of API (6.0.0 RC2), fixing some issues that arose from the ongoing testing and adding some requested features around media.

A strong start was made on documentation for the upcoming features for API in support of our SaaS proposition, particularly building OpenAPI specs for new endpoints. This work led to a review of the existing OpenAPI specs, as well as writing new ones for the parts of API that were not covered (e.g. the REST interface for managing documents).

This is an an important step to take as part of our vision for the revamped documentation, allowing us to convey information about the various endpoints in visualisations such as this one:

Work on the Go version of CDN moved forward strongly, with another modifier being introduced, this time for entropy.

The application has also been undergoing performance benchmarking, with a feedback loop leading to improved performance under heavy load.

The focus for this development stream is both performance and footprint for the application. The currently deployed build of CDN weighs in at ~568MB, which while workable in the current device set, presents serious issues for embedded devices. It also uses up a lot of disk space that could otherwise be being used for Object Storage.

The new version is currently sat at ~14MB – a huge improvement.

The team have also been working on further securing the network, introducing an encrypted network overlay to remove the ability to snoop on container-to-container traffic.

Work was finished on the consensus mechanism used by gateways as part of the distributed DAG (the database used for storing file shards and other data for Edge's next milestone release).

Work was undertaken to improve the consul session capture routine, which is now much more performant as a result.