Making eventual consistency cache updates deterministic

Techniques for making eventual consistency cache updates deterministic. One technique includes receiving, at a control plane, a request to execute an operation on data, executing the operation on the data, creating a replication event for the operation and a replication identifier associated with the replication event, sending a response that includes a custom header having the replication identifier, receiving, at a data plane, a subsequent request to execute an operation involving the data, the subsequent request includes the replication identifier, retrieving a replication identifier for a latest replication event executed on the data plane, comparing the replication identifier from the subsequent request and the replication identifier for the latest replication event, determining the replication event associated with the replication identifier from the subsequent request has not been executed on the data plane based on the comparison, and sending a deterministic error message to the client device.

FIELD OF THE INVENTION

The present disclosure relates generally to data integration, and more particularly, to techniques for making eventual consistency cache updates deterministic.

BACKGROUND

Integrating data and applications throughout an enterprise, and presenting them in a unified view is a complex proposition. Not only are there broad disparities in technologies, data structures, and application functionality, but there are also fundamental differences in integration architectures. Some integration needs are data oriented, especially those involving large data volumes. Other integration projects lend themselves to an Event Driven Architecture (EDA) or a Service Oriented Architecture (SOA), for asynchronous or synchronous integration. Data integration ensures that information is timely, accurate, and consistent across complex systems. Although data integration is frequently referred as Extract-Transform-Load (ETL)—data integration was initially considered as the architecture used for loading enterprise data warehouse systems—however data integration now includes data movement, data synchronization, data quality, data management, and data services.

A data integrator provides a solution for building, deploying, and managing complex data warehouses or as part of data-centric architectures in a SOA or business intelligence environment. In addition, the data integrator combines all the elements of data integration—data movement, data synchronization, data quality, data management, and data services—to ensure that information is timely, accurate, and consistent across complex systems. An example of a data integrator is the Oracle Data Integrator (ODI), which features an active integration platform that includes all styles of data integration: data-based, event-based and service-based. ODI unifies silos of integration by transforming large volumes of data efficiently, processing events in real time through its Changed Data Capture (CDC) framework, and providing data services to the Oracle SOA Suite. ODI also provides robust data integrity control features, assuring the consistency and correctness of data.

The data integrity control features of a data integrator such as ODI typically include automated integration testing. Integration tests often involve running end-to-end ETL, data movement, data synchronization, data quality, data management, and data service routines that may invoke various components and data across a data plane. To ensure that all components and data processing completed as expected, the developers and quality assurance team will want to determine whether the correct end-to-end ETL, data movement, data synchronization, data quality, data management, and data service routines executed and whether key business rules were properly applied. In other words, they will want the integration test to repeat many of the unit and individual component tests. However, the challenges of integration testing are substantially different from conventional software testing. For example, challenges typically include incompatibility of data, loss of data, volume and complexity of data, faults in the business process and procedures, missing business flow information, failed or delayed replication of data, and unavailability of testing data or testing processes. Accordingly, efficient techniques for data integration and particularly integration testing are desired.

BRIEF SUMMARY

Techniques are provided (e.g., a method, a system, non-transitory computer-readable medium storing code or instructions executable by one or more processors) for making eventual consistency cache updates deterministic.

In various embodiments, a method is provided for that comprises: receiving, at a control plane of a computing system, a first request to execute a first operation on data, wherein the request is received from a client device; executing, by the computing system, the first operation on the data; creating, by the computing system, a replication event for the operation and a first replication identifier associated with the replication event, where the replication event will be used to replicate execution of the first operation on a data plane; sending, by the computing system, a response back to the client device concerning the execution of the first operation on the data, where the response comprises a custom header having the first replication identifier; receiving, at the data plane of the computing system, a second request to execute a second operation involving the data, where the second request is received from the client device and includes the custom header having the first replication identifier; in response to receiving the second request, retrieving, by the computing system, a second replication identifier for a latest replication event executed on the data plane; comparing, by the computing system, the first replication identifier and the second replication identifier; determining, by the computing system, whether the replication event associated with the first replication identifier from the custom header has been executed on the data plane based on the comparison between the first replication identifier and the second replication identifier; and in response to determining the replication event has not been executed on the data plane, sending, by the computing system, an error message to the client device, where the error message is indicative that the replication event has not been executed on the data plane.

In some embodiments, the first request is to create, read, update, and/or delete the data, which is to be or presently integrated as part of an application to be or presently deployed on the computing system, and where the error message is deterministic that the replication event has not been executed on the data plane.

In some embodiments, the executing the first operation comprises: creating, by the computing system, a resource that schedules a background task to run and produce another resource that requires replication; in response to scheduling the background task, writing, by the computing system, a substitute replication identifier associated with the background task and the first operation to a data table, where the response comprises the custom header having the substitute replication identifier rather than the first replication identifier; executing, by the computing system, the background task to run and produce the another resource that requires replication; and in response to completing execution of the background task, writing, by the computing system, the first replication identifier associated with the first operation to the data table.

In some embodiments, the second request includes the custom header having the substitute replication identifier; and in response to receiving the substitute replication identifier, identifying, by the computing system, the first replication identifier from the data table using the substitute replication identifier as a key.

In some embodiments, the method further comprises: writing, by the computing system, the first request to an inbox table in a replication database located within a subscriber region, where the control plane is located within a home region; and writing, by the computing system, the first replication identifier associated with the first operation to a data table, where the executing the first operation comprises: executing, by a backfill processor within the subscriber region of the computing system, the first operation of the first request from the inbox table in the replication database; and in response to executing the first operation within the subscriber region, writing, by the computing system, a substitute replication identifier associated with first operation to the data table, wherein the response comprises the custom header having the substitute replication identifier rather than the first replication identifier.

In some embodiments, the second request includes the custom header having the substitute replication identifier; and in response to receiving the substitute replication identifier, identifying, by the computing system, the first replication identifier from the data table using the substitute replication identifier as a key.

In some embodiments, the determining whether the replication event associated with the first replication identifier from the custom header has been executed on the data plane comprises determining whether the first replication identifier from the custom header of the second request issued prior to, at the same time, or after issuance of the second replication identifier for the latest replication event.

In various embodiments, a system is provided that includes one or more data processors and a non-transitory computer readable storage medium containing instructions which, when executed on the one or more data processors, cause the one or more data processors to perform part or all of one or more methods disclosed herein.

In various embodiments, a computer-program product is provided that is tangibly embodied in a non-transitory machine-readable storage medium and that includes instructions configured to cause one or more data processors to perform part or all of one or more methods disclosed herein.

DETAILED DESCRIPTION

Introduction

In computing, a control plane is the part of the software that configures and controls the data plane. For example, the control plane may be used for adding, updating, and removing data (e.g., in terms of an authentication system—creation of users, entities, and policies governing users access) on the data plane. In contrast, the data plane (sometimes referred to as the forwarding plane) is the part of the software that processes the data requests (e.g., implements business logic). For example, the data plane takes the users, entities, and policies, and implements business logic on top of them (e.g., authentication and authorization). When data is added, updated, and removed on the control plane, an integration process is executed (e.g., via a data integrator) to replicate those operations and data changes on the data plane. The integration of data on the data plane may then be tested using integration testing (e.g., automation tools running integration of new data/business logic to be implemented on a system). In an integration test, the process flow typically follows: (i) add, update, or remove data on control plane, (ii) replicate and integrate data on data plane, and (iii) validate that business logic is implemented correctly in data plane based on added, updated, or removed data.

