Aria Allegro Architecture
This section provides a high-level overview of the Aria Allegro block architecture and its integration with Core Aria. It may not be required to share this section externally unless the Client wants to manage the operations on their own. The main purpose of this section is to understand the component architecture, likely failure causes, and scalability mechanisms.
Aria Allegro is a cloud-native, true SaaS microservices architecture. Each microservice serves a specific purpose and offers independent on-demand scalability.
Refer to the respective documentation sections for more details.
- Usage Processing Block Architecture
- The article describes the high-level architecture of the Aria Allegro usage processing framework, covering how usage files move from various external sources through S3 storage, microservices, Kafka topics, and the Allegro database. It summarizes the end-to-end flow from file ingestion and validation through mediation, rating and discounting, and finally to monetized usage records and UI-based monitoring and exception handling.
- Catalog-Account Sync Block Architecture
- This article explains how catalog and account data are synchronized from core Aria to Aria Allegro using a data feed that publishes JSON events to a Kafka topic. It describes how the Aria Allegro Sync Service processes these events into Allegro objects, handles errors, and provides a UI for reviewing and reprocessing sync activities.
- Monetized Usage Record Sync
- This article explains how Aria Allegro aggregates monetized usage records and synchronizes them to core Aria in controlled batches using the bulk_record_usage_m API, with batch size managed via system configuration. It outlines the roles of the Scheduler, Allegro Operations service, Allegro Sync Service, and Allegro UI in finding unsynced records, aggregating them, sending them through Kafka for bulk API processing, and allowing review and reprocessing of failed records.
- Allegro API Call Interfaces
- The article describes the Aria Allegro API call architecture, outlining how Core Aria, Allegro services, and external applications interact through GraphQL, TM Forum Open APIs, and a general API Gateway. It summarizes six main interface components, including job scheduling, monetized usage synchronization, Allegro UI and Core services, and upcoming TM Forum and JSON/SOAP gateways.