Explanation
Service Aggregator Pattern
Another option for eliminating microservice-to-microservice coupling is an Aggregator microservice, shown in purple in Figure 4-10.

The pattern isolates an operation that makes calls to multiple back-end microservices, centralizing its logic into a specialized microservice.The purple checkout aggregator microservice in the previous figure orchestrates the workflow for the Checkout operation. It includes calls to several back-end microservices in a sequenced order. Data from the workflow is aggregated and returned to the caller. While it still implements direct HTTP calls, the aggregator microservice reduces direct dependencies among back-end microservices.
References:
https://docs.microsoft.com/en-us/dotnet/architecture/cloud-native/service-to-service-communication#:~:text=Ser

Explanation
Token-based authentication for the CLI:
Token-based authentication for the CLI allows customers to authenticate their session interactively, then use theCLI for a single session without an API signing key. This enables customers using an identity provider that is not SCIM-supported to use a federated user account with the CLI and SDKs.
Starting a Token-based CLI Session
To use token-based authenticationfor the CLI on a computer with a web browser:
1. In the CLI, run the following command. This will launch a web browser.
oci session authenticate
2. In the browser, enter your user credentials. This authentication information is saved to the .config file.
Validating a Token
To verify that a token is valid, run the following command:
oci session validate --config-file <path_to_config_file> --profile <profile_name> --auth security_token You should receive a message showing the expiration date for the session.If you receive an error, check your profile settings.
References:
https://docs.cloud.oracle.com/en-us/iaas/Content/API/SDKDocs/clitoken.htm

Explanation
Setting Up Local Access to Clusters
To set up a kubeconfig file to enable access to a cluster using a local installation of kubectl and theKubernetes Dashboard:
Step 1: Generate an API signing key pair
Step 2: Upload the public key of the API signing key pair
Step 3: Install and configure the Oracle Cloud Infrastructure CLI
Step 4: Set up the kubeconfig file
Step 5: Verify that kubectl can access the cluster
References:
https://docs.cloud.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengdownloadkubeconfigfile.htm

Explanation
https://docs.cloud.oracle.com/en-us/iaas/Content/API/Concepts/sdks.htm
* Software Development Kits (SDKs)Build and deploy apps that integrate with Oracle Cloud Infrastructure services. Each SDK provides the tools you need to develop an app, including code samples and documentation tocreate, test, and troubleshoot. In addition, if you want to contribute to the development of the SDKs, they are all open source and available on GitHub.
* SDK for Java
* Python SDK
* Ruby SDK
* Go SDK
https://docs.cloud.oracle.com/en-us/iaas/Content/API/Concepts/sdkconfig.htm