Typically, when the data is added, updated, and removed on the control plane, there needs to be communication on the back plane between the control plane and the data plane in order to facilitate replication and integration of data from the control plane to the data plane. However, if requests and calls for services are made to the data plane based on the data present on the control plane or expected to be present on the data plane before the data has been replicated and integrated via the back plane to the data plane, then an error occurs because the data plane does not know of the data yet to use the data within the business logic being tested. This problem is common to integration testing where tests are waiting and retrying requests while the data plane is synchronizing with the control plane. When integration tests are run on multiple threads on the same machine, the CPU becomes very busy and may not get enough time to replicate and integrate the data to the data plane. This causes intermittent test failures (e.g., error—data not found).

Developers try to work around these test failures by increasing the number of testing retries and the time period between testing retries, causing the integration test runs to become longer and longer. For example, if the business logic fails because it cannot find the data such as an entity or policy requested then the integration test repeats the calls/requests up to a predetermined number of times (e.g., 7) until all of a sudden the data is replicated and makes its way over to the data plane from the control plane such that the integration testing proceeds or doesn't make its way over to the data plane by the predetermined number of times such that the integration testing fails. However, it is impossible for the client to know why the process failed at this point (e.g., was the fail simply data not replicated yet or was the fail because the data was replicated incorrectly or not at all) because the error code for data not found is nondeterministic (no discovery). This lack of discovery is by design to prevent an intruder such as a hacker from discovering entities, group of entities or business logic in place for various services. Although, this type of problem has been discussed in terms of replication and integration between the control plane and data plane, it should be understood that this type of problem could occur in other contexts and outside the realm of integration testing. For example, this type of problem can also be seen with replication and integration in different regions e.g., geographic regions—Phoenix versus Sacramento) of a control plane that are communicating with one another.

To overcome these challenges and others, various embodiments are directed to having the create/update/delete APIs in the control plane return a custom response header (for example opc-replication-id), which can be used to for making eventual consistency cache updates deterministic. Specifically, when creating any new data or modifying the data, the control plane, data plane, and replication service use identifiers (e.g., identifier numbers that sequential increase for each replication event) associated with the data to track and continuously identify the data. Aspects of the present disclosure leverage these identifiers by communicating them back to the client in custom response headers such that the client can include the identifiers within conditional headers (opc-replication-id) in subsequent requests to the control plane and data plane. If a request (e.g., an integration test request) includes this conditional header, the control plane or data plane would return a response to the request (the response could be the result of processing the request or any other error code not associated with a delay in replication) so long as replication has caught up to the replication value in the conditional header (determined by a comparison of the identifier in the conditional header to a identifier(s) associated with current data replication). Otherwise, the control plane or data plane would return a deterministic error code (e.g., an HTTP response code 412 Pre-condition failed). The deterministic error code would indicate to the client that the data plane host the client is sending a request to is not up-to-date yet and to retry the request at a later time, e.g., a few seconds/minutes (potentially using exponential back-off).

For example, if a client creates a user in a database, the creation or replication service generates and assigns an identifier to the user entity created as part of the creation/replication process, the identifier is then reported back in a http response header to the client as part of the response to the request for creating the user, and for next request the client can pass the header as a conditional request header in any subsequent request (e.g., a request to the data plane to test the business logic on the new user would include the conditional header with the identifier). The data plane receives the subsequent request having the conditional header with the sequence number, looks at the sequence number in the conditional header, and performs the business logic process if it has the replicated data for the user, but if it does not have the data yet (the data plane has not caught up to the control plane and there is a delay in data replication) then the data plane provides a different deterministic error code instead of a non-discoverable error code. In some instances, the deterministic error code does not disclose whether the resource exists just that the data plane cannot find the resource to process the request. Nonetheless, in such an instance, the error code is at least deterministic of the data plane not being caught up with replication of data, and not an error for some other reason (e.g., a failure in the business logic).

In various embodiments, a technique implemented by a computing system for making eventual consistency cache updates deterministic includes: receiving, at a control plane, a request to execute an operation on data, executing the operation on the data, creating a replication event for the operation and a replication identifier associated with the replication event, sending a response that includes a custom header having the replication identifier, receiving, at a data plane, a subsequent request to execute an operation involving the data, the subsequent request includes the replication identifier, retrieving a replication identifier for a latest replication event executed on the data plane, comparing the replication identifier from the subsequent request and the replication identifier for the latest replication event, determining the replication event associated with the replication identifier from the subsequent request has not been executed on the data plane based on the comparison, and sending a deterministic error message to a client device.

Computing System for Making Eventual Consistency Cache Updates Deterministic

FIG. 1is a block diagram illustrating a computing environment100for making eventual consistency cache updates deterministic in accordance with various embodiments. As shown inFIG. 1, the computing environment100includes a client105, a control plane110, an integration and replication system115, a data plane120, and a storage device125. The client105, control plane110, integration and replication system115, data plane120, and storage device125comprise one or more computing systems that execute computer-readable instructions (e.g., code, program) to implement functionality of each of the client105, control plane110, integration and replication environment115, data plane120, and storage device125. In some embodiments, the control plane110, the integration and replication system115, the data plane120, and the storage device125are part of a computing system130such as an identity management system.

The computing environment100depicted inFIG. 1is merely an example and is not intended to unduly limit the scope of claimed embodiments. One of ordinary skill in the art would recognize many possible variations, alternatives, and modifications. For example, in some implementations, the computing environment100can be implemented using more or fewer systems than those shown inFIG. 1, may combine two or more systems, or may have a different configuration or arrangement of systems and subsystems. For example, although the exemplary computing environment100is shown with a single client device105, any number of client devices105may be supported by the computing environment100. Moreover, the computing environment100may be implemented in various different configurations. In some embodiments, the computing environment100is implemented in an enterprise servicing users of the enterprise. In other embodiments, the computing environment100is implemented on one or more servers of a cloud provider and the network policy creation services of the systems may be provided to subscribers of cloud services on a subscription basis.

The computing environment100may be computerized such that each of the illustrated components is configured to communicate with other components via a back plane125. In instances in which components reside on a same computing device the communication on the back plane125may be via an internal communication system such as various types of buses. In instances in which components reside on different computing devices such as different servers the communication on the back plane125may be via a network. The network may be any type of network familiar to those skilled in the art that can support data communications using any of a variety of commercially-available protocols, including without limitation TCP/IP, SNA, IPX, AppleTalk, and the like. Merely by way of example, network can be a local area network (LAN) such as an Ethernet network, a Token-Ring network and/or the like, a wide-area network (WAN), a virtual network, including without limitation a virtual private network (VPN), the Internet, an intranet, an extranet, a public switched telephone network (PSTN), an infra-red network, a wireless network (e.g., a network operating under any of the IEEE 802.1X suite of protocols, the Bluetooth protocol known in the art, and/or any other wireless protocol), and/or any combination of these and/or other networks. Any other combination of networks, including secured and unsecured network communications are contemplated for use in the systems described herein.

In various embodiments, a user may interact with the control plane110using a client device105that is communicatively coupled to the control plane110, possibly via one or more communication networks. The client device105may be of various types, including but not limited to, a mobile phone, a tablet, a desktop computer, and the like. The user may represent a user of an enterprise who subscribes to the services provided by the systems of the computing environment100for automatically generating data (e.g., entities or network policies) for components of an application135to be or presently deployed in a computing environment. The user may interact with the computing system130using an application such as a browser executed by the client device105. For example, the user may use a user interface (UI) (which may be a graphical user interface (GUI)) of an application executed with a programming language such as Python by the client device105to interact with the control plane110.

