Resource Inventory Management API
Ingest and expose physical, logical, and virtual resources. Maps vendor-specific schemas into normalized standard resources.
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.
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.
Ingest and expose physical, logical, and virtual resources. Maps vendor-specific schemas into normalized standard resources.
Discover customer and resource-facing services (CFS/RFS). Correlates abstract services to underlying topology elements.
Subscribe to and correlate network faults against inventory topology to automatically determine service impact.
Stream and attach performance metrics to inventory nodes for SLA tracking and anomaly detection.
Real-time ingestion pipelines capable of processing millions of network state changes, backed by a property graph database for sub-millisecond relationship traversals.
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
Stream Processing
Stateful stream processing for entity resolution, schema normalization, and temporal join queries across telemetry streams.
Job: normalize_resource()
Job: correlate_fault()
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)
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.
All northbound systems route requests to the new API Gateway, which initially proxies 100% of traffic to the legacy monolithic inventory.
The Agent begins ingesting state changes from legacy inventory and network elements in parallel, populating the Neo4j graph without interfering with active read paths.
The Gateway routing logic is updated to direct specific queries (e.g., TMF638 Service lookups) to the new Agent, while legacy handles the rest.
As confidence builds, more domains are migrated until the legacy inventory can be safely decommissioned.
Traffic Splitter & Router
Modern Graph Store
Relational DB
Get detailed architecture diagrams, deployment prerequisites, and an exhaustive list of supported vendor integrations and TMF APIs. No marketing fluff, just engineering specs.