The purpose of the 3scale mixer adapter is to complement the functionality of a service mesh in the management of internal APIs. However, this lab currently concludes with the student using 3scale mixer adapter to manage a request originating from external to the service mesh.
This lab should provide an additional section where the request works its way through several internal APIs. ie: shopping cart -> catalog service -> inventory service. Consequently, the focus of the lab will switch to API (via 3scale) and traffic management (via Istio) of internal APIs.
To support this, the shopping cart and inventory service will need to be injected with Jaeger libraries and OpenTracing spans should be programmatically created in the functions of those services. This is similar to what has already been done for the catalog service
The purpose of the 3scale mixer adapter is to complement the functionality of a service mesh in the management of internal APIs. However, this lab currently concludes with the student using 3scale mixer adapter to manage a request originating from external to the service mesh.
This lab should provide an additional section where the request works its way through several internal APIs. ie: shopping cart -> catalog service -> inventory service. Consequently, the focus of the lab will switch to API (via 3scale) and traffic management (via Istio) of internal APIs.
To support this, the shopping cart and inventory service will need to be injected with Jaeger libraries and OpenTracing spans should be programmatically created in the functions of those services. This is similar to what has already been done for the catalog service