The control plane110receives (via the UI) the interaction such as a request to create, read, update, and/or delete data to be or presently integrated as part of the application135to be or presently deployed in the computing environment100. For instance, a user of an enterprise may wish to add a new entity, group of entities or network policy to an authentication and authorization application to be or presently deployed on an identity management platform. In this case, the client device105may provide a request to create, read, update, and/or delete data by the control plane110. The control plane110receives the request and initiates a process to execute the create, read, update, and/or delete data function. This process includes the integration and replication system115creating a replication event for the create, read, update, and/or delete data function and assigning a replication identifier to the replication event. The replication event will allow for the create, read, update, and/or delete data function to be replicated on the data plane120. In some instances, the replication identifier and associated replication event are stored in the storage device125(e.g., in a data table) for subsequent retrieval. The application programming interfaces (APIs)140in the control plane110(e.g., the create/update/delete APIs) return a custom response header (for example opc-replication-id) comprising the replication identifier to the client device105. In some instances, the control plane APIs140implement this using a request filter (e.g., an HTTP request filter) that injects the current value of the last replication event identifier (e.g., LASTSEQUENCENUMBER) from the storage device125(e.g., REPLICATION_METADATA table) into the custom header sent back with the response to the client device110, thereby avoiding the need for any changes to the action handlers themselves. The client device110receives the response with the customer response header (for example opc-replication-id) from the control plane110and maintains the replication identifier (e.g., stores the replication identifier locally on the client device105) for subsequent communication with the control plane110and data plane120.

The integration and replication system115creates the replication event for the create, read, update, and/or delete data function and initiates communication with the data plane120via APIs145(e.g., data plane APIs) and the back plane to execute the replication event on the data plane120. The control plane110may receive (via the UI) a subsequent interaction such as a request to execute business logic integrated as part of the application135to be or presently deployed in the computing environment100. For instance, a user of an enterprise may wish to test or use business logic such as a second factor authentication protocol that is part of an authentication and authorization application135to be or presently deployed on an identity management platform. The application on the client device105, which enables the client device105to interact with the control plane110, is configured to propagate the replication identifier maintained on the client device110to a custom request header (for example opc-replication-id) for the subsequent request interaction. The control plane110receives the request, determines whether to authorize the request, and in response to authorization of the request, forwards the request to the data plane120.

The data plane120uses a separate request filter (e.g., an HTTP request filter) to short-circuit the request from the client device105if the custom request header (for example opc-replication-id) is detected in the request and the replication event has not been executed on the data plane120(i.e., the state of the data plane has not caught up to the control plane). In other words, the separate request filter on the data plane120is configured to determine whether the request includes the custom request header, and if the request includes the custom request header, the data plane120will return an answer (e.g., the result of executing the business logic or an error not related to delay of executing the replication event on the data plane120) to the client device105only if the replication event has been executed on the data plane120. Otherwise, the data plane120will return a response error message (e.g., an http error code: 412 Pre-condition failed) indicative or deterministic that the replication event has not been executed on the data plane120. As used herein, the term “indicative” means the error message can specifically serve as a signal that the replication event has not been executed on the data plane. As used herein, the term “deterministic” means that given a particular input (i.e., the replication event has not been executed on the data plane), the algorithm will always produce the same output of an error message. This technique has the potential to significantly speed up integration testing (only wait when replication is behind) and make integration testing more reliable (no more test failures because the replication was behind).

Techniques for Making Eventual Consistency Cache Updates Deterministic

The processes and/or operations depicted inFIGS. 2 and 3may be implemented in software (e.g., code, instructions, program) executed by one or more processing units (e.g., processors cores), hardware, or combinations thereof. The software may be stored in a memory (e.g., on a memory device, on a non-transitory computer-readable storage medium). The particular series of processing steps inFIGS. 2 and 3is not intended to be limiting. Other sequences of steps may also be performed according to alternative embodiments. For example, in alternative embodiments the steps outlined above may be performed in a different order. Moreover, the individual steps illustrated inFIGS. 2 and 3may include multiple sub-steps that may be performed in various sequences as appropriate to the individual step. Furthermore, additional steps may be added or removed depending on the particular applications. One of ordinary skill in the art would recognize many variations, modifications, and alternatives.

FIG. 2shows a swim lane diagram illustrating a data plane replication process200with custom headers in accordance with various embodiments. The processes depicted in the swim lane diagram may be implemented by the architecture, systems, and techniques depicted inFIGS. 1 and 4-8. At step205, a control plane of a computing system receives a request to execute an operation on data. The request is received from a client device via one or more control plane APIs (e.g., create/update/delete APIs). The data may to be or presently integrated as part of an application to be or presently deployed on the computing system. In some instances, the request is to create, read, update, and/or delete data to be or presently integrated as part of the application to be or presently deployed on the computing system. Examples of the data to be implemented for an authentication or authorization application may include a new user, a prior user, credentials of a user, a new policy, a prior policy, rules of a policy, and the like. At step210, the control plane initiates a process to execute the operation on the data. The process includes the control plane performing the operation on the data, for example, creating, updating, or deleting the data on the control plane, and forwarding the request to the integration and replication system.

At step215, the integration and replication system receives the request and creates a replication event for the operation and assigns a replication identifier to the replication event. The replication event will be used to replicate execution of the operation on a data plane. In some instances, the replication identifier, the associated replication event, or a combination thereof is stored in a storage device (e.g., in a data table) for subsequent retrieval. The replication identifier only has meaning on the control and data plane services, and is opaque to the callers or users of the computing system. The replication identifier can therefore be encrypted using a key shared between services and regions to prevent callers or users from inferring any usage statistics from the numbers themselves. At step220, the integration and replication system returns the replication identifier to the control plane.

In some instances, the process to execute the operation on the control plane further includes creating resources that schedule background tasks to run and produce resources that require replication. Policies are an example of this type of resource. When a new policy is created, a policy compiler task is scheduled. When the policy compiler background task processes the policy, the policy compiler background task replicates the policy graph for the tenancy to the data plane via an ‘UPDATE POLICY GRAPH’ replication event. Thus, any action that relies on this policy being in effect needs to wait till the replication event produced by the policy compiler is processed by the data plane, not the ‘CREATE POLICY’ event created by createPolicy handler. In order to handle such an instance, a substitute replication identifier may be returned to the control plane at step220(as opposed to the actual replication identifier) when a new background task is created. In some instances, the substitute replication identifier associated with the new background task comprises a predefined format such as alphanumeric (e.g., TRX_<trxid>). A table may be created by the integration and replication system to map the substitute replication identifier with the actual replication identifier such as a REPLICATION_MAPPING, which has a TRX_ID column and a REPLICATION_ID column.

When the new background task is scheduled (e.g., the policy compilation is scheduled), the substitute replication identifier is added as an entry within a row of the TRX_ID column and the corresponding row of REPLICATION_ID column is left empty. When the background task is completed (e.g., the background task policy compiler has compiled the policies and written the replication log), the integration and replication system updates the row of REPLICATION_ID column with the actual replication identifier.

In some instances, the mapping table (e.g., REPLICATION_MAPPING) can additionally or alternatively be used to make cross-region replication deterministic. Cross-region as used herein means across geographic regions, across tenants, and/or across computing systems, e.g., between a home region and a subscribe region. Typically in cross-region replication a backfill processor reads request records from the inbox table in the replication database. A data column in a data table stores the data coming from the home region including an actual replication identifier generated for the replication event. The account service knows the home region for each tenant. When the backfill processor processes the request record from the inbox table, the backfill processor can write a mapping to the data table (e.g., REPLICATION_MAPPING) for the substitute replication identifier in a predefined format such as alphanumeric-REG-nnnnnn (e.g., IAD-123456) associated with the actual replication identifier generated for the replication event.

