Open API
An Open API is central to all of our products representing the foundation on which tools, extensions, plugins and add-ons are built. Excellence in the design of an Open API enables great flexibility, versatility, performance and scalability in the resulting implementation tailored to a particular workload, environment or execution context.
To date we have engineered three critically acclaimed Open APIs (Probes, Metrics and Diagnostics) with new Open API designs in the works – most notably our new innovative Signals Open API.
Probes (JXInsight/OpenCore) – An adaptive activity based metering and control runtime for the next generation of self adaptive application software
Metrics (JXInsight/OpenCore) – An extensible and scalable application software metric monitoring framework
Signals (JXInsight/Signals) – A low latency software behavioral analysis runtime that brings complex event processing to the JVM platform
How (not) to design a Metrics API
A series of articles on how best to design an application metrics monitoring library, in particular its API, providing versatility both in terms of application of the library across domains & environments and in its implementation by one or more vendors. In the series we will discuss the underlying thought process, principles and patterns guiding the design and development of the JXInsight/OpenCore Metrics API and in turn compare it with other libraries that don’t exhibit the resulting qualities which have emerged from such software engineering discipline.
Part 1: Information Model versus Management Model
Part 2: Delegation and Separation
Part 3: Groups, Collections and Samples
Part 4: Naming and Names
Part 5: Alternatives to Reset