The image shows the architecture as described in the surrounding text.
The architecture includes SaaS solutions, On-premises APIs, an OCI Region with a VCN and Oracle Services Network, third-party cloud components for Microsoft, and users and Admins on the Internet.
On the left are SaaS and On-Premises content. SaaS solutions includes Fusion Retail, Supply Chain Planning and Order Management with two-way interaction with on-premises REST APIs and Integration for Shipped Packages Feed and Package Images.
The VCN has a Public Subnet and a Private Subnet and three Fault Domains. The Bastion Service is in the Public Subnet in Fault Domain 1. The Load Balancer is in the Public Subnet in Fault Domain 2. Oracle Autonomous Data Warehouse is in the Private Subnet in Fault Domain 2 and Oracle Analytics Cloud is in the Private Subnet in Fault Domain 3.
There's two-way communication between the Load Balancer and the Oracle Autonomous Data Warehouse in the public and private subnet. There's two-way communication between Oracle Autonomous Data Warehouse and Oracle Analytics Cloud in the private subnet.
The following is the workflow between Oracle Services Network on the OCI Region and the other components in the architecture:
The third-party cloud in this architecture includes Microsoft Azure and Microsoft Teams. There's two-way communication between Microsoft and the Internet. The Admin on the internet has two-way dotted line communication with Oracle Digital Assistant to visualize all package data. Microsoft Teams also has two-way dotted line communication between Oracle Digital Assistant.
The Admin can send and receive requests to Oracle Analytics Cloud to query for damaged packages.