At step225, the one or more control plane APIs return a custom response header (for example opc-replication-id) comprising the replication identifier (actual or substitute replication identifier) to the client device that initiated the request. In some instances, the control plane APIs implement this using a request filter (e.g., an HTTP request filter) that injects the current value of the last replication event identifier (actual or substitute replication identifier) from the storage device (e.g., REPLICATION_METADATA table or the REPLICATION_MAPPING table) into the custom header sent back with the response to the client device, thereby avoiding the need for any changes to the action handlers themselves.

At step230, the client device receives the response with the customer response header (for example opc-replication-id) from the control plane and maintains the replication identifier for subsequent communication with the control plane and data plane services. Maintaining the replication identifier may include storing the replication identifier locally on the client device.

At step235, the control plane or the data plane of the computing system receives a subsequent request to execute an operation involving the data on the computing system. The subsequent request is received from the client device via one or more control plane or data plane APIs (e.g., execute APIs). An example of a subsequent request is an integration test to be run using the data on the computing system that was operated on in step210. Another example of a subsequent request is a user request to be run using the data on the computing system that was operated on in step210. In some instances, the subsequent operation is logic (e.g., business logic) to be executed using the data to be or presently integrated as part of the application to be or presently deployed on the computing system. An application on the client device, which enables the client device to interact with the control plane and data plane services, is configured to propagate the replication identifier maintained on the client device to a custom request header (for example opc-replication-id) for the subsequent request. The replication identifier may be propagated by the application maintaining an association between the replication identifier and the prior request, operation, and/or data received in step205.

At optional step240(in the instance the request is received at the control plane), the control plane forwards the subsequent request to the data plane for processing. In some embodiments, the control plane determines whether to authorize the subsequent request, and in response to authorization of the subsequent request, forwards the subsequent request to the data plane for processing. In some instances, the determination to authorize the subsequent request is based on credentials of a user to provide the given subsequent request, e.g., the user is authorized to request the execution of the business logic. In other instances, the determination to authorize the subsequent request is based on whether the custom request header or the replication identifier is included with the subsequent request. For example, if a replication id filter of the control plane detects a custom request header or the replication identifier within the subsequent request, the replication id filter forwards the subsequent request to the data plane. In contrast, if the replication id filter of the control plane does not detect a custom request header or the replication identifier within the subsequent request, the replication id filter returns an error message (an error not related to delay of executing the replication event on the data plane) to the client device. In some embodiments, the error message is indicative or deterministic of failure to provide a custom request header or the replication identifier with the subsequent request.

In yet other instances, the determination to authorize the subsequent request is based on whether a mapping table includes a replication identifier. For example, in the instances where background tasks are scheduled, if a replication id filter of the control plane detects a predefined format for a substitute replication identifier such as an alphanumeric format, the replication id filter checks the mapping table for an actual replication identifier using the substitute replication identifier as a key. If there is no actual replication identifier yet (e.g., policies are not compiled yet), the replication id filter returns an error message to the client device such as 412 pre-condition failed. In some embodiments, the error message is indicative or deterministic of an incomplete background task and/or an absence of a replication identifier for the replication event. In contrast, if there is an actual replication identifier (e.g., policies are compiled), the replication id filter inserts the actual replication identifier in the customer header as the replication identifier (for example opc-replication-id) and the replication id filter forwards the subsequent request to the data plane.

Moreover, in the instances where cross-region replication is implemented, if a subsequent request comes from a home region to a replication id filter in a subscribed region and the replication id filter detects a predefined format for a substitute replication identifier such as an alphanumeric format, the replication id filter checks the mapping table for an actual replication identifier using the substitute replication identifier as a key. If there is no actual replication identifier yet (e.g., the home region has not yet contacted the subscriber region), the replication id filter returns an error message to the client device such as 412 pre-condition failed. In some embodiments, the error message is indicative or deterministic of the backfill processor not yet processing the request record from the inbox table and/or an absence of a replication identifier for the replication event. In contrast, if there is an actual replication identifier (e.g., the home region has contacted the subscriber region), the replication id filter inserts the actual replication identifier in the customer header as the replication identifier (for example opc-replication-id) and the replication id filter forwards the subsequent request to the data plane. As should be understood, the authorization determination could be made using any one of the aforementioned techniques, or any combination thereof.

At step245, the data plane of the computing system receives the subsequent request either from the client device directly (as discussed with respect to step235) or via the control plane (as discussed with respect to step240). At step250, a separate replication id filter of the data plane sends a call to a data storage device (e.g., a database or data table) to retrieve a replication identifier for the latest replication event executed on the data plane. At step255, the replication identifier for the latest replication event is retrieved from the data storage device and forwarded back to the replication id filter of the data plane.

At step260, the replication id filter of the data plane compares the replication identifier for the latest replication event retrieved in step255with the replication identifier from the custom request header of the subsequent request received in step245. The replication id filter of the data plane determines, based on the comparison, whether the replication event associated with the replication identifier from the custom request header of the subsequent request has been executed on the data plane. As used herein, when an action is “based on” something, this means the action is based at least in part on at least a part of the something. This determination may be made in a number of ways depending upon the type of replication identifiers being issued. Fundamentally, the replication id filter of the data plane is determining whether the replication identifier from the custom request header of the subsequent request issued prior to, at the same time (the replication identifier is the same), or after issuance of the replication identifier for the latest replication event. For example, if the replication identifiers are issued sequentially then the replication id filter determines whether the replication identifier for the latest replication event is greater than, equal to, or less than the replication identifier from the custom request header of the subsequent request. If the replication identifier from the custom request header of the subsequent request did issue prior to issuance of the replication identifier for the latest replication event or at the same time (the replication identifier is the same), then it is determinable that the replication event associated with the replication identifier from the custom request header of the subsequent request has been executed on the data plane. If the replication identifier from the custom request header of the subsequent request did not issue prior to issuance of the replication identifier for the latest replication event or at the same time (the replication identifier is the same), then it is determinable that the replication event associated with the replication identifier from the custom request header of the subsequent request has not been executed on the data plane.

In response to the replication event associated with the replication identifier from the custom request header not being executed on the data plane, at step265the replication id filter of the data plane returns an error message to the control plane such as 412 pre-condition failed. The error message is indicative or deterministic that the replication event has not been executed on the data plane, and thus failure to execute the subsequent request is due to a delay in executing a replication event for a resource utilized with the subsequent request. At step270, the replication id filter of the control plane returns the error message to the client device. Alternatively, in response to the replication event associated with the replication identifier from the custom request header being executed on the data plane, at step275the replication id filter of the data plane returns an answer to the control plane. At step280, the replication id filter of the control plane returns the answer to the client device. The answer can be the result of executing the request on the data plane such as the result generated from executing the business logic on the data plane or the answer can be any error other than an error related to a delay in executing the replication event on the data plane such as a business logic failure to execute error.

FIG. 3shows a flowchart300that illustrates a process for determining whether a replication event associated with the first replication identifier from a custom header has been executed on a data plane based on a comparison between a first replication identifier and a second replication identifier for a latest replication event executed on the data plane. In some embodiments, the processes depicted in flowchart300may be implemented by the architecture, systems, and techniques depicted inFIGS. 1 and 4-8. At step305, a first request is received at a control plane of a computing system from a client device. The first request is to execute a first operation on data. In some embodiments, the first request is to create, read, update, and/or delete the data, which is to be or presently integrated as part of an application to be or presently deployed on the computing system.

At step310, the first operation is executed by the computing system on the data. At step315, a replication event for the operation and a first replication identifier associated with the replication event are created by the computing system. The replication event will be used to replicate execution of the first operation on a data plane. At step320, a response is sent by the computing system back to the client device concerning the execution of the first operation on the data. The response comprises a custom header having the first replication identifier.

