Integration & APIs

Standardized Interfaces for
Intelligent Inventory

Open Digital Architecture (ODA) aligned APIs, real-time event streaming pipelines, and secure data contracts. Built to seamlessly integrate the Inventory Intelligence Agent into legacy OSS landscapes.

TM Forum Open API Compliance

Azalio's Inventory Intelligence Agent speaks the language of modern OSS. By implementing certified ODA components and standard TMF APIs, we eliminate proprietary integration debt.

TMF639

Resource Inventory Management API

Ingest and expose physical, logical, and virtual resources. Maps vendor-specific schemas into normalized standard resources.

GET/resource
POST/resource
PATCH/resource/{id}
TMF638

Service Inventory Management API

Discover customer and resource-facing services (CFS/RFS). Correlates abstract services to underlying topology elements.

GET/service
POST/service
PATCH/service/{id}
TMF642

Alarm Management API

Subscribe to and correlate network faults against inventory topology to automatically determine service impact.

POST/alarm
GET/alarm
POST/hub
TMF628

Performance Management API

Stream and attach performance metrics to inventory nodes for SLA tracking and anomaly detection.

POST/measurementCollectionJob
GET/measurement

Event-Driven Telemetry & Topology Stack

Real-time ingestion pipelines capable of processing millions of network state changes, backed by a property graph database for sub-millisecond relationship traversals.

Data Sources

  • NMS & EMS Systems
  • Passive Probes
  • Active Orchestrators
  • Device Configs (CLI/NETCONF)

Apache Kafka

Event Backbone

High-throughput distributed event streaming platform handling backpressure, retry logic, and guaranteed delivery of network events.

Topic: network.topology.raw

Topic: network.alarm.stream

Apache Flink

Stream Processing

Stateful stream processing for entity resolution, schema normalization, and temporal join queries across telemetry streams.

Job: normalize_resource()

Job: correlate_fault()

Neo4j Graph

Topology Store

Native property graph database connecting normalized physical, logical, and service inventory entities with multi-hop relationships.

(Service)-[DEPENDS_ON]->

(Logical)

(Logical)-[HOSTED_ON]->

(Physical)

Strangler Pattern Migration Strategy

Replacing a legacy inventory monolith introduces immense operational risk. Azalio employs the Strangler Fig pattern to systematically decouple dependencies, routing API traffic intelligently and deprecating legacy systems domain-by-domain without downtime.

1

Introduce API Gateway Facade

All northbound systems route requests to the new API Gateway, which initially proxies 100% of traffic to the legacy monolithic inventory.

2

Stand up Inventory Intelligence Agent

The Agent begins ingesting state changes from legacy inventory and network elements in parallel, populating the Neo4j graph without interfering with active read paths.

3

Traffic Routing & Cutover

The Gateway routing logic is updated to direct specific queries (e.g., TMF638 Service lookups) to the new Agent, while legacy handles the rest.

4

Deprecate Legacy Modules

As confidence builds, more domains are migrated until the legacy inventory can be safely decommissioned.

Northbound Clients (BSS / Assurance)

Intelligent API Gateway

Traffic Splitter & Router

Inventory Intelligence Agent

Modern Graph Store

Handling 60% Traffic

Legacy Monolith

Relational DB

Deprecating (40% Traffic)

Ready to review the full capability map?

Get detailed architecture diagrams, deployment prerequisites, and an exhaustive list of supported vendor integrations and TMF APIs. No marketing fluff, just engineering specs.