An objective of the Substrates API is that it should be possible for developers to be location independent in that code can execute without change within the local process itself or a remote server that is being served the data via a Relay.
Author: William David Louth
Simplifying Instrument Synthesis
Three overriding principles are applied in the design of the Substrates API - consistency (standardizing), conciseness (simplifying), and correctness (sequencing).
API Design – A Moving Target
Good design takes time, over many iterations (of converging and diverging design paths), in developing, discovering, discussing, discounting, and occasionally destroying.
Data Pipeline Segmentation
The stages within a local data pipeline managed by the Substrates runtime are detailed, from a client call to an Instrument interface method to dispatching an Event to an Outlet registered by a Subscriber.
Playing with Pipelines
A walk through of one of the Substrates showcase examples hosted on GitHub, demonstrating two of the most critical aspects of pipelines – the production and consumption of captured data and published events.
Pipelines Reimagined
Using Substrates, the fusion of multiple streams of data from multiple sources, an essential process of any monitoring and management solution, can be done in-process and in real-time.
Circuits, not Pipelines!
The first official release of the Substrates API is nearing completion. With that, it is time to explore one of the toolkit's most significant differences compared to other approaches, such as OpenTelemetry.
Humainary vs OpenTelemetry – Spatial
For Humainary, the goal is to encourage as much as possible the analytical processing of observations at the source of event emittance and in the moment of the situation. To propagate assessments, not data.
A Roadmap for an Observability Toolkit
We have divided up our mission for the Humainary Toolkit into three phases, with each phase mapping to one or more layers: Measure, Model, and Memory
Measurement and Control 2022
Since the very beginning of the hype of Observability, we have contended that the link with Controllability must be maintained for there ever to be a return on investment (ROI) that matches the extravagant claims from vendors pushing a message of more-is-better.