In some embodiments, the executing the first operation comprises: (i) creating a resource that schedules a background task to run and produce another resource that requires replication, and (ii) in response to scheduling the background task, writing a substitute replication identifier associated with the background task and the first operation to a data table. In this instance, the response comprises the custom header having the substitute replication identifier rather than the first replication identifier. The executing of the first operation may further comprise: (iii) executing the background task to run and produce another resource that requires replication, and (iv) in response to completing execution of the background task, writing the first replication identifier associated with the first operation to the data table.

In other embodiments, the control plane is located within a home region of the computing system and the first request is written to an inbox table in a replication database located within a subscriber region of the computing system. The first replication identifier associated with the first operation is written to a data table. The executing the first operation comprises: (i) executing, by a backfill processor within the subscriber region, the first operation of the first request from the inbox table in the replication database, and (ii) in response to executing the first operation within the subscriber region, writing a substitute replication identifier associated with first operation to the data table. In this instance, the response comprises the custom header having the substitute replication identifier rather than the first replication identifier.

At step325, a second request is received by the data plane of the computing system to execute a second operation involving the data. The second request is received from the client device and includes the custom header having the first replication identifier. In some embodiments, the second request includes the custom header having the substitute replication identifier; and in response to receiving the substitute replication identifier, the first replication identifier is identified from the data table using the substitute replication identifier as a key.

At step330, in response to receiving the second request, a second replication identifier is retrieved by the computing system for a latest replication event executed on the data plane. At step335, the first replication identifier and the second replication identifier are compared by the computing system. At step340, a determination is made by the computing system as to whether the replication event associated with the first replication identifier from the custom header has been executed on the data plane based on the comparison between the first replication identifier and the second replication identifier. The determining whether the replication event associated with the first replication identifier from the custom header has been executed on the data plane comprises determining whether the first replication identifier from the custom header of the second request issued prior to, at the same time, or after issuance of the second replication identifier for the latest replication event.

At step345, in response to determining the replication event has not been executed on the data plane, an error message is sent by the computing system to the client device. The error message is indicative or deterministic that the replication event has not been executed on the data plane. At step350, in response to determining the replication event has been executed on the data plane, an answer is sent by the computing system to the client device. The answer can be the result of executing the request on the data plane such as the result generated from executing the second operation on the data plane or the answer can be any error other than an error related to a delay in executing the replication event on the data plane such as a business logic failure to execute error.

Illustrative Systems

The VCN406can include a local peering gateway (LPG)410that can be communicatively coupled to a secure shell (SSH) VCN412via an LPG410contained in the SSH VCN412. The SSH VCN412can include an SSH subnet414, and the SSH VCN412can be communicatively coupled to a control plane VCN416via the LPG410contained in the control plane VCN416. Also, the SSH VCN412can be communicatively coupled to a data plane VCN418via an LPG410. The control plane VCN416and the data plane VCN418can be contained in a service tenancy419that can be owned and/or operated by the IaaS provider.

The control plane VCN416can include a control plane demilitarized zone (DMZ) tier420that acts as a perimeter network (e.g., portions of a corporate network between the corporate intranet and external networks). The DMZ-based servers may have restricted responsibilities and help keep breaches contained. Additionally, the DMZ tier420can include one or more load balancer (LB) subnet(s)422, a control plane app tier424that can include app subnet(s)426, a control plane data tier428that can include database (DB) subnet(s)430(e.g., frontend DB subnet(s) and/or backend DB subnet(s)). The LB subnet(s)422contained in the control plane DMZ tier420can be communicatively coupled to the app subnet(s)426contained in the control plane app tier424and an Internet gateway434that can be contained in the control plane VCN416, and the app subnet(s)426can be communicatively coupled to the DB subnet(s)430contained in the control plane data tier428and a service gateway436and a network address translation (NAT) gateway438. The control plane VCN416can include the service gateway436and the NAT gateway438.

The control plane VCN416can include a data plane mirror app tier440that can include app subnet(s)426. The app subnet(s)426contained in the data plane mirror app tier440can include a virtual network interface controller (VNIC)442that can execute a compute instance444. The compute instance444can communicatively couple the app subnet(s)426of the data plane mirror app tier440to app subnet(s)426that can be contained in a data plane app tier446.

The data plane VCN418can include the data plane app tier446, a data plane DMZ tier448, and a data plane data tier450. The data plane DMZ tier448can include LB subnet(s)422that can be communicatively coupled to the app subnet(s)426of the data plane app tier446and the Internet gateway434of the data plane VCN418. The app subnet(s)426can be communicatively coupled to the service gateway436of the data plane VCN418and the NAT gateway438of the data plane VCN418. The data plane data tier450can also include the DB subnet(s)430that can be communicatively coupled to the app subnet(s)426of the data plane app tier446.

The Internet gateway434of the control plane VCN416and of the data plane VCN418can be communicatively coupled to a metadata management service452that can be communicatively coupled to public Internet454. Public Internet454can be communicatively coupled to the NAT gateway438of the control plane VCN416and of the data plane VCN418. The service gateway436of the control plane VCN416and of the data plane VCN418can be communicatively couple to cloud services456.

In some examples, the service gateway436of the control plane VCN416or of the data plane VCN418can make application programming interface (API) calls to cloud services456without going through public Internet454. The API calls to cloud services456from the service gateway436can be one-way: the service gateway436can make API calls to cloud services456, and cloud services456can send requested data to the service gateway436. But, cloud services456may not initiate API calls to the service gateway436.

In some examples, the secure host tenancy404can be directly connected to the service tenancy419, which may be otherwise isolated. The secure host subnet408can communicate with the SSH subnet414through an LPG410that may enable two-way communication over an otherwise isolated system. Connecting the secure host subnet408to the SSH subnet414may give the secure host subnet408access to other entities within the service tenancy419.

The control plane VCN416may allow users of the service tenancy419to set up or otherwise provision desired resources. Desired resources provisioned in the control plane VCN416may be deployed or otherwise used in the data plane VCN418. In some examples, the control plane VCN416can be isolated from the data plane VCN418, and the data plane mirror app tier440of the control plane VCN416can communicate with the data plane app tier446of the data plane VCN418via VNICs442that can be contained in the data plane mirror app tier440and the data plane app tier446.

In some examples, users of the system, or customers, can make requests, for example create, read, update, or delete (CRUD) operations, through public Internet454that can communicate the requests to the metadata management service452. The metadata management service452can communicate the request to the control plane VCN416through the Internet gateway434. The request can be received by the LB subnet(s)422contained in the control plane DMZ tier420. The LB subnet(s)422may determine that the request is valid, and in response to this determination, the LB subnet(s)422can transmit the request to app subnet(s)426contained in the control plane app tier424. If the request is validated and requires a call to public Internet454, the call to public Internet454may be transmitted to the NAT gateway438that can make the call to public Internet454. Memory that may be desired to be stored by the request can be stored in the DB subnet(s)430.

In some examples, the data plane mirror app tier440can facilitate direct communication between the control plane VCN416and the data plane VCN418. For example, changes, updates, or other suitable modifications to configuration may be desired to be applied to the resources contained in the data plane VCN418. Via a VNIC442, the control plane VCN416can directly communicate with, and can thereby execute the changes, updates, or other suitable modifications to configuration to, resources contained in the data plane VCN418.

In some embodiments, the control plane VCN416and the data plane VCN418can be contained in the service tenancy419. In this case, the user, or the customer, of the system may not own or operate either the control plane VCN416or the data plane VCN418. Instead, the IaaS provider may own or operate the control plane VCN416and the data plane VCN418, both of which may be contained in the service tenancy419. This embodiment can enable isolation of networks that may prevent users or customers from interacting with other users', or other customers', resources. Also, this embodiment may allow users or customers of the system to store databases privately without needing to rely on public Internet454, which may not have a desired level of threat prevention, for storage.

