Oracle 1Z0-1084-22 PDF Exam Questions:

Service Aggregator Pattern

Another option for eliminating microservice-to-microservice coupling is anAggregator microservice, shown in purple in Figure 4-10.

The pattern isolatesanoperation that makes calls to multipleback-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=Service%20Aggregator%20Pattern&text=The%20pattern%20isolates%20an%20operation,logic%20into%20a%20specialized%20microservice.&text=While%20it%20still%20implements%20direct,dependencies%20among%20back%2Dend%20microservices.

Oracle Functions Concepts:

This topic describes key concepts you need to understand when using Oracle Functions.

Applications:

In Oracle Functions, an application is:

1. a logical grouping of functions

2. a common context to store configuration variables that are available to all functions in the application

3. a way to ensure function runtime isolation

When you define an application in Oracle Functions, you specify the subnets in which to run the functions in the application. When functions from different applications are invoked simultaneously, Oracle Functions ensures these function executions are isolated from each other.

Oracle Functions shows applications and their functions in the Console.

References:

https://docs.cloud.oracle.com/en-us/iaas/Content/Functions/Concepts/functionsconcepts.htm

A PersistentVolume (PV)is a piece of storage in the cluster that has been provisioned by an administrator. PVs are volume plugins like Volumes, but have a lifecycle independent of any individual Pod that uses the PV.

A PersistentVolumeClaim (PVC)is a request for storage by a user. It is similar to a Pod. Pods consume node resources and PVCs consume PV resources.

If you intend to create Kubernetes persistent volumes, sufficient block volume quota must be available in each availability domain to meet the persistent volume claim. Persistent volume claims must request a minimum of 50 gigabytes

You can define and apply a persistent volume claim to your cluster, which in turn creates a persistent volume that's bound to the claim. A claim is a block storage volume in the underlying IaaS provider that's durable and offers persistent storage, enabling your data to remain intact, regardless of whether the containers that the storage is connected to are terminated.

With Oracle Cloud Infrastructure as the underlying IaaS provider, you can provision persistent volume claims by attaching volumes from theBlock Storage service.

https://oracle.github.io/weblogic-kubernetes-operator/faq/oci-fss-pv/

https://kubernetes.io/docs/concepts/storage/persistent-volumes/

https://docs.cloud.oracle.com/en-us/iaas/Content/Streaming/Concepts/streamingoverview.htm

If you use theFn Project CLI or the Oracle Cloud Infrastructure CLI to invoke a function,authentication is handled for you.SeeUsing the Fn Project CLI to Invoke FunctionsandUsing the Oracle Cloud Infrastructure CLI to Invoke Functions.

If you use an Oracle Cloud Infrastructure SDK to invoke a function, you can use the SDK to handle authentication. SeeUsing SDKs to Invoke Functions.

If you make a signed HTTP request to a function's invoke endpoint, you'll have to handle authentication yourself by including a signature and the OCID of the compartment to which the function belongs in the request header

Fn Project CLIyou can create an Fn Project CLI Context to Connect to Oracle Cloud Infrastructure and specify --provider oracle This option enables Oracle Functions to perform authentication and authorization using Oracle Cloud Infrastructure request signing, private keys, user groups, and policies that grant permissions to those user groups.

References:

https://blogs.oracle.com/developers/oracle-functions-invoking-functions-automatically-with-cloud-events

https://docs.cloud.oracle.com/en-us/iaas/Content/Functions/Tasks/functionsinvokingfunctions.htm