In other embodiments, the LB subnet(s)422contained in the control plane VCN416can be configured to receive a signal from the service gateway436. In this embodiment, the control plane VCN416and the data plane VCN418may be configured to be called by a customer of the IaaS provider without calling public Internet454. Customers of the IaaS provider may desire this embodiment since database(s) that the customers use may be controlled by the IaaS provider and may be stored on the service tenancy419, which may be isolated from public Internet454.

FIG. 5is a block diagram500illustrating another example pattern of an IaaS architecture, according to at least one embodiment. Service operators502(e.g. service operators402ofFIG. 4) can be communicatively coupled to a secure host tenancy504(e.g. the secure host tenancy404ofFIG. 4) that can include a virtual cloud network (VCN)506(e.g. the VCN406ofFIG. 4) and a secure host subnet508(e.g. the secure host subnet408ofFIG. 4). The VCN506can include a local peering gateway (LPG)510(e.g. the LPG410ofFIG. 4) that can be communicatively coupled to a secure shell (SSH) VCN512(e.g. the SSH VCN412ofFIG. 4) via an LPG410contained in the SSH VCN512. The SSH VCN512can include an SSH subnet514(e.g. the SSH subnet414ofFIG. 4), and the SSH VCN512can be communicatively coupled to a control plane VCN516(e.g. the control plane VCN416ofFIG. 4) via an LPG510contained in the control plane VCN516. The control plane VCN516can be contained in a service tenancy519(e.g. the service tenancy419ofFIG. 4), and the data plane VCN518(e.g. the data plane VCN418ofFIG. 4) can be contained in a customer tenancy521that may be owned or operated by users, or customers, of the system.

The control plane VCN516can include a control plane DMZ tier520(e.g. the control plane DMZ tier420ofFIG. 4) that can include LB subnet(s)522(e.g. LB subnet(s)422ofFIG. 4), a control plane app tier524(e.g. the control plane app tier424ofFIG. 4) that can include app subnet(s)526(e.g. app subnet(s)426ofFIG. 4), a control plane data tier528(e.g. the control plane data tier428ofFIG. 4) that can include database (DB) subnet(s)530(e.g. similar to DB subnet(s)430ofFIG. 4). The LB subnet(s)522contained in the control plane DMZ tier520can be communicatively coupled to the app subnet(s)526contained in the control plane app tier524and an Internet gateway534(e.g. the Internet gateway434ofFIG. 4) that can be contained in the control plane VCN516, and the app subnet(s)526can be communicatively coupled to the DB subnet(s)530contained in the control plane data tier528and a service gateway536(e.g. the service gateway ofFIG. 4) and a network address translation (NAT) gateway538(e.g. the NAT gateway438ofFIG. 4). The control plane VCN516can include the service gateway536and the NAT gateway538.

The control plane VCN516can include a data plane mirror app tier540(e.g. the data plane mirror app tier440ofFIG. 4) that can include app subnet(s)526. The app subnet(s)526contained in the data plane mirror app tier540can include a virtual network interface controller (VNIC)542(e.g. the VNIC of442) that can execute a compute instance544(e.g. similar to the compute instance444ofFIG. 4). The compute instance544can facilitate communication between the app subnet(s)526of the data plane mirror app tier540and the app subnet(s)526that can be contained in a data plane app tier546(e.g. the data plane app tier446ofFIG. 4) via the VNIC542contained in the data plane mirror app tier540and the VNIC542contained in the data plane app tier546.

The Internet gateway534contained in the control plane VCN516can be communicatively coupled to a metadata management service552(e.g. the metadata management service452ofFIG. 4) that can be communicatively coupled to public Internet554(e.g. public Internet454ofFIG. 4). Public Internet554can be communicatively coupled to the NAT gateway538contained in the control plane VCN516. The service gateway536contained in the control plane VCN516can be communicatively couple to cloud services556(e.g. cloud services456ofFIG. 4).

In some examples, the data plane VCN518can be contained in the customer tenancy521. In this case, the IaaS provider may provide the control plane VCN516for each customer, and the IaaS provider may, for each customer, set up a unique compute instance544that is contained in the service tenancy519. Each compute instance544may allow communication between the control plane VCN516, contained in the service tenancy519, and the data plane VCN518that is contained in the customer tenancy521. The compute instance544may allow resources, that are provisioned in the control plane VCN516that is contained in the service tenancy519, to be deployed or otherwise used in the data plane VCN518that is contained in the customer tenancy521.

In other examples, the customer of the IaaS provider may have databases that live in the customer tenancy521. In this example, the control plane VCN516can include the data plane mirror app tier540that can include app subnet(s)526. The data plane mirror app tier540can reside in the data plane VCN518, but the data plane mirror app tier540may not live in the data plane VCN518. That is, the data plane mirror app tier540may have access to the customer tenancy521, but the data plane mirror app tier540may not exist in the data plane VCN518or be owned or operated by the customer of the IaaS provider. The data plane mirror app tier540may be configured to make calls to the data plane VCN518but may not be configured to make calls to any entity contained in the control plane VCN516. The customer may desire to deploy or otherwise use resources in the data plane VCN518that are provisioned in the control plane VCN516, and the data plane mirror app tier540can facilitate the desired deployment, or other usage of resources, of the customer.

In some embodiments, the customer of the IaaS provider can apply filters to the data plane VCN518. In this embodiment, the customer can determine what the data plane VCN518can access, and the customer may restrict access to public Internet554from the data plane VCN518. The IaaS provider may not be able to apply filters or otherwise control access of the data plane VCN518to any outside networks or databases. Applying filters and controls by the customer onto the data plane VCN518, contained in the customer tenancy521, can help isolate the data plane VCN518from other customers and from public Internet554.

In some embodiments, cloud services556can be called by the service gateway536to access services that may not exist on public Internet554, on the control plane VCN516, or on the data plane VCN518. The connection between cloud services556and the control plane VCN516or the data plane VCN518may not be live or continuous. Cloud services556may exist on a different network owned or operated by the IaaS provider. Cloud services556may be configured to receive calls from the service gateway536and may be configured to not receive calls from public Internet554. Some cloud services556may be isolated from other cloud services556, and the control plane VCN516may be isolated from cloud services556that may not be in the same region as the control plane VCN516. For example, the control plane VCN516may be located in “Region 1,” and cloud service “Deployment 4,” may be located in Region 1 and in “Region 2.” If a call to Deployment 4 is made by the service gateway536contained in the control plane VCN516located in Region 1, the call may be transmitted to Deployment 4 in Region 1. In this example, the control plane VCN516, or Deployment 4 in Region 1, may not be communicatively coupled to, or otherwise in communication with, Deployment 4 in Region 2.

FIG. 6is a block diagram600illustrating another example pattern of an IaaS architecture, according to at least one embodiment. Service operators602(e.g. service operators402ofFIG. 4) can be communicatively coupled to a secure host tenancy604(e.g. the secure host tenancy404ofFIG. 4) that can include a virtual cloud network (VCN)606(e.g. the VCN406ofFIG. 4) and a secure host subnet608(e.g. the secure host subnet408ofFIG. 4). The VCN606can include an LPG610(e.g. the LPG410ofFIG. 4) that can be communicatively coupled to an SSH VCN612(e.g. the SSH VCN412ofFIG. 4) via an LPG610contained in the SSH VCN612. The SSH VCN612can include an SSH subnet614(e.g. the SSH subnet414ofFIG. 4), and the SSH VCN612can be communicatively coupled to a control plane VCN616(e.g. the control plane VCN416ofFIG. 4) via an LPG610contained in the control plane VCN616and to a data plane VCN618(e.g. the data plane418ofFIG. 4) via an LPG610contained in the data plane VCN618. The control plane VCN616and the data plane VCN618can be contained in a service tenancy619(e.g. the service tenancy419ofFIG. 4).

The control plane VCN616can include a control plane DMZ tier620(e.g. the control plane DMZ tier420ofFIG. 4) that can include load balancer (LB) subnet(s)622(e.g. LB subnet(s)422ofFIG. 4), a control plane app tier624(e.g. the control plane app tier424ofFIG. 4) that can include app subnet(s)626(e.g. similar to app subnet(s)426ofFIG. 4), a control plane data tier628(e.g. the control plane data tier428ofFIG. 4) that can include DB subnet(s)630. The LB subnet(s)622contained in the control plane DMZ tier620can be communicatively coupled to the app subnet(s)626contained in the control plane app tier624and to an Internet gateway634(e.g. the Internet gateway434ofFIG. 4) that can be contained in the control plane VCN616, and the app subnet(s)626can be communicatively coupled to the DB subnet(s)630contained in the control plane data tier628and to a service gateway636(e.g. the service gateway ofFIG. 4) and a network address translation (NAT) gateway638(e.g. the NAT gateway438ofFIG. 4). The control plane VCN616can include the service gateway636and the NAT gateway638.

The data plane VCN618can include a data plane app tier646(e.g. the data plane app tier446ofFIG. 4), a data plane DMZ tier648(e.g. the data plane DMZ tier448ofFIG. 4), and a data plane data tier650(e.g. the data plane data tier450ofFIG. 4). The data plane DMZ tier648can include LB subnet(s)622that can be communicatively coupled to trusted app subnet(s)660and untrusted app subnet(s)662of the data plane app tier646and the Internet gateway634contained in the data plane VCN618. The trusted app subnet(s)660can be communicatively coupled to the service gateway636contained in the data plane VCN618, the NAT gateway638contained in the data plane VCN618, and DB subnet(s)630contained in the data plane data tier650. The untrusted app subnet(s)662can be communicatively coupled to the service gateway636contained in the data plane VCN618and DB subnet(s)630contained in the data plane data tier650. The data plane data tier650can include DB subnet(s)630that can be communicatively coupled to the service gateway636contained in the data plane VCN618.

The untrusted app subnet(s)662can include one or more primary VNICs664(1)-(N) that can be communicatively coupled to tenant virtual machines (VMs)666(1)-(N). Each tenant VM666(1)-(N) can be communicatively coupled to a respective app subnet667(1)-(N) that can be contained in respective container egress VCNs668(1)-(N) that can be contained in respective customer tenancies670(1)-(N). Respective secondary VNICs672(1)-(N) can facilitate communication between the untrusted app subnet(s)662contained in the data plane VCN618and the app subnet contained in the container egress VCNs668(1)-(N). Each container egress VCNs668(1)-(N) can include a NAT gateway638that can be communicatively coupled to public Internet654(e.g. public Internet454ofFIG. 4).

The Internet gateway634contained in the control plane VCN616and contained in the data plane VCN618can be communicatively coupled to a metadata management service652(e.g. the metadata management system452ofFIG. 4) that can be communicatively coupled to public Internet654. Public Internet654can be communicatively coupled to the NAT gateway638contained in the control plane VCN616and contained in the data plane VCN618. The service gateway636contained in the control plane VCN616and contained in the data plane VCN618can be communicatively couple to cloud services656.

In some embodiments, the data plane VCN618can be integrated with customer tenancies670. This integration can be useful or desirable for customers of the IaaS provider in some cases such as a case that may desire support when executing code. The customer may provide code to run that may be destructive, may communicate with other customer resources, or may otherwise cause undesirable effects. In response to this, the IaaS provider may determine whether to run code given to the IaaS provider by the customer.

In some examples, the customer of the IaaS provider may grant temporary network access to the IaaS provider and request a function to be attached to the data plane tier app646. Code to run the function may be executed in the VMs666(1)-(N), and the code may not be configured to run anywhere else on the data plane VCN618. Each VM666(1)-(N) may be connected to one customer tenancy670. Respective containers671(1)-(N) contained in the VMs666(1)-(N) may be configured to run the code. In this case, there can be a dual isolation (e.g., the containers671(1)-(N) running code, where the containers671(1)-(N) may be contained in at least the VM666(1)-(N) that are contained in the untrusted app subnet(s)662), which may help prevent incorrect or otherwise undesirable code from damaging the network of the IaaS provider or from damaging a network of a different customer. The containers671(1)-(N) may be communicatively coupled to the customer tenancy670and may be configured to transmit or receive data from the customer tenancy670. The containers671(1)-(N) may not be configured to transmit or receive data from any other entity in the data plane VCN618. Upon completion of running the code, the IaaS provider may kill or otherwise dispose of the containers671(1)-(N).

In some embodiments, the trusted app subnet(s)660may run code that may be owned or operated by the IaaS provider. In this embodiment, the trusted app subnet(s)660may be communicatively coupled to the DB subnet(s)630and be configured to execute CRUD operations in the DB subnet(s)630. The untrusted app subnet(s)662may be communicatively coupled to the DB subnet(s)630, but in this embodiment, the untrusted app subnet(s) may be configured to execute read operations in the DB subnet(s)630. The containers671(1)-(N) that can be contained in the VM666(1)-(N) of each customer and that may run code from the customer may not be communicatively coupled with the DB subnet(s)630.

In other embodiments, the control plane VCN616and the data plane VCN618may not be directly communicatively coupled. In this embodiment, there may be no direct communication between the control plane VCN616and the data plane VCN618. However, communication can occur indirectly through at least one method. An LPG610may be established by the IaaS provider that can facilitate communication between the control plane VCN616and the data plane VCN618. In another example, the control plane VCN616or the data plane VCN618can make a call to cloud services656via the service gateway636. For example, a call to cloud services656from the control plane VCN616can include a request for a service that can communicate with the data plane VCN618.

FIG. 7is a block diagram700illustrating another example pattern of an IaaS architecture, according to at least one embodiment. Service operators702(e.g. service operators402ofFIG. 4) can be communicatively coupled to a secure host tenancy704(e.g. the secure host tenancy404ofFIG. 4) that can include a virtual cloud network (VCN)706(e.g. the VCN406ofFIG. 4) and a secure host subnet708(e.g. the secure host subnet408ofFIG. 4). The VCN706can include an LPG710(e.g. the LPG410ofFIG. 4) that can be communicatively coupled to an SSH VCN712(e.g. the SSH VCN412ofFIG. 4) via an LPG710contained in the SSH VCN712. The SSH VCN712can include an SSH subnet714(e.g. the SSH subnet414ofFIG. 4), and the SSH VCN712can be communicatively coupled to a control plane VCN716(e.g. the control plane VCN416ofFIG. 4) via an LPG710contained in the control plane VCN716and to a data plane VCN718(e.g. the data plane418ofFIG. 4) via an LPG710contained in the data plane VCN718. The control plane VCN716and the data plane VCN718can be contained in a service tenancy719(e.g. the service tenancy419ofFIG. 4).

The control plane VCN716can include a control plane DMZ tier720(e.g. the control plane DMZ tier420ofFIG. 4) that can include LB subnet(s)722(e.g. LB subnet(s)422ofFIG. 4), a control plane app tier724(e.g. the control plane app tier424ofFIG. 4) that can include app subnet(s)726(e.g. app subnet(s)426ofFIG. 4), a control plane data tier728(e.g. the control plane data tier428ofFIG. 4) that can include DB subnet(s)730(e.g. DB subnet(s)630ofFIG. 6). The LB subnet(s)722contained in the control plane DMZ tier720can be communicatively coupled to the app subnet(s)726contained in the control plane app tier724and to an Internet gateway734(e.g. the Internet gateway434ofFIG. 4) that can be contained in the control plane VCN716, and the app subnet(s)726can be communicatively coupled to the DB subnet(s)730contained in the control plane data tier728and to a service gateway736(e.g. the service gateway ofFIG. 4) and a network address translation (NAT) gateway738(e.g. the NAT gateway438ofFIG. 4). The control plane VCN716can include the service gateway736and the NAT gateway738.

The data plane VCN718can include a data plane app tier746(e.g. the data plane app tier446ofFIG. 4), a data plane DMZ tier748(e.g. the data plane DMZ tier448ofFIG. 4), and a data plane data tier750(e.g. the data plane data tier450ofFIG. 4). The data plane DMZ tier748can include LB subnet(s)722that can be communicatively coupled to trusted app subnet(s)760(e.g. trusted app subnet(s)660ofFIG. 6) and untrusted app subnet(s)762(e.g. untrusted app subnet(s)662ofFIG. 6) of the data plane app tier746and the Internet gateway734contained in the data plane VCN718. The trusted app subnet(s)760can be communicatively coupled to the service gateway736contained in the data plane VCN718, the NAT gateway738contained in the data plane VCN718, and DB subnet(s)730contained in the data plane data tier750. The untrusted app subnet(s)762can be communicatively coupled to the service gateway736contained in the data plane VCN718and DB subnet(s)730contained in the data plane data tier750. The data plane data tier750can include DB subnet(s)730that can be communicatively coupled to the service gateway736contained in the data plane VCN718.

The untrusted app subnet(s)762can include primary VNICs764(1)-(N) that can be communicatively coupled to tenant virtual machines (VMs)766(1)-(N) residing within the untrusted app subnet(s)762. Each tenant VM766(1)-(N) can run code in a respective container767(1)-(N), and be communicatively coupled to an app subnet726that can be contained in a data plane app tier746that can be contained in a container egress VCN768. Respective secondary VNICs772(1)-(N) can facilitate communication between the untrusted app subnet(s)762contained in the data plane VCN718and the app subnet contained in the container egress VCN768. The container egress VCN can include a NAT gateway738that can be communicatively coupled to public Internet754(e.g. public Internet454ofFIG. 4).

The Internet gateway734contained in the control plane VCN716and contained in the data plane VCN718can be communicatively coupled to a metadata management service752(e.g. the metadata management system452ofFIG. 4) that can be communicatively coupled to public Internet754. Public Internet754can be communicatively coupled to the NAT gateway738contained in the control plane VCN716and contained in the data plane VCN718. The service gateway736contained in the control plane VCN716and contained in the data plane VCN718can be communicatively couple to cloud services756.

In some examples, the pattern illustrated by the architecture of block diagram700ofFIG. 7may be considered an exception to the pattern illustrated by the architecture of block diagram600ofFIG. 6and may be desirable for a customer of the IaaS provider if the IaaS provider cannot directly communicate with the customer (e.g., a disconnected region). The respective containers767(1)-(N) that are contained in the VMs766(1)-(N) for each customer can be accessed in real-time by the customer. The containers767(1)-(N) may be configured to make calls to respective secondary VNICs772(1)-(N) contained in app subnet(s)726of the data plane app tier746that can be contained in the container egress VCN768. The secondary VNICs772(1)-(N) can transmit the calls to the NAT gateway738that may transmit the calls to public Internet754. In this example, the containers767(1)-(N) that can be accessed in real-time by the customer can be isolated from the control plane VCN716and can be isolated from other entities contained in the data plane VCN718. The containers767(1)-(N) may also be isolated from resources from other customers.

In other examples, the customer can use the containers767(1)-(N) to call cloud services756. In this example, the customer may run code in the containers767(1)-(N) that requests a service from cloud services756. The containers767(1)-(N) can transmit this request to the secondary VNICs772(1)-(N) that can transmit the request to the NAT gateway that can transmit the request to public Internet754. Public Internet754can transmit the request to LB subnet(s)722contained in the control plane VCN716via the Internet gateway734. In response to determining the request is valid, the LB subnet(s) can transmit the request to app subnet(s)726that can transmit the request to cloud services756via the service gateway736.

FIG. 8illustrates an example computer system800, in which various embodiments may be implemented. The system800may be used to implement any of the computer systems described above. As shown in the figure, computer system800includes a processing unit804that communicates with a number of peripheral subsystems via a bus subsystem802. These peripheral subsystems may include a processing acceleration unit806, an I/O subsystem808, a storage subsystem818and a communications subsystem824. Storage subsystem818includes tangible computer-readable storage media822and a system memory810.

Processing unit804, which can be implemented as one or more integrated circuits (e.g., a conventional microprocessor or microcontroller), controls the operation of computer system800. One or more processors may be included in processing unit804. These processors may include single core or multicore processors. In certain embodiments, processing unit804may be implemented as one or more independent processing units832and/or834with single or multicore processors included in each processing unit. In other embodiments, processing unit804may also be implemented as a quad-core processing unit formed by integrating two dual-core processors into a single chip.

In various embodiments, processing unit804can execute a variety of programs in response to program code and can maintain multiple concurrently executing programs or processes. At any given time, some or all of the program code to be executed can be resident in processor(s)804and/or in storage subsystem818. Through suitable programming, processor(s)804can provide various functionalities described above. Computer system800may additionally include a processing acceleration unit806, which can include a digital signal processor (DSP), a special-purpose processor, and/or the like.

Computer system800may comprise a storage subsystem818that comprises software elements, shown as being currently located within a system memory810. System memory810may store program instructions that are loadable and executable on processing unit804, as well as data generated during the execution of these programs.

Storage subsystem818may also provide a tangible computer-readable storage medium for storing the basic programming and data constructs that provide the functionality of some embodiments. Software (programs, code modules, instructions) that when executed by a processor provide the functionality described above may be stored in storage subsystem818. These software modules or instructions may be executed by processing unit804. Storage subsystem818may also provide a repository for storing data used in accordance with the present disclosure.

Storage subsystem800may also include a computer-readable storage media reader820that can further be connected to computer-readable storage media822. Together and, optionally, in combination with system memory810, computer-readable storage media822may comprehensively represent remote, local, fixed, and/or removable storage devices plus storage media for temporarily and/or more permanently containing, storing, transmitting, and retrieving computer-readable information.

Communications subsystem824provides an interface to other computer systems and networks. Communications subsystem824serves as an interface for receiving data from and transmitting data to other systems from computer system800. For example, communications subsystem824may enable computer system800to connect to one or more devices via the Internet. In some embodiments communications subsystem824can include radio frequency (RF) transceiver components for accessing wireless voice and/or data networks (e.g., using cellular telephone technology, advanced data network technology, such as 3G, 4G or EDGE (enhanced data rates for global evolution), WiFi (IEEE 802.11 family standards, or other mobile communication technologies, or any combination thereof), global positioning system (GPS) receiver components, and/or other components. In some embodiments communications subsystem824can provide wired network connectivity (e.g., Ethernet) in addition to or instead of a wireless interface.

In some embodiments, communications subsystem824may also receive input communication in the form of structured and/or unstructured data feeds826, event streams828, event updates830, and the like on behalf of one or more users who may use computer system800.

Communications subsystem824may also be configured to output the structured and/or unstructured data feeds826, event streams828, event updates830, and the like to one or more databases that may be in communication with one or more streaming data source computers coupled to computer system800.