US10599500B2 - API registry in a container platform for automatically generating client code libraries - Google Patents

API registry in a container platform for automatically generating client code libraries Download PDF

Info

Publication number
US10599500B2
US10599500B2 US16/147,334 US201816147334A US10599500B2 US 10599500 B2 US10599500 B2 US 10599500B2 US 201816147334 A US201816147334 A US 201816147334A US 10599500 B2 US10599500 B2 US 10599500B2
Authority
US
United States
Prior art keywords
service
api
services
registry
functions
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US16/147,334
Other languages
English (en)
Other versions
US20190102239A1 (en
Inventor
Claudio Caldato
Boris Scholl
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Oracle International Corp
Original Assignee
Oracle International Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oracle International Corp filed Critical Oracle International Corp
Priority to US16/147,334 priority Critical patent/US10599500B2/en
Assigned to ORACLE INTERNATIONAL CORPORATION reassignment ORACLE INTERNATIONAL CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CALDATO, CLAUDIO, SCHOLL, Boris
Publication of US20190102239A1 publication Critical patent/US20190102239A1/en
Priority to US16/826,629 priority patent/US11132241B2/en
Application granted granted Critical
Publication of US10599500B2 publication Critical patent/US10599500B2/en
Priority to US17/485,689 priority patent/US11755393B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2023—Failover techniques
    • G06F11/203—Failover techniques using migration
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Prevention of errors by analysis, debugging or testing of software
    • G06F11/362—Debugging of software
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Prevention of errors by analysis, debugging or testing of software
    • G06F11/362—Debugging of software
    • G06F11/3644—Debugging of software by instrumenting at runtime
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/602—Providing cryptographic facilities or services
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/448—Execution paradigms, e.g. implementations of programming paradigms
    • G06F9/4488—Object-oriented
    • G06F9/449—Object-oriented method invocation or resolution
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/505—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5072—Grid computing
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5083—Techniques for rebalancing the load in a distributed system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45562—Creating, deleting, cloning virtual machine instances
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482—Interaction with lists of selectable items, e.g. menus
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G06F8/63—Image based installation; Cloning; Build to order
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects

Definitions

  • containers in any form represent a standardized method of packaging and interacting with information. Containers can be isolated from each other and used in parallel without any risk of cross-contamination.
  • a software container such as a Docker® container, is a software construct the logically encapsulates and defines a piece of software.
  • the most common type of software to be encapsulated in the container is an application, service, or microservice.
  • Modern containers also include all of the software support required for the application/service to operate, such as an operating system, libraries, storage volumes, configuration files, application binaries, and other parts of a technology stack that would be found in a typical computing environment.
  • Containers can be deployed in a production data center, an on-premises data center, a cloud computing platform, and so forth without any changes. Spinning up a container on the cloud is the same as spinning up a container on a local workstation.
  • Containers can be instantiated to focus on individual specific tasks, and multiple containers can then work in concert to implement sophisticated applications.
  • This may be referred to as a microservice architecture, and each container can use different versions of programming languages and libraries that can be upgraded independently.
  • the isolated nature of the processing within containers allows them to be upgraded and replaced with little effort or risk compared to changes that will be made to a larger, more monolithic architectures.
  • Container platforms are much more efficient than traditional virtual machines in running this microservice architecture, although virtual machines can be used to run a container platform.
  • a method of providing Application Programming Interface (API) functions for registered service endpoints in container environments may include receiving, at an API registry, an API definition that may include an endpoint of a first service that is encapsulated in a container that is deployed in a container environment and one or more API functions.
  • the method may also include creating, by the API registry, a binding between the one or more API functions and the endpoint of the service; receiving, by the API registry, a request from a second service to use the first service; and providing, by the API registry, the one or more API functions to the second service.
  • API Application Programming Interface
  • a non-transitory, computer-readable medium may include instructions that, when executed by one or more processors, causes the one or more processors to perform operations including receiving, at an API registry, an API definition that may include an endpoint of a first service that is encapsulated in a container that is deployed in a container environment and one or more API functions.
  • the operations may also include creating, by the API registry, a binding between the one or more API functions and the endpoint of the service; receiving, by the API registry, a request from a second service to use the first service; and providing, by the API registry, the one or more API functions to the second service.
  • a system may include one or more processors and one or more memory devices comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform operations including receiving, at an API registry, an API definition that may include an endpoint of a first service that is encapsulated in a container that is deployed in a container environment and one or more API functions.
  • the operations may also include creating, by the API registry, a binding between the one or more API functions and the endpoint of the service; receiving, by the API registry, a request from a second service to use the first service; and providing, by the API registry, the one or more API functions to the second service.
  • the method/operations may also include generating a client library for the second service that includes the one or more API functions.
  • the client library may include an object class with member functions that implement the API functions.
  • the client library may include a direct call to the endpoint of the first service.
  • the client library may include code that updates the endpoint of the first service at runtime when one of the one or more API functions is called by the second service.
  • the client library may reformat data received as one or more parameters of the one or more API functions into an HTTP call to the endpoint of the first service.
  • the client library may request additional information from a third service to add to the HTTP call of the endpoint of the first service.
  • the client library may include code that retries unsuccessful calls to the first service.
  • the client library may include code that extracts a result value from a result set of the first service and packages the result value as a return value for the one or more API functions.
  • the endpoint of the first service may include an IP address and a port number.
  • the container environment may include a plurality of services encapsulated in containers.
  • the API registry may be deployed as a service encapsulated in a container in the container environment. the API registry is available to services in development in an Integrated Development Environment (IDE) and services already deployed in the container environment.
  • the method/operations may also include identifying, by the API registry, any available endpoints for containerized services that have been deployed to the container environment.
  • the method/operations may further include causing a list of API functions for all services registered with the API registry to be displayed in a user interface.
  • the request from the second service to use the first service may be received by receiving a selection of one of the one or more API functions displayed in the user interface.
  • the user interface may include a command line interface.
  • the user interface may include a graphical user interface.
  • FIG. 1 illustrates a software structure and logical arrangement of development and runtime environments for services in a container platform, according to some embodiments.
  • FIG. 2 illustrates a specialized computer hardware system that is specifically designed to run the embodiments described herein.
  • FIG. 3 illustrates a data organization that may be specific to the container platform used by some of the embodiments described herein.
  • FIG. 4 illustrates an API registry that can be deployed to the IDE and the production/runtime environment, according to some embodiments.
  • FIG. 5 illustrates the deployment of the API registry for use with the container platform at runtime, according to some embodiments.
  • FIG. 6A illustrates a flowchart of a method for deploying the API registry, according to some embodiments.
  • FIG. 6B illustrates a software structure of a container platform when the API registry is deployed using the flowchart in FIG. 6A , according to some embodiments.
  • FIG. 7A illustrates a flowchart of a method for registering a service with the API registry, according to some embodiments.
  • FIG. 7B illustrates a hardware/software diagram of the steps for registering an API with the API registry, according to some embodiments.
  • FIG. 8 illustrates examples of a graphical interface and a command line interface for browsing and selecting APIs that are registered with the API registry, according to some embodiments.
  • FIG. 9 illustrates a flowchart of a method for using a service and its corresponding function registered with the API registry, according to some embodiments.
  • FIG. 10 illustrates how a selection may be received by the API registry through the graphical interface of the CreateUser( ) function.
  • FIG. 11 illustrates an example of a client library generated automatically for a service by the API registry, according to some embodiments.
  • FIG. 12 illustrates an embodiment of a client library that accommodates dynamic binding between service endpoints and API functions, according to some embodiments.
  • FIG. 13 illustrates an embodiment of a client library that can marshal additional data to complete an input data set for a service call, according to some embodiments.
  • FIG. 14 illustrates a client library that can handle retries when calling a service, according to some embodiments.
  • FIG. 15 illustrates a simplified block diagram of a distributed system for implementing some of the embodiments.
  • FIG. 16 illustrates a simplified block diagram of components of a system environment by which services provided by the components of an embodiment system may be offered as cloud services.
  • FIG. 17 illustrates an exemplary computer system, in which various embodiments may be implemented.
  • API registry that is part of an Integrated Development Environment (IDE) that allows developers to register services during development and make those services available to other services both during and after deployment.
  • the API registry can be deployed as part of an orchestrated container platform, operating as a containerized application on the container platform. As services or microservices are developed and deployed into containers on the container platform, the API registry can execute a discovery process to locate available endpoints (e.g., IP addresses and port numbers) within the container platform that correspond to available services.
  • the API registry can also accept an upload of an API definition file that can be used to turn the raw service endpoint into an API function made available through the API registry.
  • the API registry can dynamically bind the discovered endpoint to an API function that be kept up-to-date and made available to other services in the container platform. This provides a stable endpoint that other services can statically call while the API registry manages any changes to the binding between the API function in the service endpoint. This also simplifies the process for using services in the container platform. Instead of writing code for an HTTP call, new services can simply use the API interface to access registered services.
  • the IDE can provide a navigation/browse interface for developers to locate services that are available in the container platform and registered with the API registry.
  • the API registry can automatically generate a set of client libraries that include all the necessary functionality to interact with the registered service. For example, some embodiments may generate an object class that includes member functions corresponding to API calls. During development, new services can simply instantiate these objects and/or use their member functions to make a call to the corresponding API.
  • the code in the client libraries governs a direct connection between the calling service and the endpoint of the registered service and may include code that handles all the functionality necessary for this interaction.
  • the automatically generated client libraries may include: code for packaging and formatting parameters from the API call into an HTTP call to the service endpoint, code for marshaling data to complete parameter sets for the call, code for packaging information into a compatible packet (JSON, XML, etc.), code for receiving and parsing result packets, code for handling retries and error conditions, and so forth.
  • code to handle all of this functionality is automatically generated by the API registry and therefore abstracts and encapsulates the details of the service call into the client library object. All that is required of the calling service is to execute a member function of the client library object created by the API registry.
  • the API registry can also accept an upload of a set of properties that may define the runtime execution of the registered service.
  • This set of properties can be uploaded during development along with the API definition file.
  • These properties can define runtime characteristics, such as end-to-end encryption, usage/logging requirements, user authentication, on-demand service instantiation, multiple service deployment instances for high availability, rate/usage limiting, and other runtime characteristics.
  • the API registry can ensure that these properties are met by interacting with the container environment during development, during deployment, and during runtime.
  • the automatically generated client libraries for calling services can include code that may be required to execute these properties, such as encryption code, usage logging code, and/or interaction with a user authentication service.
  • the API registry can instruct the container platform to instantiate multiple instances of the service and/or additional load-balancing modules to ensure high reliability of the service during runtime.
  • the API registry can cause the service to be instantiated for on-demand instantiation, limit the number of API calls that can be made to throttle usage, and perform other runtime functions.
  • FIG. 1 illustrates a software structure and logical arrangement of development and runtime environments for services in a container platform, according to some embodiments.
  • the environments may include an IDE 102 that may be used to develop services and microservices to be deployed on a container platform.
  • An IDE is a software suite that consolidates and provides all of the basic tools that service developers can use to write and test new services.
  • the IDE 102 may include a source code editor 106 with a graphical user interface (GUI), code completion functions, and navigate/browse interfaces that allow a developer to write, navigate, integrate, and visualize the source-code-writing process.
  • GUI graphical user interface
  • the IDE 102 may also include a debugger 110 that includes variable interfaces, immediate variable interfaces, expression evaluation interfaces, memory content interfaces, breakpoint visualization and functionality, and other debugging functions.
  • the IDE 102 may also include a compiler and/or interpreter 108 for compiling and running compiled machine code or interpreted byte code.
  • the compiler/interpreter 108 can include build tools that allow developers to use/generate makefiles another build automation constructs.
  • Some embodiments of the IDE 102 may include code libraries 112 that include common code functions, objects, interfaces, and/or other structures that can be linked into a service under development and reused across multiple developments.
  • Services can be developed and thoroughly tested within the IDE 102 until they are ready for deployment. The services can then be deployed to a production/deployment environment 104 .
  • the production/development environment 104 may include many different hardware and/or software structures, including dedicated hardware, virtual machines, and containerized platforms. Prior to this disclosure, when a service 114 was deployed into the production/deployment environment 104 , the service 114 would no longer have runtime access to many of the tools used in the IDE 102 . Any functionality needed by the service 114 to run in the production/development environment 104 needed to be packaged from the code libraries 112 and deployed with the service 114 into the production/deployment environment 104 .
  • the service 114 would typically be deployed without any of the functionality for the debugger 110 or a copy of the source code from the source code editor 106 . Essentially, the service 114 would be deployed to the production/deployment environment 104 with all of the functionality required for runtime operation, but would be stripped of the information that was only used during development.
  • FIG. 2 illustrates a specialized computer hardware system that is specifically designed to run the embodiments described herein.
  • the service 114 can be deployed into an Infrastructure as a Service (IaaS) cloud computing environment 202 .
  • IaaS Infrastructure as a Service
  • the IaaS cloud computing environment 202 may also include or be coupled with other cloud computing environments arranged as Software as a Service (SaaS) and/or Platform as a Service (PaaS) architectures.
  • the cloud provider can host an infrastructure of hardware and/or software components that were traditionally present in an on-premises data center.
  • This hardware may include servers, storage, networking hardware, disk arrays, software libraries, and virtualization utilities such as a hypervisor layer.
  • the IaaS environment 202 can be provided by a commercial source, such as Oracle® or other publicly available cloud platforms.
  • the IaaS environment 202 may also be deployed as a private cloud using a private infrastructure of hardware and software.
  • the service 114 can be deployed onto a number of different types of hardware/software systems.
  • the service 114 can be deployed to dedicated hardware 206 .
  • the dedicated hardware 206 may include hardware resources, such as servers, disks, operating systems, software packages, and so forth, that are specifically assigned to the service 114 .
  • a specific server may be allocated to handle traffic flowing to and from the service 114 .
  • the service 114 can be deployed to hardware/software that is operated as one or more virtual machines 208 .
  • a virtual machine is an emulation of a computer system that provides the functionality of the dedicated computer hardware 206 .
  • the physical hardware can be shared by number of different virtual machines. Each virtual machine can provide all the functionality needed to execute including a complete operating system. This allows virtual machines having different operating systems to run on the same physical hardware and allows multiple services to share a single piece of hardware.
  • the service 114 can be deployed to a container platform 210 .
  • the container platform differs from the virtual machines 208 in a number of important ways.
  • the container platform 210 packages individual services into containers as described in greater detail below in FIG. 3 .
  • Each container shares a host operating system kernel, and they also share binaries, libraries, and other read-only components. This allows containers to be exceptionally light often only a few megabytes in size. Additionally, a lightweight container is very efficient, taking just seconds to start versus the minutes required to boot up a virtual machine. Containers also reduce management overhead by sharing the operating system and other libraries that can be maintained together for the entire set of containers in the container platform 210 .
  • Container technologies may include Docker® containers, the Linux Libcontainer®, the Open Container Initiative (OCI), Kubernetes®, CoeOS, Apache® Mesos, along with others. These containers can be deployed to a container orchestration platform, which may be referred to herein as simply the “container platform” 210 .
  • a container platform manages the automated arrangement, coordination, and management of deployed software containers.
  • the container platform 210 can provide service discovery, load-balancing, health checks, multiple deployments, and so forth.
  • the container platform 210 may be implemented by any publicly available container platform, such as Kubernetes, that runs containers organized in nodes and pods.
  • each of the platforms 206 , 208 , 210 can provide service endpoints 212 , 214 , 216 that provide public access for calling the service 114 .
  • these endpoints can be accessed through an HTTP call and are associated with an IP address and a port number.
  • IP address and port number By connecting to the correct IP address and port number, other services can call services deployed to any of the platforms 206 , 208 , 210 when they are made publicly available.
  • Each service such as service 114 , may include its own proprietary formats and data requirements for calling the service. Similarly, each service may return results that are specific in format and data type to that service 114 .
  • the particular deployment platform 206 , 208 , 210 may also include additional requirements for interacting with the service 114 , such as programming languages, package formats (JSON, XML, etc.) that need to be complied with to properly interact with the service, and so forth.
  • additional requirements for interacting with the service 114 such as programming languages, package formats (JSON, XML, etc.) that need to be complied with to properly interact with the service, and so forth.
  • the embodiments described herein are specifically designed for the container platform 210 described above.
  • embodiments that are specifically recited to be deployed in a “container platform” can be distinguished from other embodiments that are specifically recited to be deployed in a virtual machine platform, on the server or dedicated hardware platform, or generally in an IaaS environment.
  • FIG. 3 illustrates a data organization that may be specific to the container platform 210 used by some of the embodiments described herein.
  • a pod is an abstraction that represents a group of one or more application containers (e.g., Docker or rkt).
  • a pod may also include some shared resources that are commonly available to all of the containers within the pod.
  • pod 304 includes container 310 and container 312 .
  • Pod 304 also includes a shared resource 308 .
  • the resource may include a storage volume or other information about how containers are run or connected within the pod 304 .
  • the pod 304 can model an application-specific logical host that contains different service containers 310 , 312 that are relatively tightly coupled.
  • service 326 in container 310 can utilize the resource 308 and call service 320 in container 312 .
  • Service 320 can also call service 322 , which in turn calls service 324 , each of which are deployed to container 312 .
  • the output of service 324 can be provided to a network IP address and port 318 , which is another common resource shared by the pod 304 .
  • the services 320 , 322 , 324 , 326 all work together with the shared resource 308 to provide a single service that can be accessed by the IP address and port number 318 by services run in other containers.
  • the service can also be accessed through the IP address and port 318 by computer systems that are external to the container platform, such as a workstation, a laptop computer, a smart phone, or other computing device that is not part of the container platform or IaaS environment.
  • each container may include a single service
  • each pod may include a single container that encapsulates the service.
  • pod 306 includes only a single container 314 with a single service 328 .
  • the single service is accessible through the IP address and port number 316 of the pod 306 .
  • a container and a pod will be instantiated to hold the service.
  • a number of different pods can be deployed to a container node 302 .
  • pods run within nodes.
  • a node represents a worker machine (either virtual or physical) in the container platform.
  • Each node is managed by a “master” that automatically handles scheduling pods within each of the nodes.
  • Each node can run a process that is responsible for communication between the master and the node and for managing the pods in containers on the machine represented by the node.
  • Each node may also include a container runtime responsible for pulling a container image from a registry, unpacking the container, and running the service.
  • FIG. 4 illustrates an API registry 404 that can be deployed to the IDE 102 and the production/runtime environment 104 , according to some embodiments.
  • a technical problem exists wherein when the service 114 is deployed from the IDE 102 to the production/deployment environment 104 , the service 114 loses runtime access to information that is exclusively available in the IDE 102 .
  • the API registry 404 is accessible by the service 114 while it is deployed and operating during runtime in the production/development environment 104 .
  • the previous technical problem that isolated development functions from runtime functions is overcome by the API registry 404 by the registration of services with the API registry 404 during development and providing an API definition and/or API properties to the API registry 404 .
  • the information defining the API can be used by new services in development in the IDE 102 as well as services that have been deployed to the production/deployment environment 104 .
  • the service 114 can operate using client libraries that access the API registry 404 during runtime to ensure that the API functions are correctly bound to the current IP address and port number of the corresponding service.
  • the API registry 404 represents a new data structure and processing unit that was specifically designed to solve these technical problems.
  • Another technical problem that existed in the art was implementing service properties as they are deployed to the production/development environment 104 .
  • the developer would need to build container deployment files that specifically instantiated multiple instances of the service in the container platform and balanced traffic in such a way that the service was always available.
  • Service developers did not always have this expertise, nor were they often able to manage the deployment of their service.
  • the API registry 404 allows a service to simply select properties, such as high availability, that can then be implemented automatically by the API registry 404 . This technical solution is possible because the API registry 404 bridges the gap between the IDE 102 and the production/deployment environment 104 .
  • FIG. 5 illustrates the deployment of the API registry 404 for use with the container platform 210 at runtime, according to some embodiments.
  • One of the technical solutions and improvements to the existing technology offered by the API registry 404 is the maintenance of stable endpoints for service calls, as well as the simplification and automatic code generation for accessing the service calls.
  • calls between services were point-to-point connections using, for example, an HTTP call to an IP address and port number.
  • IP address and port number may change frequently. This required all services that called an updated service to update their IP address and port numbers in the actual code that called that service.
  • the API registry 404 solves this technical problem by providing a dynamic binding between the IP address and port number of a service and an API function that is made available through the API registry.
  • the client libraries that are automatically generated by the API registry 404 can include a function that accesses the API registry 404 to retrieve and/or verify a current IP address and port number for a particular service.
  • a first service connecting to a second service need only perform a one-time generation of a client library to provide a lifetime-stable connection to the second service.
  • API registry 404 Another technical problem solved by the API registry 404 is the automatic generation of client libraries.
  • a first service accessing a second service required the developer to write custom code for accessing the second service. Because this code could change over time, incompatibilities would a rise between the first and second services that required updates to both services.
  • the API registry 404 solves this technical problem by uploading an API definition file that is used to automatically generate client libraries for calling services. Therefore, a service can specify specifically how the calling code in any other service should operate, which guarantees compatibility.
  • client libraries also greatly simplify and encapsulate the code for calling the service.
  • a complicated HTTP call using IP address and a port numbers can be replaced with a simple member function call in a language that is specific to the calling service (e.g., Java, C#, etc.).
  • This allows a calling service to select an API function from the API registry 404 , and the code that implements at function can be downloaded to the calling service as a client library.
  • FIG. 6A illustrates a flowchart of a method for deploying the API registry 404 , according to some embodiments.
  • the method may include deploying the API registry service to the container environment ( 601 ).
  • the API registry can be implemented as a service operating in the container environment within the container. Thus, the API registry can be actively running after services are deployed within the container environment such that it can be accessed at run time.
  • the API registry can also be linked to the existing IDE described above.
  • the method may further include discovering ports for available services in the container platform ( 603 ). As services are deployed to the container platform, the API registry can launch a discovery process that sequentially traverses each of the services deployed to the container platform. For each service, the API registry can detect and record an IP address and a port number.
  • the listing of IP address and port numbers discovered by this process can be stored in a data structure, such as a table associated with the API registry. Each IP address and port number can also be stored with a name for the service or other identifier that uniquely identifies the service on the container platform.
  • FIG. 6B illustrates a software structure of the container platform 210 when the API registry is deployed using the flowchart in FIG. 6A , according to some embodiments.
  • the API registry 404 can be deployed to a container 620 in the container platform 210 .
  • the container 620 can operate within one or more pods and within a node as described above in FIG. 3 .
  • the API registry 404 can be made privately available to any of the other containers in the container platform 210 .
  • the API registry 404 can also be made publicly available to other devices that are not part of the container platform 210 .
  • the API registry 404 may have an IP address and port number that are available to other services.
  • the IP address and port number of the API registry 404 would only be used by the code that is automatically generated in client libraries, therefore some embodiments do not need to publish the IP address and port number for the API registry 404 .
  • the client libraries in the IDE itself can maintain an up-to-date listing of the IP address and port number for the API registry 404 such that it can be contacted during development, deployment, and runtime of other services.
  • the API registry 404 can execute a discovery process.
  • the discovery process can use a directory listing for nodes in the container platform to identify pods that implement services with an IP address and port number.
  • the API registry 404 can then access a unique identifier, such as a number or name for each available service, and store an identifier with each IP address and port number in the container platform 210 .
  • This discovery process can be periodically executed to detect new services that are added to the container platform 210 , as well as to identify existing services that are removed from the container platform 210 . As described below, this discovery process can also be used to detect when an IP address and port number change for an existing service.
  • the API registry 404 can discover services having endpoints 602 , 604 , 606 , 608 . In the process described below, the API registry 404 can bind each of these endpoints 602 , 604 , 606 , 608 to an API function that is registered with the API registry 404 . At some point after this initial discovery, the IP address and/or port number for endpoint 602 may be changed when the service associated with endpoint 602 is replaced, updated, or revised. The API registry 404 can detect this change to endpoint 602 and update a binding to an existing API function provided by the API registry 44 .
  • the API registry 404 can use the discovery process to detect when endpoints are no longer available, and then remove the API functions associated with the service.
  • the API registry 404 can provide a mock response to any service calling the corresponding API functions. For example, if an API has been registered for the service corresponding to endpoint 604 , but endpoint 604 is not currently available, the API registry 404 can intercept a call made to endpoint 604 and provide default or dummy data in response. This allows services that call the service associated with endpoint 604 to maintain functionality and/or continue the design process without “breaking” the connection to this particular service. Mock/testing data scenarios will be described in greater detail below.
  • FIG. 7A illustrates a flowchart of a method for registering a service with the API registry 404 , according to some embodiments.
  • the method may include receiving an upload of an API definition ( 701 ).
  • the API definition may be provided in the form of a data packet, file, or a link to an information repository.
  • the API definition may include any information that can be used to identify and define API functions that should be bound to endpoints associated with the service.
  • some embodiments of the API definition may include the following data: a service name or other unique identifier; function names corresponding to service endpoints and calls, data inputs required to call the service with corresponding descriptions and data types; result data formats and data types; a current IP address and/or port number; documentation that describes the functionality of the API functions that will be associated with the endpoint; default or dummy data values that should be returned during mock/test scenarios; and any other information that may be used by the API registry 404 to translate the HTTP request received by the endpoint into a client library that uses API function calls of class data objects.
  • the method may also include creating corresponding API functions based on the uploaded API definitions ( 703 ). These API functions can be generated automatically based on the API definition.
  • Each endpoint for a service may be associated with a plurality of different API functions.
  • an endpoint implementing a RESTful interface may receive HTTP calls for POST, GET, PUT, and DELETE functions at the same IP address and port number. This may result in, for example, for different API functions.
  • the interface represents a list of users, this can correspond to at least four different API functions, such as GetUser( ), AddUser( ), RemoveUser( ), and UpdateUser( ).
  • each API function may include a number of different parameter lists, such as UpdateUser(id), UpdateUser(name), UpdateUser(firstname, lastname), and so forth.
  • UpdateUser(id) can be generated and made available to other services through the API registry.
  • services are not required to call these functions through the API registry. Instead, these functions are made available to browse in the API registry, and when selected, the API registry can generate client libraries that implement these functions in the calling service.
  • the method may additionally include creating a binding in the API registry between the API function and the corresponding endpoint of the service ( 705 ).
  • the API registry can now create a dynamic binding between an endpoint for a service in the container platform and the API function created by the API registry.
  • the API registry can now store a corresponding function or set of functions for each endpoint.
  • this binding can be constantly updated as the discovery process determines when services are updated, moved, replaced, or added to the container platform. This allows the client libraries created in a calling service to first check with the API registry to verify or receive a current IP address and port number for the service.
  • FIG. 7B illustrates a hardware/software diagram of the steps for registering an API with the API registry 404 , according to some embodiments.
  • the API registry 404 can be instantiated and running in a container 620 in the container platform 210 . Even though the container platform 210 represents a production/deployment environment, the API registry 404 can still be accessed by the IDE 102 used to develop the service.
  • the IDE 102 can provide a mechanism for uploading the API definition files 702 to the API registry 404 .
  • the user interface of the IDE 102 may include a window or interface that allows the developer to define and/or populate fields for the API definition files 702 .
  • This information described above may include function names, parameter lists, data types, field lengths, object class definitions, an IP address and port number, a service name or other unique identifier, and so forth.
  • This information can be uploaded to the API registry 404 and linked in a dynamic binding to a particular IP address and port number for the endpoint 602 .
  • the API registry 404 can generate one or more API functions 704 that can be made available through the API registry 404 .
  • FIG. 8 illustrates examples of a graphical interface 802 and a command line interface 804 for browsing and selecting APIs that are registered with the API registry 804 , according to some embodiments.
  • the developer can access the graphical interface 802 to browse and select API functions that can be used in their service.
  • This graphical interface 802 is merely an example and not meant to be limiting of the types of graphical interfaces that can be used to browse and select API functions.
  • the IDE 102 can summon the graphical interface 802 to provide a list of APIs that are registered with the API registry.
  • the APIs are categorized based on endpoint. For example, one endpoint corresponding to a service may offer a RESTful interface for storing user records (e.g., “UserStorage”).
  • the graphical interface 802 can display all of the API functions (e.g., “CreateUser”, “DeleteUser”, “UpdateUser”, etc.) that are available through the selected endpoint. Other embodiments may group functions based on the overall service in cases where the service offers multiple endpoints.
  • the graphical interface 802 can receive a selection of one or more API functions to be used in a calling the service.
  • the API registry can then provide documentation that illustrates how to use the API function, including required parameters and return values.
  • the command line interface 804 can provide similar information and can receive similar inputs as the graphical interface 802 .
  • the interfaces 802 , 804 illustrated in FIG. 8 provide a number of technical benefits.
  • these interfaces 802 , 804 provide an up-to-date listing of all APIs that are registered with the API registry. This corresponds to a list of all services currently available in the container platform. Instead of being required to look up documentation, contact a service developer, and/or perform other inefficient tasks for locating a list of available services, a service developer can retrieve and display this information in real-time. Additionally, as services are updated, the API definition files can be updated in a corresponding fashion. This then updates the display illustrated in FIG. 8 to provide up-to-date availability information for each API function.
  • FIG. 9 illustrates a flowchart of a method for using a service and its corresponding function registered with the API registry, according to some embodiments.
  • the method may include providing a listing of registered APIs ( 901 ). This step may be omitted in cases where the desired service is already known. However, generally the services can be displayed for browsing and navigation using the interfaces described above in FIG. 8 .
  • the method may also include receiving a selection of an API function ( 901 ). This selection may be received by the API registry from a developer of the service. For example, a developer may decide to update a database of user records using the CreateUser( ) function described above.
  • FIG. 10 illustrates how a selection 1002 may be received by the API registry through the graphical interface 802 for the CreateUser( ) function. Other embodiments may receive the selection through the command line interface or through other input methods provided by the IDE.
  • the API registry can generate one or more client libraries for the calling service ( 905 ).
  • Generating client libraries may provide the calling service with the service endpoint that is dynamically bound to the API function.
  • the IDE can generate a set of class objects in the IDE that encapsulate the functionality required to interface directly with the service endpoint in the container platform.
  • client libraries may include object classes that can be instantiated or used to call member functions that embody the code required to communicate with the service. Examples of these client libraries will be described in greater detail below.
  • the method may additionally include providing test data ( 907 ).
  • test data When a service is registered with the API registry, it need not be complete. Instead, the service can indicate to the API registry that it is not yet ready to provide functional responses to calling services.
  • the API definition file that is uploaded to the API registry can include a specification of the type of information that should be returned before the service is functional.
  • the client library generated by the API registry can route requests to the API registry instead of the service endpoint. The API registry can then provide a response using dummy, null, or default values. Alternatively, the code within the client libraries themselves can generate the default data to be returned to the calling service.
  • FIG. 9 provides particular methods of using an API registry according to various embodiments of the present invention. Other sequences of steps may also be performed according to alternative embodiments. For example, alternative embodiments of the present invention may perform the steps outlined above in a different order. Moreover, the individual steps illustrated in FIG. 9 may 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.
  • the User service may use a RESTful interface to edit individual user records that are stored by the service.
  • the API registry can generate the CreateUser( ) function to implement a POST call to the User service.
  • One of the functions that can be performed by the class library is to parse, filter, and format data provided as parameters to the API function to be sent as a data packet directly to the service.
  • the CreateUser( ) function can accept parameters that are formatted for the convenience of the calling service.
  • the calling service may separately store strings for the user first name and the user last.
  • the POST command may require a concatenated string of the first name in the last name together.
  • the client library 1102 can perform a set operations that format the data received as parameters to the function into a format that is compatible with the service endpoint. This may include generating header information, altering the format of certain data fields, concatenating data fields, requesting additional data from other sources, performing calculations or data transforms, and so forth. This may also include packaging the reformatted parameters into a format, such as JSON, XML, etc.
  • the client library 1102 can also handle the POST call to the service.
  • the IP address and port number for the service can be inserted into the CreateUser( ) function to be used in an HTTP request to the service.
  • the details of the HTTP request are encapsulated in the CreateUser( ) function.
  • a developer for a calling service wants to use the POST function made available by the service, instead of writing the code in the library 1102 themselves, they can instead select the User service from the API registry.
  • the API registry will then automatically generate the client library 1102 that includes the User class.
  • the service developer can simply use the User.CreateUser (“John”, “Smith”, 2112 ) function to add the user John Smith to the service.
  • FIG. 12 illustrates an embodiment of a client library 1202 that accommodates dynamic binding between service endpoints and API functions, according to some embodiments.
  • the CreateUser( ) function can include code 1204 that dynamically retrieves the IP address and port number for the service.
  • the calling service 114 can use the GetIPPort( ) function to send a request to the API registry 404 at run time when the calling service 114 is operating in the production/deployment environment 104 , such as the container platform.
  • the API registry 404 can access its internal table that is consistently updated to maintain up-to-date bindings between the API functions and the service endpoints.
  • the API registry 404 can then return a current IP address and port number to the calling service 114 .
  • the client library 1202 can then insert the IP address and port number into the HTTP POST code that connects to the service. Because the API registry 404 can be accessed at run time by any calling service in the container platform, none of these services need to be updated or patched when the IP address for port number for the service being called changes. Instead, the API registry 404 can provide up-to-date information every time a service is called.
  • the GetIPPort( ) function may only need to call the API registry 404 once an hour, once a day, once a week, and so forth, to minimize the number of function calls made outside of the container for the service 114 under the assumption that the service endpoints do not change frequently in the production environment.
  • FIG. 13 illustrates an embodiment of a client library 1302 that can marshal additional data to complete an input data set for a service call, according to some embodiments.
  • the client library 1302 may minimize the number of parameters required from the service developer. Additional data that may be required to make the service call can be retrieved from other sources and thus may be omitted from the parameter list. These additional parameters can instead be retrieved directly by the client library 1302 from these other sources. For example, creating a new user may include specifying a user role for the user. Instead of requiring the service developer to provide a user role as one of the parameters, the client library 1302 can instead include code 1304 that automatically retrieves a role for the user from some other source.
  • the client library 1302 can also parse and return data received from the service and handle error conditions.
  • the POST command may return a data packet into the Result variable.
  • a service may return a data packet that includes more information than the calling service needs. Therefore, the client library 1302 can parse the data fields in the Result variable and extract, format, and package data from the Result variable into a format that is more usable and expected by the User class.
  • the code 1306 can extract fields from the Result variable and use them to create a new User object that is returned from the API function.
  • individual API functions can be generated in the User class that extract different fields from the Result variable from the GET command.
  • the User class could provide a GetFirstName(id) function, a GetLastName(id) function, a GetRole(id) function, and so forth. Each of these functions may include very similar code while returning different fields from the Result variable.
  • the client library 1302 may also generate code 1308 that handles error conditions associated with using the service.
  • the code 1308 can test a status field in the Result variable to determine whether the POST command was successful. If the command was successful, then the CreateUser( ) function can return a new User object. In cases where the Post command failed, the function can instead return a null object and/or retry the call to the service.
  • FIG. 14 illustrates a client library 1402 that can handle retries when calling a service, according to some embodiments.
  • the client library 1402 uses a status in a Result variable populated by the POST HTTP call to determine whether the call was successful or not. While the result is unsuccessful, the client library 1402 can continue to retry until the call is successful. Some embodiments may use a counter or other mechanism to limit the number of retries or add a wait time between retries.
  • Each of the methods described herein may be implemented by a specialized computer system. Each step of these methods may be executed automatically by the computer system, and/or may be provided with inputs/outputs involving a user. For example, a user may provide inputs for each step in a method, and each of these inputs may be in response to a specific output requesting such an input, wherein the output is generated by the computer system. Each input may be received in response to a corresponding requesting output. Furthermore, inputs may be received from a user, from another computer system as a data stream, retrieved from a memory location, retrieved over a network, requested from a web service, and/or the like.
  • each step of the methods described herein may be performed by a computer system, and may involve any number of inputs, outputs, and/or requests to and from the computer system which may or may not involve a user. Those steps not involving a user may be said to be performed automatically by the computer system without human intervention. Therefore, it will be understood in light of this disclosure, that each step of each method described herein may be altered to include an input and output to and from a user, or may be done automatically by a computer system without human intervention where any determinations are made by a processor. Furthermore, some embodiments of each of the methods described herein may be implemented as a set of instructions stored on a tangible, non-transitory storage medium to form a tangible software product.
  • FIG. 15 depicts a simplified diagram of a distributed system 1500 that may interact with any of the embodiments described above.
  • distributed system 1500 includes one or more client computing devices 1502 , 1504 , 1506 , and 1508 , which are configured to execute and operate a client application such as a web browser, proprietary client (e.g., Oracle Forms), or the like over one or more network(s) 1510 .
  • Server 1512 may be communicatively coupled with remote client computing devices 1502 , 1504 , 1506 , and 1508 via network 1510 .
  • the software components 1518 , 1520 and 1522 of system 1500 are shown as being implemented on server 1512 .
  • one or more of the components of system 1500 and/or the services provided by these components may also be implemented by one or more of the client computing devices 1502 , 1504 , 1506 , and/or 1508 . Users operating the client computing devices may then utilize one or more client applications to use the services provided by these components.
  • These components may be implemented in hardware, firmware, software, or combinations thereof. It should be appreciated that various different system configurations are possible, which may be different from distributed system 1500 .
  • the embodiment shown in the figure is thus one example of a distributed system for implementing an embodiment system and is not intended to be limiting.
  • Client computing devices 1502 , 1504 , 1506 , and/or 1508 may be portable handheld devices (e.g., an iPhone®, cellular telephone, an iPad®, computing tablet, a personal digital assistant (PDA)) or wearable devices (e.g., a Google Glass® head mounted display), running software such as Microsoft Windows Mobile®, and/or a variety of mobile operating systems such as iOS, Windows Phone, Android, Blackberry 10, Palm OS, and the like, and being Internet, e-mail, short message service (SMS), Blackberry®, or other communication protocol enabled.
  • the client computing devices can be general purpose personal computers including, by way of example, personal computers and/or laptop computers running various versions of Microsoft Windows®, Apple Macintosh®, and/or Linux operating systems.
  • the client computing devices can be workstation computers running any of a variety of commercially-available UNIX® or UNIX-like operating systems, including without limitation the variety of GNU/Linux operating systems, such as for example, Google Chrome OS.
  • client computing devices 1502 , 1504 , 1506 , and 1508 may be any other electronic device, such as a thin-client computer, an Internet-enabled gaming system (e.g., a Microsoft Xbox gaming console with or without a Kinect® gesture input device), and/or a personal messaging device, capable of communicating over network(s) 1510 .
  • exemplary distributed system 1500 is shown with four client computing devices, any number of client computing devices may be supported. Other devices, such as devices with sensors, etc., may interact with server 1512 .
  • Network(s) 1510 in distributed system 1500 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 (transmission control protocol/Internet protocol), SNA (systems network architecture), IPX (Internet packet exchange), AppleTalk, and the like.
  • network(s) 1510 can be a local area network (LAN), such as one based on Ethernet, Token-Ring and/or the like.
  • LAN local area network
  • Network(s) 1510 can be a wide-area network and the Internet.
  • a virtual network including without limitation a virtual private network (VPN), 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 Institute of Electrical and Electronics (IEEE) 802.11 suite of protocols, Bluetooth®, and/or any other wireless protocol); and/or any combination of these and/or other networks.
  • VPN virtual private network
  • PSTN public switched telephone network
  • IEEE Institute of Electrical and Electronics 802.11 suite of protocols
  • Bluetooth® Bluetooth®
  • any other wireless protocol any combination of these and/or other networks.
  • Server 1512 may be composed of one or more general purpose computers, specialized server computers (including, by way of example, PC (personal computer) servers, UNIX® servers, mid-range servers, mainframe computers, rack-mounted servers, etc.), server farms, server clusters, or any other appropriate arrangement and/or combination.
  • server 1512 may be adapted to run one or more services or software applications described in the foregoing disclosure.
  • server 1512 may correspond to a server for performing processing described above according to an embodiment of the present disclosure.
  • Server 1512 may run an operating system including any of those discussed above, as well as any commercially available server operating system. Server 1512 may also run any of a variety of additional server applications and/or mid-tier applications, including HTTP (hypertext transport protocol) servers, FTP (file transfer protocol) servers, CGI (common gateway interface) servers, JAVA® servers, database servers, and the like. Exemplary database servers include without limitation those commercially available from Oracle, Microsoft, Sybase, IBM (International Business Machines), and the like.
  • server 1512 may include one or more applications to analyze and consolidate data feeds and/or event updates received from users of client computing devices 1502 , 1504 , 1506 , and 1508 .
  • data feeds and/or event updates may include, but are not limited to, Twitter® feeds, Facebook® updates or real-time updates received from one or more third party information sources and continuous data streams, which may include real-time events related to sensor data applications, financial tickers, network performance measuring tools (e.g., network monitoring and traffic management applications), clickstream analysis tools, automobile traffic monitoring, and the like.
  • Server 1512 may also include one or more applications to display the data feeds and/or real-time events via one or more display devices of client computing devices 1502 , 1504 , 1506 , and 1508 .
  • Distributed system 1500 may also include one or more databases 1514 and 1516 .
  • Databases 1514 and 1516 may reside in a variety of locations.
  • one or more of databases 1514 and 1516 may reside on a non-transitory storage medium local to (and/or resident in) server 1512 .
  • databases 1514 and 1516 may be remote from server 1512 and in communication with server 1512 via a network-based or dedicated connection.
  • databases 1514 and 1516 may reside in a storage-area network (SAN).
  • SAN storage-area network
  • any necessary files for performing the functions attributed to server 1512 may be stored locally on server 1512 and/or remotely, as appropriate.
  • databases 1514 and 1516 may include relational databases, such as databases provided by Oracle, that are adapted to store, update, and retrieve data in response to SQL-formatted commands.
  • FIG. 16 is a simplified block diagram of one or more components of a system environment 1600 by which services provided by one or more components of an embodiment system may be offered as cloud services, in accordance with an embodiment of the present disclosure.
  • system environment 1600 includes one or more client computing devices 1604 , 1606 , and 1608 that may be used by users to interact with a cloud infrastructure system 1602 that provides cloud services.
  • the client computing devices may be configured to operate a client application such as a web browser, a proprietary client application (e.g., Oracle Forms), or some other application, which may be used by a user of the client computing device to interact with cloud infrastructure system 1602 to use services provided by cloud infrastructure system 1602 .
  • client application such as a web browser, a proprietary client application (e.g., Oracle Forms), or some other application, which may be used by a user of the client computing device to interact with cloud infrastructure system 1602 to use services provided by cloud infrastructure system 1602 .
  • cloud infrastructure system 1602 depicted in the figure may have other components than those depicted. Further, the embodiment shown in the figure is only one example of a cloud infrastructure system that may incorporate an embodiment of the invention. In some other embodiments, cloud infrastructure system 1602 may have more or fewer components than shown in the figure, may combine two or more components, or may have a different configuration or arrangement of components.
  • Client computing devices 1604 , 1606 , and 1608 may be devices similar to those described above for 1502 , 1504 , 1506 , and 1508 .
  • exemplary system environment 1600 is shown with three client computing devices, any number of client computing devices may be supported. Other devices such as devices with sensors, etc. may interact with cloud infrastructure system 1602 .
  • Network(s) 1610 may facilitate communications and exchange of data between clients 1604 , 1606 , and 1608 and cloud infrastructure system 1602 .
  • Each 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 those described above for network(s) 1510 .
  • Cloud infrastructure system 1602 may comprise one or more computers and/or servers that may include those described above for server 1512 .
  • a specific instantiation of a service provided by cloud infrastructure system is referred to herein as a “service instance.”
  • any service made available to a user via a communication network, such as the Internet, from a cloud service provider's system is referred to as a “cloud service.”
  • a cloud service provider's system may host an application, and a user may, via a communication network such as the Internet, on demand, order and use the application.
  • a service in a computer network cloud infrastructure may include protected computer network access to storage, a hosted database, a hosted web server, a software application, or other service provided by a cloud vendor to a user, or as otherwise known in the art.
  • a service can include password-protected access to remote storage on the cloud through the Internet.
  • a service can include a web service-based hosted relational database and a script-language middleware engine for private use by a networked developer.
  • a service can include access to an email software application hosted on a cloud vendor's web site.
  • cloud infrastructure system 1602 may include a suite of applications, middleware, and database service offerings that are delivered to a customer in a self-service, subscription-based, elastically scalable, reliable, highly available, and secure manner.
  • An example of such a cloud infrastructure system is the Oracle Public Cloud provided by the present assignee.
  • cloud infrastructure system 1602 may be adapted to automatically provision, manage and track a customer's subscription to services offered by cloud infrastructure system 1602 .
  • Cloud infrastructure system 1602 may provide the cloud services via different deployment models. For example, services may be provided under a public cloud model in which cloud infrastructure system 1602 is owned by an organization selling cloud services (e.g., owned by Oracle) and the services are made available to the general public or different industry enterprises. As another example, services may be provided under a private cloud model in which cloud infrastructure system 1602 is operated solely for a single organization and may provide services for one or more entities within the organization. The cloud services may also be provided under a community cloud model in which cloud infrastructure system 1602 and the services provided by cloud infrastructure system 1602 are shared by several organizations in a related community. The cloud services may also be provided under a hybrid cloud model, which is a combination of two or more different models.
  • the services provided by cloud infrastructure system 1602 may include one or more services provided under Software as a Service (SaaS) category, Platform as a Service (PaaS) category, Infrastructure as a Service (IaaS) category, or other categories of services including hybrid services.
  • SaaS Software as a Service
  • PaaS Platform as a Service
  • IaaS Infrastructure as a Service
  • a customer via a subscription order, may order one or more services provided by cloud infrastructure system 1602 .
  • Cloud infrastructure system 1602 then performs processing to provide the services in the customer's subscription order.
  • the services provided by cloud infrastructure system 1602 may include, without limitation, application services, platform services and infrastructure services.
  • application services may be provided by the cloud infrastructure system via a SaaS platform.
  • the SaaS platform may be configured to provide cloud services that fall under the SaaS category.
  • the SaaS platform may provide capabilities to build and deliver a suite of on-demand applications on an integrated development and deployment platform.
  • the SaaS platform may manage and control the underlying software and infrastructure for providing the SaaS services.
  • customers can utilize applications executing on the cloud infrastructure system.
  • Customers can acquire the application services without the need for customers to purchase separate licenses and support.
  • Various different SaaS services may be provided. Examples include, without limitation, services that provide solutions for sales performance management, enterprise integration, and business flexibility for large organizations.
  • platform services provided by the cloud infrastructure system may include database cloud services, middleware cloud services (e.g., Oracle Fusion Middleware services), and Java cloud services.
  • database cloud services may support shared service deployment models that enable organizations to pool database resources and offer customers a Database as a Service in the form of a database cloud.
  • middleware cloud services may provide a platform for customers to develop and deploy various business applications
  • Java cloud services may provide a platform for customers to deploy Java applications, in the cloud infrastructure system.
  • resources in cloud infrastructure system 1602 may be shared by multiple users and dynamically re-allocated per demand. Additionally, resources may be allocated to users in different time zones. For example, cloud infrastructure system 1630 may enable a first set of users in a first time zone to utilize resources of the cloud infrastructure system for a specified number of hours and then enable the re-allocation of the same resources to another set of users located in a different time zone, thereby maximizing the utilization of resources.
  • a number of internal shared services 1632 may be provided that are shared by different components or modules of cloud infrastructure system 1602 and by the services provided by cloud infrastructure system 1602 .
  • These internal shared services may include, without limitation, a security and identity service, an integration service, an enterprise repository service, an enterprise manager service, a virus scanning and white list service, a high availability, backup and recovery service, service for enabling cloud support, an email service, a notification service, a file transfer service, and the like.
  • cloud infrastructure system 1602 may provide comprehensive management of cloud services (e.g., SaaS, PaaS, and IaaS services) in the cloud infrastructure system.
  • cloud management functionality may include capabilities for provisioning, managing and tracking a customer's subscription received by cloud infrastructure system 1602 , and the like.
  • cloud management functionality may be provided by one or more modules, such as an order management module 1620 , an order orchestration module 1622 , an order provisioning module 1624 , an order management and monitoring module 1626 , and an identity management module 1628 .
  • modules may include or be provided using one or more computers and/or servers, which may be general purpose computers, specialized server computers, server farms, server clusters, or any other appropriate arrangement and/or combination.
  • a customer using a client device may interact with cloud infrastructure system 1602 by requesting one or more services provided by cloud infrastructure system 1602 and placing an order for a subscription for one or more services offered by cloud infrastructure system 1602 .
  • the customer may access a cloud User Interface (UI), cloud UI 1612 , cloud UI 1614 and/or cloud UI 1616 and place a subscription order via these UIs.
  • UI cloud User Interface
  • the order information received by cloud infrastructure system 1602 in response to the customer placing an order may include information identifying the customer and one or more services offered by the cloud infrastructure system 1602 that the customer intends to subscribe to.
  • the order information is received via the cloud UIs, 1612 , 1614 and/or 1616 .
  • Order database 1618 can be one of several databases operated by cloud infrastructure system 1618 and operated in conjunction with other system elements.
  • order management module 1620 may be configured to perform billing and accounting functions related to the order, such as verifying the order, and upon verification, booking the order.
  • Order orchestration module 1622 may utilize the order information to orchestrate the provisioning of services and resources for the order placed by the customer. In some instances, order orchestration module 1622 may orchestrate the provisioning of resources to support the subscribed services using the services of order provisioning module 1624 .
  • a notification of the provided service may be sent to customers on client devices 1604 , 1606 and/or 1608 by order provisioning module 1624 of cloud infrastructure system 1602 .
  • order management and monitoring module 1626 may be configured to collect usage statistics for the services in the subscription order, such as the amount of storage used, the amount data transferred, the number of users, and the amount of system up time and system down time.
  • cloud infrastructure system 1600 may include an identity management module 1628 .
  • Identity management module 1628 may be configured to provide identity services, such as access management and authorization services in cloud infrastructure system 1600 .
  • identity management module 1628 may control information about customers who wish to utilize the services provided by cloud infrastructure system 1602 . Such information can include information that authenticates the identities of such customers and information that describes which actions those customers are authorized to perform relative to various system resources (e.g., files, directories, applications, communication ports, memory segments, etc.)
  • Identity management module 1628 may also include the management of descriptive information about each customer and about how and by whom that descriptive information can be accessed and modified.
  • FIG. 17 illustrates an exemplary computer system 1700 , in which various embodiments of the present invention may be implemented.
  • the system 1700 may be used to implement any of the computer systems described above.
  • computer system 1700 includes a processing unit 1704 that communicates with a number of peripheral subsystems via a bus subsystem 1702 .
  • peripheral subsystems may include a processing acceleration unit 1706 , an I/O subsystem 1708 , a storage subsystem 1718 and a communications subsystem 1724 .
  • Storage subsystem 1718 includes tangible computer-readable storage media 1722 and a system memory 1710 .
  • Bus subsystem 1702 provides a mechanism for letting the various components and subsystems of computer system 1700 communicate with each other as intended.
  • Bus subsystem 1702 is shown schematically as a single bus, alternative embodiments of the bus subsystem may utilize multiple buses.
  • Bus subsystem 1702 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.
  • bus architectures may include an Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus, which can be implemented as a Mezzanine bus manufactured to the IEEE P1386.1 standard.
  • ISA Industry Standard Architecture
  • MCA Micro Channel Architecture
  • EISA Enhanced ISA
  • VESA Video Electronics Standards Association
  • PCI Peripheral Component Interconnect
  • Processing unit 1704 which can be implemented as one or more integrated circuits (e.g., a conventional microprocessor or microcontroller), controls the operation of computer system 1700 .
  • processors may be included in processing unit 1704 . These processors may include single core or multicore processors.
  • processing unit 1704 may be implemented as one or more independent processing units 1732 and/or 1734 with single or multicore processors included in each processing unit.
  • processing unit 1704 may also be implemented as a quad-core processing unit formed by integrating two dual-core processors into a single chip.
  • processing unit 1704 can 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) 1704 and/or in storage subsystem 1718 . Through suitable programming, processor(s) 1704 can provide various functionalities described above.
  • Computer system 1700 may additionally include a processing acceleration unit 1706 , which can include a digital signal processor (DSP), a special-purpose processor, and/or the like.
  • DSP digital signal processor
  • I/O subsystem 1708 may include user interface input devices and user interface output devices.
  • User interface input devices may include a keyboard, pointing devices such as a mouse or trackball, a touchpad or touch screen incorporated into a display, a scroll wheel, a click wheel, a dial, a button, a switch, a keypad, audio input devices with voice command recognition systems, microphones, and other types of input devices.
  • User interface input devices may include, for example, motion sensing and/or gesture recognition devices such as the Microsoft Kinect® motion sensor that enables users to control and interact with an input device, such as the Microsoft Xbox® 360 game controller, through a natural user interface using gestures and spoken commands.
  • User interface input devices may also include eye gesture recognition devices such as the Google Glass® blink detector that detects eye activity (e.g., ‘blinking’ while taking pictures and/or making a menu selection) from users and transforms the eye gestures as input into an input device (e.g., Google Glass®). Additionally, user interface input devices may include voice recognition sensing devices that enable users to interact with voice recognition systems (e.g., Siri® navigator), through voice commands.
  • eye gesture recognition devices such as the Google Glass® blink detector that detects eye activity (e.g., ‘blinking’ while taking pictures and/or making a menu selection) from users and transforms the eye gestures as input into an input device (e.g., Google Glass®).
  • user interface input devices may include voice recognition sensing devices that enable users to interact with voice recognition systems (e.g., Siri® navigator), through voice commands.
  • voice recognition systems e.g., Siri® navigator
  • User interface input devices may also include, without limitation, three dimensional (3D) mice, joysticks or pointing sticks, gamepads and graphic tablets, and audio/visual devices such as speakers, digital cameras, digital camcorders, portable media players, webcams, image scanners, fingerprint scanners, barcode reader 3D scanners, 3D printers, laser rangefinders, and eye gaze tracking devices.
  • user interface input devices may include, for example, medical imaging input devices such as computed tomography, magnetic resonance imaging, position emission tomography, medical ultrasonography devices.
  • User interface input devices may also include, for example, audio input devices such as MIDI keyboards, digital musical instruments and the like.
  • User interface output devices may include a display subsystem, indicator lights, or non-visual displays such as audio output devices, etc.
  • the display subsystem may be a cathode ray tube (CRT), a flat-panel device, such as that using a liquid crystal display (LCD) or plasma display, a projection device, a touch screen, and the like.
  • CTR cathode ray tube
  • LCD liquid crystal display
  • plasma display a projection device
  • touch screen a touch screen
  • output device is intended to include all possible types of devices and mechanisms for outputting information from computer system 1700 to a user or other computer.
  • user interface output devices may include, without limitation, a variety of display devices that visually convey text, graphics and audio/video information such as monitors, printers, speakers, headphones, automotive navigation systems, plotters, voice output devices, and modems.
  • Computer system 1700 may comprise a storage subsystem 1718 that comprises software elements, shown as being currently located within a system memory 1710 .
  • System memory 1710 may store program instructions that are loadable and executable on processing unit 1704 , as well as data generated during the execution of these programs.
  • system memory 1710 may be volatile (such as random access memory (RAM)) and/or non-volatile (such as read-only memory (ROM), flash memory, etc.)
  • RAM random access memory
  • ROM read-only memory
  • system memory 1710 may include multiple different types of memory, such as static random access memory (SRAM) or dynamic random access memory (DRAM).
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • BIOS basic input/output system
  • BIOS basic input/output system
  • BIOS basic routines that help to transfer information between elements within computer system 1700 , such as during start-up, may typically be stored in the ROM.
  • system memory 1710 also illustrates application programs 1712 , which may include client applications, Web browsers, mid-tier applications, relational database management systems (RDBMS), etc., program data 1714 , and an operating system 1716 .
  • operating system 1716 may include various versions of Microsoft Windows®, Apple Macintosh®, and/or Linux operating systems, a variety of commercially-available UNIX® or UNIX-like operating systems (including without limitation the variety of GNU/Linux operating systems, the Google Chrome® OS, and the like) and/or mobile operating systems such as iOS, Windows® Phone, Android® OS, BlackBerry® 10 OS, and Palm® OS operating systems.
  • Storage subsystem 1700 may also include a computer-readable storage media reader 1720 that can further be connected to computer-readable storage media 1722 .
  • computer-readable storage media 1722 may 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.
  • Computer-readable storage media 1722 may also include, solid-state drives (SSD) based on non-volatile memory such as flash-memory based SSDs, enterprise flash drives, solid state ROM, and the like, SSDs based on volatile memory such as solid state RAM, dynamic RAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, and hybrid SSDs that use a combination of DRAM and flash memory based SSDs.
  • SSD solid-state drives
  • volatile memory such as solid state RAM, dynamic RAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, and hybrid SSDs that use a combination of DRAM and flash memory based SSDs.
  • MRAM magnetoresistive RAM
  • hybrid SSDs that use a combination of DRAM and flash memory based SSDs.
  • the disk drives and their associated computer-readable media may provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for computer system 1700 .
  • communications subsystem 1724 may also receive input communication in the form of structured and/or unstructured data feeds 1726 , event streams 1728 , event updates 1730 , and the like on behalf of one or more users who may use computer system 1700 .
  • Computer system 1700 can be one of various types, including a handheld portable device (e.g., an iPhone® cellular phone, an iPad® computing tablet, a PDA), a wearable device (e.g., a Google Glass® head mounted display), a PC, a workstation, a mainframe, a kiosk, a server rack, or any other data processing system.
  • a handheld portable device e.g., an iPhone® cellular phone, an iPad® computing tablet, a PDA
  • a wearable device e.g., a Google Glass® head mounted display
  • PC personal computer
  • workstation e.g., a workstation
  • mainframe e.g., a mainframe
  • kiosk e.g., a server rack
  • server rack e.g., a server rack, or any other data processing system.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Computer Hardware Design (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mathematical Physics (AREA)
  • Health & Medical Sciences (AREA)
  • Computer Security & Cryptography (AREA)
  • General Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • Stored Programmes (AREA)
  • Debugging And Monitoring (AREA)
US16/147,334 2017-09-30 2018-09-28 API registry in a container platform for automatically generating client code libraries Active US10599500B2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US16/147,334 US10599500B2 (en) 2017-09-30 2018-09-28 API registry in a container platform for automatically generating client code libraries
US16/826,629 US11132241B2 (en) 2017-09-30 2020-03-23 API registry in a container platform for automatically generating client code libraries
US17/485,689 US11755393B2 (en) 2017-09-30 2021-09-27 API registry in a container platform for automatically generating client code libraries

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762566351P 2017-09-30 2017-09-30
US16/147,334 US10599500B2 (en) 2017-09-30 2018-09-28 API registry in a container platform for automatically generating client code libraries

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/826,629 Continuation US11132241B2 (en) 2017-09-30 2020-03-23 API registry in a container platform for automatically generating client code libraries

Publications (2)

Publication Number Publication Date
US20190102239A1 US20190102239A1 (en) 2019-04-04
US10599500B2 true US10599500B2 (en) 2020-03-24

Family

ID=63963482

Family Applications (8)

Application Number Title Priority Date Filing Date
US16/147,334 Active US10599500B2 (en) 2017-09-30 2018-09-28 API registry in a container platform for automatically generating client code libraries
US16/147,305 Active US10599499B2 (en) 2017-09-30 2018-09-28 API registry in a container platform providing property-based API functionality
US16/147,332 Active US12450110B2 (en) 2017-09-30 2018-09-28 Optimizing redeployment of functions and services across multiple container platforms and installations
US16/147,343 Active 2039-01-26 US10824489B2 (en) 2017-09-30 2018-09-28 Dynamic node rebalancing between container platforms
US16/147,351 Active 2039-01-22 US10838788B2 (en) 2017-09-30 2018-09-28 Real-time debugging instances in a deployed container platform
US16/826,629 Active 2038-10-03 US11132241B2 (en) 2017-09-30 2020-03-23 API registry in a container platform for automatically generating client code libraries
US16/827,090 Active 2039-09-13 US11681573B2 (en) 2017-09-30 2020-03-23 API registry in a container platform providing property-based API functionality
US17/485,689 Active 2038-12-17 US11755393B2 (en) 2017-09-30 2021-09-27 API registry in a container platform for automatically generating client code libraries

Family Applications After (7)

Application Number Title Priority Date Filing Date
US16/147,305 Active US10599499B2 (en) 2017-09-30 2018-09-28 API registry in a container platform providing property-based API functionality
US16/147,332 Active US12450110B2 (en) 2017-09-30 2018-09-28 Optimizing redeployment of functions and services across multiple container platforms and installations
US16/147,343 Active 2039-01-26 US10824489B2 (en) 2017-09-30 2018-09-28 Dynamic node rebalancing between container platforms
US16/147,351 Active 2039-01-22 US10838788B2 (en) 2017-09-30 2018-09-28 Real-time debugging instances in a deployed container platform
US16/826,629 Active 2038-10-03 US11132241B2 (en) 2017-09-30 2020-03-23 API registry in a container platform for automatically generating client code libraries
US16/827,090 Active 2039-09-13 US11681573B2 (en) 2017-09-30 2020-03-23 API registry in a container platform providing property-based API functionality
US17/485,689 Active 2038-12-17 US11755393B2 (en) 2017-09-30 2021-09-27 API registry in a container platform for automatically generating client code libraries

Country Status (5)

Country Link
US (8) US10599500B2 (enExample)
EP (5) EP3688595B1 (enExample)
JP (9) JP7203096B2 (enExample)
CN (7) CN111279321B (enExample)
WO (5) WO2019068031A1 (enExample)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10824489B2 (en) 2017-09-30 2020-11-03 Oracle International Corporation Dynamic node rebalancing between container platforms
US11336588B2 (en) 2020-06-26 2022-05-17 Red Hat, Inc. Metadata driven static determination of controller availability
US11456931B1 (en) 2021-04-06 2022-09-27 Amdocs Development Limited System, method and computer program for orchestrating loosely coupled services
US11659027B1 (en) * 2022-01-06 2023-05-23 Vmware, Inc. Multi-network/domain service discovery in a container orchestration platform
US20240031229A1 (en) * 2022-07-20 2024-01-25 Vmware, Inc. Synchronization of logical network configuration between multi-tenant network manager and local network manager

Families Citing this family (238)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8560604B2 (en) 2009-10-08 2013-10-15 Hola Networks Ltd. System and method for providing faster and more efficient data communication
US9225638B2 (en) 2013-05-09 2015-12-29 Vmware, Inc. Method and system for service switching using service tags
US9241044B2 (en) 2013-08-28 2016-01-19 Hola Networks, Ltd. System and method for improving internet communication by using intermediate nodes
US10129077B2 (en) 2014-09-30 2018-11-13 Nicira, Inc. Configuring and operating a XaaS model in a datacenter
US9531590B2 (en) 2014-09-30 2016-12-27 Nicira, Inc. Load balancing across a group of load balancers
US10257095B2 (en) 2014-09-30 2019-04-09 Nicira, Inc. Dynamically adjusting load balancing
US10594743B2 (en) 2015-04-03 2020-03-17 Nicira, Inc. Method, apparatus, and system for implementing a content switch
US11023846B2 (en) 2015-04-24 2021-06-01 United Parcel Service Of America, Inc. Location-based pick up and delivery services
US11057446B2 (en) 2015-05-14 2021-07-06 Bright Data Ltd. System and method for streaming content from multiple servers
US11824863B2 (en) * 2016-11-03 2023-11-21 Nicira, Inc. Performing services on a host
US10447811B2 (en) * 2017-07-18 2019-10-15 Citrix Systems, Inc. Cloud to on-premises debug service routing
EP4648362A2 (en) 2017-08-28 2025-11-12 Bright Data Ltd. Content fetching by selecting tunnel devices
US11947489B2 (en) 2017-09-05 2024-04-02 Robin Systems, Inc. Creating snapshots of a storage volume in a distributed storage system
US10797966B2 (en) 2017-10-29 2020-10-06 Nicira, Inc. Service operation chaining
US12375573B1 (en) 2017-11-27 2025-07-29 Fortinet, Inc. Container event monitoring using kernel space communication
US11792284B1 (en) * 2017-11-27 2023-10-17 Lacework, Inc. Using data transformations for monitoring a cloud compute environment
US12130878B1 (en) 2017-11-27 2024-10-29 Fortinet, Inc. Deduplication of monitored communications data in a cloud environment
US11392363B2 (en) 2018-01-11 2022-07-19 Robin Systems, Inc. Implementing application entrypoints with containers of a bundled application
US11582168B2 (en) 2018-01-11 2023-02-14 Robin Systems, Inc. Fenced clone applications
US11748203B2 (en) * 2018-01-11 2023-09-05 Robin Systems, Inc. Multi-role application orchestration in a distributed storage system
US10805192B2 (en) 2018-03-27 2020-10-13 Nicira, Inc. Detecting failure of layer 2 service using broadcast messages
US11128530B2 (en) 2018-03-29 2021-09-21 Hewlett Packard Enterprise Development Lp Container cluster management
US10812337B2 (en) 2018-06-15 2020-10-20 Vmware, Inc. Hierarchical API for a SDDC
US10942788B2 (en) 2018-06-15 2021-03-09 Vmware, Inc. Policy constraint framework for an sddc
US11023328B2 (en) 2018-07-30 2021-06-01 Robin Systems, Inc. Redo log for append only storage scheme
US11086700B2 (en) 2018-08-24 2021-08-10 Vmware, Inc. Template driven approach to deploy a multi-segmented application in an SDDC
US11595250B2 (en) 2018-09-02 2023-02-28 Vmware, Inc. Service insertion at logical network gateway
US10805154B2 (en) * 2018-10-16 2020-10-13 Hartford Fire Insurance Company Secure configuration management system
US10747556B2 (en) * 2018-10-18 2020-08-18 Sap Se Serverless function as a service (FAAS)
US11036439B2 (en) 2018-10-22 2021-06-15 Robin Systems, Inc. Automated management of bundled applications
US10846078B2 (en) * 2018-11-06 2020-11-24 Sap Se Synchronization of master data across multiple cloud-based systems
US11457080B1 (en) * 2018-11-23 2022-09-27 Amazon Technologies, Inc. Service mesh management
US11243813B2 (en) * 2018-11-28 2022-02-08 International Business Machines Corporation Process as a network service hub
US20200167215A1 (en) * 2018-11-28 2020-05-28 Centurylink Intellectual Property Llc Method and System for Implementing an Application Programming Interface Automation Platform
US10715388B2 (en) * 2018-12-10 2020-07-14 Sap Se Using a container orchestration service for dynamic routing
US11212366B2 (en) 2018-12-11 2021-12-28 Sap Se Kubernetes as a distributed operating system for multitenancy/multiuser
US11381476B2 (en) 2018-12-11 2022-07-05 Sap Se Standardized format for containerized applications
US10700949B1 (en) * 2018-12-13 2020-06-30 Sap Se Stacking of tentant-aware services
CN109743367B (zh) * 2018-12-24 2021-08-17 青岛海信智能商用系统股份有限公司 服务处理方法、装置、电子设备及可读存储介质
US10962946B2 (en) * 2018-12-31 2021-03-30 Johnson Controls Technology Company Building automation system with microservice architecture to support multi-node on-premise bas server
US11018956B2 (en) 2019-01-18 2021-05-25 Fidelity Information Services, Llc Systems and methods for rapid booting and deploying of an enterprise system in a cloud environment
US11038926B2 (en) * 2019-01-23 2021-06-15 Vmware, Inc. System and method for embedding infrastructure security services into management nodes
US10860364B2 (en) * 2019-01-23 2020-12-08 Vmware, Inc. Containerized management services with high availability
US11119804B2 (en) 2019-02-22 2021-09-14 Vmware, Inc. Segregated service and forwarding planes
EP4075304B1 (en) * 2019-02-25 2023-06-28 Bright Data Ltd. System and method for url fetching retry mechanism
US11019157B2 (en) * 2019-03-06 2021-05-25 At&T Intellectual Property I, L.P. Connectionless service and other services for devices using microservices in 5G or other next generation communication systems
US10942855B2 (en) * 2019-03-18 2021-03-09 Microsoft Technology Licensing, Llc Contextual loading based on dynamic context
US11086725B2 (en) 2019-03-25 2021-08-10 Robin Systems, Inc. Orchestration of heterogeneous multi-role applications
EP4428717A3 (en) 2019-04-02 2024-11-27 Bright Data Ltd. Managing a non-direct url fetching service
CN110018962A (zh) * 2019-04-11 2019-07-16 重庆猪八戒知识产权服务有限公司 基于分布式服务框架和注册中心的服务调试方法及系统
US11256434B2 (en) 2019-04-17 2022-02-22 Robin Systems, Inc. Data de-duplication
US11416285B1 (en) * 2019-04-30 2022-08-16 Splunk Inc. Efficient and secure scalable-two-stage data collection
DE102019112485A1 (de) * 2019-05-13 2020-11-19 Eberhard-Karls-Universität Tübingen Verfahren zum selektiven Ausführen eines Containers
US10911558B1 (en) * 2019-05-15 2021-02-02 Pivotal Software, Inc. On-demand network segmentation
WO2020234792A1 (en) * 2019-05-21 2020-11-26 Politecnico Di Milano An fpga-as-a-service system for accelerated serverless computing
CN110162405A (zh) * 2019-05-31 2019-08-23 福建南威软件有限公司 一种自动服务发现与负载均衡的方法及系统
CN110266679B (zh) * 2019-06-14 2023-02-28 腾讯科技(成都)有限公司 容器网络隔离方法及装置
US11681278B2 (en) * 2019-06-19 2023-06-20 Honeywell International Inc. High availability for container based control execution
TW202101322A (zh) * 2019-06-19 2021-01-01 和碩聯合科技股份有限公司 管理軟體服務的方法及伺服器
US11507880B2 (en) * 2019-06-25 2022-11-22 Kyndryl, Inc. Automatic and continuous monitoring and remediation of API integrations
CN112187841B (zh) * 2019-07-02 2022-07-08 北京百度网讯科技有限公司 基于SaaS平台的服务托管方法、装置、电子设备及存储介质
US12019613B2 (en) * 2019-07-18 2024-06-25 EMC IP Holding Company LLC Data integrity and consensuses with blockchain
US11422785B2 (en) * 2019-07-23 2022-08-23 Paypal, Inc. Container orchestration framework
US11411733B1 (en) * 2019-08-08 2022-08-09 Citibank, N.A. Systems and methods for identity and access control
US11226847B2 (en) 2019-08-29 2022-01-18 Robin Systems, Inc. Implementing an application manifest in a node-specific manner using an intent-based orchestrator
US11520650B2 (en) 2019-09-05 2022-12-06 Robin Systems, Inc. Performing root cause analysis in a multi-role application
US11249851B2 (en) 2019-09-05 2022-02-15 Robin Systems, Inc. Creating snapshots of a storage volume in a distributed storage system
US11556321B2 (en) * 2019-09-06 2023-01-17 International Business Machines Corporation Deploying microservices across a service infrastructure
US10972548B2 (en) * 2019-09-09 2021-04-06 International Business Machines Corporation Distributed system deployment
US10965752B1 (en) * 2019-09-13 2021-03-30 Google Llc Live migration of clusters in containerized environments
US11714638B2 (en) * 2019-09-18 2023-08-01 International Business Machines Corporation Availability level-based service management
US11176245B2 (en) * 2019-09-30 2021-11-16 International Business Machines Corporation Protecting workloads in Kubernetes
US11347684B2 (en) 2019-10-04 2022-05-31 Robin Systems, Inc. Rolling back KUBERNETES applications including custom resources
US11113158B2 (en) 2019-10-04 2021-09-07 Robin Systems, Inc. Rolling back kubernetes applications
US11140218B2 (en) 2019-10-30 2021-10-05 Vmware, Inc. Distributed service chain across multiple clouds
US11157304B2 (en) * 2019-11-01 2021-10-26 Dell Products L.P. System for peering container clusters running on different container orchestration systems
CN112783642B (zh) * 2019-11-11 2024-09-13 阿里巴巴集团控股有限公司 容器内逻辑配置方法、设备以及计算机可读介质
US11347491B2 (en) * 2019-11-15 2022-05-31 Mastercard International Incorporated Containerized application deployment
WO2021095943A1 (ko) * 2019-11-15 2021-05-20 대구대학교 산학협력단 서비스 프로파일을 고려한 컨테이너의 배치 방법
US12131197B2 (en) * 2019-11-25 2024-10-29 Kyndryl, Inc. Container load balancing and availability
CN110888714B (zh) * 2019-11-26 2023-06-23 北京京东尚科信息技术有限公司 容器的调度方法、装置和计算机可读存储介质
US11403188B2 (en) 2019-12-04 2022-08-02 Robin Systems, Inc. Operation-level consistency points and rollback
EP3836051A1 (en) * 2019-12-13 2021-06-16 Basf Se Industrial plant optimization
CN111193783B (zh) * 2019-12-19 2022-08-26 新浪网技术(中国)有限公司 一种服务访问的处理方法及装置
CN114846444A (zh) * 2019-12-19 2022-08-02 皇家飞利浦有限公司 基于动态要求的动态个性化平台生成
US11397630B2 (en) 2020-01-02 2022-07-26 Kyndryl, Inc. Fault detection and correction of API endpoints in container orchestration platforms
US11216155B2 (en) * 2020-01-06 2022-01-04 Fmr Llc Systems and methods for data processing
US11223494B2 (en) 2020-01-13 2022-01-11 Vmware, Inc. Service insertion for multicast traffic at boundary
US11659061B2 (en) 2020-01-20 2023-05-23 Vmware, Inc. Method of adjusting service function chains to improve network performance
US11301285B1 (en) * 2020-01-30 2022-04-12 Parallels International Gmbh Methods and systems for seamless virtual machine changing for software applications
CN111615066B (zh) * 2020-02-07 2021-07-16 中国海洋大学 一种基于广播的分布式微服务注册及调用方法
CN111367659B (zh) * 2020-02-24 2022-07-12 苏州浪潮智能科技有限公司 一种Kubernetes中节点的资源管理方法、设备以及介质
US11210205B2 (en) * 2020-02-28 2021-12-28 Sap Se Application debugging
US11409555B2 (en) * 2020-03-12 2022-08-09 At&T Intellectual Property I, L.P. Application deployment in multi-cloud environment
US11762742B2 (en) 2020-03-31 2023-09-19 Honeywell International Inc. Process control system with different hardware architecture controller backup
EP4078901B1 (en) * 2020-04-01 2024-11-27 VMware LLC Auto deploying network elements for heterogeneous compute elements
US11368387B2 (en) 2020-04-06 2022-06-21 Vmware, Inc. Using router as service node through logical service plane
CN111541746B (zh) * 2020-04-09 2022-04-15 哈尔滨工业大学 面向用户需求变化的多版本并存的微服务自适应方法
US11853330B1 (en) * 2020-04-30 2023-12-26 Splunk Inc. Data structure navigator
US11144362B1 (en) * 2020-05-05 2021-10-12 International Business Machines Corporation Container scheduling in a container orchestration system
US11108638B1 (en) 2020-06-08 2021-08-31 Robin Systems, Inc. Health monitoring of automatically deployed and managed network pipelines
US11528186B2 (en) 2020-06-16 2022-12-13 Robin Systems, Inc. Automated initialization of bare metal servers
US11645193B2 (en) * 2020-07-07 2023-05-09 International Business Machines Corporation Heterogeneous services for enabling collaborative logic design and debug in aspect oriented hardware designing
US11501026B2 (en) * 2020-07-13 2022-11-15 Avaya Management L.P. Method to encrypt the data at rest for data residing on Kubernetes persistent volumes
US10901704B1 (en) * 2020-07-19 2021-01-26 Xmodn Security, Llc Computer-aided design, simulation, and code generation for cryptography
CN111858370B (zh) * 2020-07-28 2023-12-26 浪潮云信息技术股份公司 DevOps的实现方法、装置、计算机可读介质
US20220036206A1 (en) * 2020-07-29 2022-02-03 Red Hat, Inc. Containerized distributed rules engine
US11803408B2 (en) 2020-07-29 2023-10-31 Vmware, Inc. Distributed network plugin agents for container networking
US11863352B2 (en) 2020-07-30 2024-01-02 Vmware, Inc. Hierarchical networking for nested container clusters
US11153227B1 (en) 2020-08-05 2021-10-19 International Business Machines Corporation Managing communication between microservices
US11805076B2 (en) * 2020-08-21 2023-10-31 Kyndryl, Inc. Microservice placement in hybrid multi-cloud using graph matching
US12050946B2 (en) 2020-09-21 2024-07-30 International Business Machines Corporation Just in time assembly of transactions
CN111857977B (zh) * 2020-09-21 2020-12-25 腾讯科技（深圳）有限公司 弹性伸缩方法、装置、服务器和存储介质
US11740980B2 (en) 2020-09-22 2023-08-29 Robin Systems, Inc. Managing snapshot metadata following backup
CN112256384B (zh) * 2020-09-22 2023-10-24 杭州指令集智能科技有限公司 基于容器技术的服务集合处理方法、装置和计算机设备
US11989084B2 (en) 2020-09-23 2024-05-21 Honeywell International Inc. Self-healing process control system
CN112130880B (zh) * 2020-09-27 2022-12-02 深圳平安医疗健康科技服务有限公司 微服务的发布方法、装置、计算机设备及存储介质
CN112035220B (zh) * 2020-09-30 2025-02-14 北京百度网讯科技有限公司 开发机操作任务的处理方法、装置、设备以及存储介质
EP3979081B1 (de) 2020-09-30 2023-06-07 Siemens Aktiengesellschaft Verfahren zum testen einer microservice-anwendung
US11743188B2 (en) 2020-10-01 2023-08-29 Robin Systems, Inc. Check-in monitoring for workflows
US11321217B1 (en) * 2020-10-06 2022-05-03 Splunk Inc. Generating metrics values at component levels of a monolithic application and of a microservice of a microservices-based architecture
US11347622B1 (en) 2020-10-06 2022-05-31 Splunk Inc. Generating metrics values for teams of microservices of a microservices-based architecture
US11271895B1 (en) 2020-10-07 2022-03-08 Robin Systems, Inc. Implementing advanced networking capabilities using helm charts
US11456914B2 (en) 2020-10-07 2022-09-27 Robin Systems, Inc. Implementing affinity and anti-affinity with KUBERNETES
US11475078B2 (en) * 2020-10-19 2022-10-18 Clearwater Analytics, Llc Endpoint identifier for application programming interfaces and web services
CN112269738B (zh) * 2020-10-26 2023-04-07 杭州光通天下网络科技有限公司 Ctf靶场调试方法、装置、电子设备及介质
CN112349165A (zh) * 2020-10-29 2021-02-09 国网甘肃省电力公司 基于调控云的电网调度员仿真培训方法、装置及系统
CN112328359B (zh) * 2020-10-30 2022-06-17 烽火通信科技股份有限公司 避免容器集群启动拥塞的调度方法和容器集群管理平台
US11874938B2 (en) 2020-11-03 2024-01-16 Honeywell International Inc. Admittance mechanism
US11750451B2 (en) 2020-11-04 2023-09-05 Robin Systems, Inc. Batch manager for complex workflows
EP4002098B1 (de) * 2020-11-18 2025-12-31 Deutsche Telekom AG Verfahren zur bereitstellung der funktionalität von mehreren mikrodiensten und/oder der funktionalität von mehreren software-containern mittels einer cloud-infrastruktur, system, verwendungssystem, computerprogramm und computerlesbares medium
CN112486495A (zh) * 2020-11-23 2021-03-12 珠海格力电器股份有限公司 一种工业视觉算法部署方法、系统及存储介质
KR102439056B1 (ko) * 2020-11-24 2022-09-01 주식회사 솔박스 노드 레이블링 방법 및 장치
US11748153B2 (en) * 2020-11-25 2023-09-05 International Business Machines Corporation Anticipated containerized infrastructure used in performing cloud migration
CN112328297B (zh) * 2020-11-30 2021-04-20 北京技德系统技术有限公司 一种在Linux上兼容运行的Android系统的升级方法与装置
KR102480731B1 (ko) * 2020-12-09 2022-12-22 대구대학교 산학협력단 클라우드 컴퓨팅의 다중 노드 환경을 위한 배치 스케줄링 장치 및 배치 스케줄링 방법
US11556361B2 (en) 2020-12-09 2023-01-17 Robin Systems, Inc. Monitoring and managing of complex multi-role applications
KR102466231B1 (ko) * 2020-12-09 2022-11-10 대구대학교 산학협력단 오케스트레이터 환경에서의 프로세스 마이그레이션을 위한 컨테이너 관리 장치 및 관리 방법
US11734043B2 (en) 2020-12-15 2023-08-22 Vmware, Inc. Providing stateful services in a scalable manner for machines executing on host computers
US11611625B2 (en) * 2020-12-15 2023-03-21 Vmware, Inc. Providing stateful services in a scalable manner for machines executing on host computers
US20220188089A1 (en) * 2020-12-15 2022-06-16 Baker Hughes Holdings Llc Framework for industrial analytics
CN112579199A (zh) * 2020-12-15 2021-03-30 北京动力机械研究所 基于开放式数据平台的处理方法及装置
JP2022095016A (ja) * 2020-12-16 2022-06-28 株式会社日立製作所 演算装置、共通リソース生成方法
CN112511560B (zh) * 2020-12-21 2021-10-22 北京云思畅想科技有限公司 一种基于服务网格的混合云环境下数据安全保障方法
CN112698970B (zh) * 2020-12-31 2024-07-12 北京千方科技股份有限公司 用于微服务架构的服务调用方法、装置及计算机存储介质
CN112732245B (zh) * 2021-01-11 2025-08-19 苏州众钺科技有限公司 跨平台应用的开发方法、装置及存储介质
US11223522B1 (en) * 2021-01-15 2022-01-11 Dell Products L.P. Context-based intelligent re-initiation of microservices
US11567740B2 (en) * 2021-02-11 2023-01-31 Oracle International Corporation Techniques for building and optimizing contact service centers
AU2022225210A1 (en) * 2021-02-23 2023-09-28 Orchard Holding A system, device, process and method of measuring food, food consumption and food waste
CN112631739A (zh) * 2021-03-09 2021-04-09 北京世纪好未来教育科技有限公司 容器控制方法及装置、介质、计算机设备
US11671401B2 (en) 2021-03-25 2023-06-06 Cisco Technology, Inc. Providing persistent external internet protocol address for extra-cluster services
WO2022203937A1 (en) 2021-03-25 2022-09-29 Cisco Technology, Inc. Providing persistent external internet protocol address for extra-cluster services
US20220309164A1 (en) * 2021-03-29 2022-09-29 International Business Machines Corporation Secure placement of processing elements
CN113067890B (zh) * 2021-04-07 2022-08-19 武汉光庭信息技术股份有限公司 一种适用于智能座舱的动态注册服务方法及智能座舱
CN112802457A (zh) * 2021-04-14 2021-05-14 北京世纪好未来教育科技有限公司 语音识别的方法、装置、设备和存储介质
US11768713B2 (en) 2021-04-19 2023-09-26 Microsoft Technology Licensing, Llc Dynamic relocation of pods to optimize inter-pod networking
US11645055B2 (en) * 2021-04-29 2023-05-09 Sap Se Custom integration flow step for integration service
US12206559B2 (en) * 2021-05-05 2025-01-21 International Business Machines Corporation Adapting microservices to multi-platform deployments
US11797282B2 (en) * 2021-05-06 2023-10-24 Red Hat, Inc. Optimizing services deployment in a cloud computing environment
US12106082B2 (en) 2021-05-20 2024-10-01 International Business Machines Corporation Generative experiments for application deployment in 5G networks
US11606254B2 (en) 2021-06-11 2023-03-14 Vmware, Inc. Automatic configuring of VLAN and overlay logical switches for container secondary interfaces
US11418550B1 (en) * 2021-07-12 2022-08-16 Sap Se Service-mesh session prioritization
CN113821299A (zh) * 2021-07-23 2021-12-21 邢利力 一种多版本控制的微服务开发部署系统
US20230031434A1 (en) * 2021-07-28 2023-02-02 Hewlett-Packard Development Company, L.P. Exclusion registry
IT202100021161A1 (it) * 2021-08-04 2023-02-04 Marco Simoncini Sistema di containerizzazione di workstation aziendali con interfacce utente remote a basso costo
CN113392034B (zh) * 2021-08-17 2021-10-15 北京安普诺信息技术有限公司 Api自发现方法和基于此的测试覆盖率统计方法及装置
US20230058959A1 (en) * 2021-08-19 2023-02-23 Pepperdata, Inc. Systems, methods, and devices for capacity optimization in a cluster system
US11847412B2 (en) * 2021-09-01 2023-12-19 Capital One Services, Llc Enforcing data ownership at gateway registration using natural language processing
US12328296B2 (en) * 2021-09-09 2025-06-10 Beijing Bytedance Network Technology Co., Ltd. Multifunctional application gateway for security and privacy
US12367320B2 (en) * 2021-09-22 2025-07-22 Ridgeline, Inc. Mechanism for real-time identity resolution in a distributed system
US12254020B2 (en) 2021-09-24 2025-03-18 Sap Se Container plugin for legacy on-premise application
US11841731B2 (en) 2021-09-24 2023-12-12 Sap Se Cloud plugin for legacy on-premise application
US12026496B2 (en) 2021-09-24 2024-07-02 Sap Se Cloud upgrade for legacy on-premise application
US12386801B2 (en) 2021-09-24 2025-08-12 Sap Se Cloud application management using instance metadata
US11922163B2 (en) * 2021-09-24 2024-03-05 Sap Se Cloud version management for legacy on-premise application
US12210909B2 (en) 2021-09-29 2025-01-28 Sap Se Autoscaling GPU applications in Kubernetes based on GPU utilization
US11880296B2 (en) * 2021-10-04 2024-01-23 International Business Machines Corporation Generating a test cluster for testing a container orchestration system
US12367067B2 (en) * 2021-10-04 2025-07-22 UiPath, Inc. Cloud migration
US12271758B2 (en) * 2021-10-06 2025-04-08 Sap Se Multi-tenancy interference model for scaling in container orchestration systems
CN113672273B (zh) * 2021-10-21 2022-04-15 阿里云计算有限公司 数据处理方法、系统及设备
CN113709707B (zh) * 2021-10-29 2022-03-15 中兴通讯股份有限公司 服务网格中边车部署的方法、装置、电子设备和存储介质
US11893373B2 (en) * 2021-11-05 2024-02-06 Microsoft Technology Licensing, Llc Exposure and de-duplication of input parameters for complex Helm chart deployment
CN114047931B (zh) * 2021-11-15 2025-03-18 湖南快乐阳光互动娱乐传媒有限公司 一种脚本的上线方法及开发平台
WO2022072953A1 (en) * 2021-11-17 2022-04-07 Innopeak Technology, Inc. Automatic app resource adaptation
CN114090126A (zh) * 2021-11-23 2022-02-25 浩云科技股份有限公司 一种自定义系统变量方法、装置、终端设备及存储介质
US12348507B2 (en) * 2021-11-29 2025-07-01 Salesforce, Inc. Administration of services executing in cloud platform based datacenters for web-based applications
US20230168872A1 (en) * 2021-11-29 2023-06-01 Salesforce.Com, Inc. Generating user interfaces for administration of services executing in cloud platforms
US11907687B2 (en) * 2021-12-03 2024-02-20 Sap Se Re-usable integration component configuration in a microservice based integration service
CN114205342B (zh) * 2021-12-10 2023-05-16 易保网络技术(上海)有限公司 服务调试的路由方法、电子设备及介质
CN114253854B (zh) * 2021-12-21 2024-05-14 四川启睿克科技有限公司 基于多类型设备模拟上报数据的自动化测试方法
US20220121470A1 (en) * 2021-12-23 2022-04-21 Intel Corporation Optimizing deployment and security of microservices
US12231398B2 (en) 2022-01-14 2025-02-18 VMware LLC Per-namespace IP address management method for container networks
DE102022200460A1 (de) * 2022-01-17 2023-07-20 Siemens Aktiengesellschaft Verfahren zur Verteilung von Rechendiensten verteilter Softwareapplikationen auf Rechenknoten eines Rechenknotennetzwerks, Verteileinrichtung und Rechenknotennetzwerk
US12373245B2 (en) * 2022-03-04 2025-07-29 Jpmorgan Chase Bank, N.A. Systems and methods for configuration driven integration of services in business process models agnostic of workflow systems
EP4494314A1 (en) 2022-03-18 2025-01-22 VMware LLC Mapping vlan of container network to logical network in hypervisor to support flexible ipam and routing container traffic
US11915063B2 (en) 2022-04-05 2024-02-27 Red Hat, Inc. Managing a presentation mode for application programming interface functions
CN114706596B (zh) * 2022-04-11 2023-12-01 中国电信股份有限公司 容器部署方法、资源调度方法、装置、介质和电子设备
WO2023201179A1 (en) * 2022-04-12 2023-10-19 Netapp, Inc. Distributed control plane for reformatting communication between a container orchestration platform and a distributed storage architecture
US11775204B1 (en) 2022-04-12 2023-10-03 Netapp, Inc. Distributed control plane for facilitating communication between a container orchestration platform and a distributed storage architecture
CN114938396B (zh) * 2022-05-09 2024-09-10 阿里巴巴（中国）有限公司 服务调用请求的路由方法、创建服务的方法及装置
DE102022111836A1 (de) 2022-05-11 2023-11-16 Cariad Se Verfahren und Kraftfahrzeug-Steuergerät zum Betreiben einer Containervirtualisierung mit Logging-Funktion sowie computerlesbares Speichermedium
US11711315B1 (en) 2022-05-24 2023-07-25 Red Hat, Inc. Dynamic endpoint resources discovery in Kubernetes clusters via stable URI locator for workflow services
EP4293512A1 (de) * 2022-06-14 2023-12-20 Siemens Aktiengesellschaft Verfahren zum bereitstellen einer mehrzahl von anwendungen und kommunikationssystem
KR20230174137A (ko) * 2022-06-20 2023-12-27 삼성전자주식회사 컨테이너 기반 다중 클러스터 환경에서 데이터 동기화를 위한 방법 및 장치
CN115048087A (zh) * 2022-08-15 2022-09-13 江苏博云科技股份有限公司 Kubernetes环境下实现在线IDE工具的方法、设备及存储介质
US12086579B2 (en) 2022-08-31 2024-09-10 Red Hat, Inc. Deriving a container from a package set
US12346246B2 (en) 2022-09-12 2025-07-01 Bank Of America Corporation System and method for dynamic debugging of data in a triage environment integration with use of a virtual assistant graphical user interface
CN115391753B (zh) * 2022-09-13 2025-05-23 中电信数智科技有限公司 一种兼容不同部署环境的软件授权方法和系统
US12210863B2 (en) 2022-09-26 2025-01-28 Dell Products L.P. Automatic canary deployments with analyzing third party libraries
US12175232B2 (en) 2022-09-26 2024-12-24 Dell Products L.P. Automatic canary deployments with static analysis and code instrumentation
US12254306B2 (en) * 2022-09-26 2025-03-18 Dell Products L.P. Automatic canary deployments with dynamically updating call thresholds
CN117857548A (zh) * 2022-09-30 2024-04-09 华为技术有限公司 一种通信方法及装置
US12177124B2 (en) 2022-10-04 2024-12-24 VMware LLC Using CRDs to create externally routable addresses and route records for pods
US12289380B2 (en) * 2022-10-27 2025-04-29 Dell Products L.P. Generation and deployment of custom microservices for orchestration of multiple source services
US11848910B1 (en) 2022-11-11 2023-12-19 Vmware, Inc. Assigning stateful pods fixed IP addresses depending on unique pod identity
US12199833B2 (en) 2022-11-29 2025-01-14 VMware LLC Network controller as a service (NCaaS) to define network policies for third-party container clusters
US12267212B2 (en) 2022-11-29 2025-04-01 VMware LLC Implementing defined service policies in a third-party container cluster
US12261828B2 (en) * 2022-12-08 2025-03-25 International Business Machines Corporation Modifying security of microservices in a chain based on predicted confidential data flow through the microservices
WO2024136908A1 (en) * 2022-12-19 2024-06-27 Rakuten Mobile Usa Llc Micro frontend framework for redeployment of specific chunks of existing application build
US11831511B1 (en) 2023-01-17 2023-11-28 Vmware, Inc. Enforcing network policies in heterogeneous systems
US20240289111A1 (en) * 2023-02-28 2024-08-29 Gm Cruise Holdings Llc Low-disruption maintenance of cluster infrastructure
TWI846382B (zh) * 2023-03-15 2024-06-21 緯創資通股份有限公司 主機及其存取服務的方法
US20240311171A1 (en) * 2023-03-16 2024-09-19 Qualcomm Incorporated Arbitrary destination callback invocation between a trusted execution environment and a virtual machine
CN116149628A (zh) * 2023-03-31 2023-05-23 重庆长安汽车股份有限公司 一种车端服务装配方法、架构、装置、设备及介质
US20240370351A1 (en) * 2023-05-05 2024-11-07 Red Hat, Inc. Automatically retrieving debugging information based on a declarative specification for debugging a software application
WO2024235480A1 (en) * 2023-05-12 2024-11-21 NEC Laboratories Europe GmbH A computer-implemented method and system for operating at least one application in a trusted computing enabled platform and a corresponding application
US20240403032A1 (en) * 2023-06-05 2024-12-05 Dell Products L.P. Physical node optimizer in a containerized application management system
WO2024254734A1 (en) 2023-06-12 2024-12-19 Vmware Information Technology (China) Co., Ltd. Layer 7 network security for container workloads
CN117112074B (zh) * 2023-06-19 2024-03-12 领悦数字信息技术有限公司 将http应用自动转换成无服务器函数的方法、系统和介质
CN116939016B (zh) * 2023-07-17 2025-09-26 北京火山引擎科技有限公司 微服务治理服务控制方法、装置、电子设备及存储介质
US20250028628A1 (en) * 2023-07-21 2025-01-23 VMware LLC Automated debugging of kubernetes application
US12288045B2 (en) 2023-07-25 2025-04-29 Bank Of America Corporation Methods and systems for self-optimizing library functions
US20250077214A1 (en) * 2023-08-29 2025-03-06 Mastercard Technologies Canada ULC Serverless containerization of collaboration applications for automatic installation and version updates
CN117041330B (zh) * 2023-10-10 2023-12-15 三峡高科信息技术有限责任公司 一种基于强化学习的边缘微服务细粒度部署方法及系统
CN117390105B (zh) * 2023-12-11 2024-03-01 中核武汉核电运行技术股份有限公司 一种工业服务开放平台的服务录入方法及系统
US12423187B1 (en) 2024-04-24 2025-09-23 Dell Products L.P. Detecting configuration issues during pre-canary deployment
JP7656756B1 (ja) 2024-05-09 2025-04-03 株式会社大和総研 証券基幹業務システムおよびプログラム
US12393461B1 (en) * 2024-10-16 2025-08-19 Citigroup Inc. Context-aware application provisioning

Citations (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020120685A1 (en) 1999-06-01 2002-08-29 Alok Srivastava System for dynamically invoking remote network services using service descriptions stored in a service registry
US20030204645A1 (en) * 2002-04-09 2003-10-30 Sun Microsystems, Inc. Method, system, and articles of manufacture for providing a servlet container based web service endpoint
US7634759B2 (en) 2004-12-01 2009-12-15 Microsoft Corporation Distributed debugger environment
WO2011010909A1 (en) 2009-07-20 2011-01-27 Mimos Berhad A method and system for an intelligent framework of a service orientated architecture
US8346929B1 (en) 2003-08-18 2013-01-01 Oracle America, Inc. System and method for generating secure Web service architectures using a Web Services security assessment methodology
US8352801B2 (en) 2009-12-24 2013-01-08 At&T Intellectual Property I, L.P. Systems, methods, and apparatus to debug a network application by utilizing a cloned network and an interactive debugging technique
US8701128B2 (en) * 2011-02-14 2014-04-15 General Electric Company Method, system and computer program product for a client application programming interface (API) in a service oriented architecture
US8707171B2 (en) 2009-08-04 2014-04-22 International Business Machines Corporation Service registry policy editing user interface
WO2014145777A1 (en) 2013-03-15 2014-09-18 Servicemesh, Inc. Systems and methods for providing ranked deployment options
US20140324196A1 (en) 2013-04-25 2014-10-30 General Electric Company Real-time debugging systems and methods
US20150269257A1 (en) 2014-03-18 2015-09-24 Axis Ab Finding services in a service-oriented architecture (soa) network
US9201762B1 (en) 2010-04-21 2015-12-01 Marvell International Ltd. Processor implemented systems and methods for reversible debugging using a replicate process system call
US9201759B2 (en) 2013-07-26 2015-12-01 Sap Se Debugging applications in the cloud
US9246987B2 (en) 2012-06-13 2016-01-26 International Business Machines Corporation Service registry for web services
US9274848B2 (en) 2009-12-03 2016-03-01 International Business Machines Corporation Optimizing cloud service delivery within a cloud computing environment
US20160217050A1 (en) 2015-01-28 2016-07-28 Red Hat, Inc. Automated Container Migration in a Platform-as-a-Service System
US9483312B2 (en) 2010-08-16 2016-11-01 International Business Machines Corporation Locating service endpoints from a service registry
US20160378527A1 (en) 2015-06-26 2016-12-29 Vmware, Inc. Cloning a virtual machine from a physical device based on a local snapshot
US20170046146A1 (en) 2015-08-11 2017-02-16 International Business Machines Corporation Autonomously healing microservice-based applications
US9632914B2 (en) 2015-05-21 2017-04-25 International Business Machines Corporation Error diagnostic in a production environment
US20170147319A1 (en) 2015-11-25 2017-05-25 Red Hat, Inc. Active Representation of a Composite Application
WO2017084276A1 (zh) 2015-11-17 2017-05-26 乐视控股（北京）有限公司 用于容器部署的主机调度方法及系统
US20170180346A1 (en) 2015-12-18 2017-06-22 Amazon Technologies, Inc. Software container registry service
US20170220451A1 (en) 2016-01-29 2017-08-03 Ca, Inc. Debugging in-cloud distributed code in live load environment
US10225140B2 (en) * 2017-04-26 2019-03-05 Oracle International Corporation Portable instance provisioning framework for cloud services

Family Cites Families (77)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7401131B2 (en) * 2000-05-22 2008-07-15 Verizon Business Global Llc Method and system for implementing improved containers in a global ecosystem of interrelated services
US7870241B2 (en) 2002-11-27 2011-01-11 International Business Machines Corporation Automated power control policies based on application-specific redundancy characteristics
US7284054B2 (en) 2003-04-11 2007-10-16 Sun Microsystems, Inc. Systems, methods, and articles of manufacture for aligning service containers
US7698398B1 (en) 2003-08-18 2010-04-13 Sun Microsystems, Inc. System and method for generating Web Service architectures using a Web Services structured methodology
US7822826B1 (en) 2003-12-30 2010-10-26 Sap Ag Deployment of a web service
US7500225B2 (en) * 2004-02-10 2009-03-03 Microsoft Corporation SQL server debugging in a distributed database environment
US8200823B1 (en) 2004-03-30 2012-06-12 Oracle America, Inc. Technique for deployment and management of network system management services
JP2007538313A (ja) 2004-04-29 2007-12-27 インターナショナル・ビジネス・マシーンズ・コーポレーション 分散ネットワーキング・アーキテクチャ内にサービスをモデル化し、動的にデプロイするためのシステムおよび方法
US7877735B2 (en) 2004-05-25 2011-01-25 Sap Ag Application cloning
US7702779B1 (en) * 2004-06-30 2010-04-20 Symantec Operating Corporation System and method for metering of application services in utility computing environments
JP2006146434A (ja) * 2004-11-17 2006-06-08 Hitachi Ltd 分散アプリケーションテスト方法及び分散アプリケーションテスト装置
US9009181B2 (en) 2007-08-23 2015-04-14 International Business Machines Corporation Accessing objects in a service registry and repository
US20140201218A1 (en) * 2008-06-19 2014-07-17 Servicemesh, Inc. Systems and methods for providing ranked deployment options
US9459925B2 (en) 2010-06-23 2016-10-04 Twilio, Inc. System and method for managing a computing cluster
US8479211B1 (en) 2010-06-29 2013-07-02 Amazon Technologies, Inc. Dynamic resource commitment management
JP2012037935A (ja) 2010-08-03 2012-02-23 Fujitsu Ltd 情報処理装置
US8862933B2 (en) * 2011-02-09 2014-10-14 Cliqr Technologies, Inc. Apparatus, systems and methods for deployment and management of distributed computing systems and applications
US10225335B2 (en) 2011-02-09 2019-03-05 Cisco Technology, Inc. Apparatus, systems and methods for container based service deployment
CN102681825A (zh) 2011-03-09 2012-09-19 北京航空航天大学 服务运行容器管理系统和方法
US20120271949A1 (en) * 2011-04-20 2012-10-25 International Business Machines Corporation Real-time data analysis for resource provisioning among systems in a networked computing environment
CN102223398B (zh) 2011-05-30 2013-09-11 北京航空航天大学 一种部署在云计算环境中部署服务的方法
US8924542B1 (en) 2011-05-31 2014-12-30 Amazon Technologies, Inc. Methods and apparatus for scalable private services
US9781205B2 (en) 2011-09-12 2017-10-03 Microsoft Technology Licensing, Llc Coordination engine for cloud selection
GB2504491A (en) * 2012-07-30 2014-02-05 Ibm Remote debug service in a cloud environment
US9563480B2 (en) 2012-08-21 2017-02-07 Rackspace Us, Inc. Multi-level cloud computing system
US8825550B2 (en) 2012-08-23 2014-09-02 Amazon Technologies, Inc. Scaling a virtual machine instance
US10419524B2 (en) 2012-09-07 2019-09-17 Oracle International Corporation System and method for workflow orchestration for use with a cloud computing environment
US8938053B2 (en) 2012-10-15 2015-01-20 Twilio, Inc. System and method for triggering on platform usage
US10178154B2 (en) * 2012-10-23 2019-01-08 Telefonaktiebolaget Lm Ericsson (Publ) Method and system for cloud service deployment
JP2014197340A (ja) 2013-03-29 2014-10-16 富士ゼロックス株式会社 分散処理システム及びプログラム
EP3103239B1 (en) 2014-02-07 2023-10-11 Oracle International Corporation Cloud service custom execution environment
US9678731B2 (en) 2014-02-26 2017-06-13 Vmware, Inc. Methods and apparatus to generate a customized application blueprint
US9270553B1 (en) 2014-03-26 2016-02-23 Amazon Technologies, Inc. Dynamic service debugging in a virtual environment
JP6207463B2 (ja) 2014-05-28 2017-10-04 Kddi株式会社 Ｉｔシステムにおけるサーバの性能の抽象化方法および資源管理方法
WO2015197564A1 (en) 2014-06-23 2015-12-30 Getclouder Ltd. Cloud hosting systems featuring scaling and load balancing with containers
CN104125275B (zh) * 2014-07-21 2017-08-25 浪潮电子信息产业股份有限公司 一种基于动态可扩展安全服务总线和引擎容器套件体系的安全服务系统
US10362059B2 (en) 2014-09-24 2019-07-23 Oracle International Corporation Proxy servers within computer subnetworks
US9396091B2 (en) 2014-09-29 2016-07-19 Sap Se End-to end, lifecycle aware, API management
US10230571B2 (en) * 2014-10-30 2019-03-12 Equinix, Inc. Microservice-based application development framework
US9256467B1 (en) 2014-11-11 2016-02-09 Amazon Technologies, Inc. System for managing and scheduling containers
US9672123B2 (en) * 2014-12-31 2017-06-06 Oracle International Corporation Deploying services on application server cloud with high availability
US9775008B2 (en) 2015-01-14 2017-09-26 Kodiak Networks, Inc. System and method for elastic scaling in a push to talk (PTT) platform using user affinity groups
US9930103B2 (en) 2015-04-08 2018-03-27 Amazon Technologies, Inc. Endpoint management system providing an application programming interface proxy service
US9727374B2 (en) * 2015-04-21 2017-08-08 International Business Machines Corporation Temporary virtual machine migration for improved software application warmup
US9515993B1 (en) * 2015-05-13 2016-12-06 International Business Machines Corporation Automated migration planning for moving into a setting of multiple firewalls
US10042697B2 (en) 2015-05-28 2018-08-07 Oracle International Corporation Automatic anomaly detection and resolution system
JP6374845B2 (ja) 2015-08-07 2018-08-15 株式会社日立製作所 計算機システム及びコンテナ管理方法
US9965261B2 (en) 2015-08-18 2018-05-08 International Business Machines Corporation Dependency-based container deployment
JP6387330B2 (ja) 2015-08-21 2018-09-05 日本電信電話株式会社 管理サーバ装置及び管理プログラム
US10623514B2 (en) * 2015-10-13 2020-04-14 Home Box Office, Inc. Resource response expansion
CN106603594B (zh) 2015-10-15 2019-07-09 中国电信股份有限公司 一种分布式服务的管理方法和系统
US10348808B2 (en) * 2015-10-30 2019-07-09 International Business Machines Corporation Hybrid cloud applications
US10002247B2 (en) * 2015-12-18 2018-06-19 Amazon Technologies, Inc. Software container registry container image deployment
US10409657B2 (en) 2016-01-15 2019-09-10 Google Llc Identifiers across application instances
US9733834B1 (en) * 2016-01-28 2017-08-15 Weka.IO Ltd. Congestion mitigation in a distributed storage system
US11388037B2 (en) 2016-02-25 2022-07-12 Open Text Sa Ulc Systems and methods for providing managed services
WO2017152178A1 (en) * 2016-03-04 2017-09-08 Bladelogic, Inc. Provisioning of containers for virtualized applications
US10574584B1 (en) * 2016-03-22 2020-02-25 Amazon Technologies, Inc. Controlling network device capacity
KR102092721B1 (ko) * 2016-03-23 2020-04-23 포그혼 시스템스 인코포레이티드 실시간 데이터플로우 프로그래밍에서 패턴 구동형 반응의 구성
JP6680028B2 (ja) 2016-03-24 2020-04-15 日本電気株式会社 監視システム、監視方法および監視プログラム
US9942354B1 (en) * 2016-03-29 2018-04-10 Amazon Technologies, Inc. Managing service message rates in a computing service environment
CN105959138B (zh) * 2016-04-29 2019-05-17 深圳大数点科技有限公司 基于云计算的微服务动态部署的系统及方法
US10594838B2 (en) * 2016-04-29 2020-03-17 Intuit Inc. Configuration data as code
US10496987B2 (en) 2016-09-13 2019-12-03 Verizon Patent And Licensing Inc. Containerization of network services
US10498625B1 (en) * 2016-10-14 2019-12-03 Amazon Technologies, Inc. Distributed testing service
US10942839B2 (en) * 2016-10-28 2021-03-09 Ingram Micro Inc. System and method for debugging applications on a developer workstation
US10489215B1 (en) * 2016-11-02 2019-11-26 Nutanix, Inc. Long-range distributed resource planning using workload modeling in hyperconverged computing clusters
US20180165177A1 (en) 2016-12-08 2018-06-14 Nutanix, Inc. Debugging distributed web service requests
CN106776212B (zh) 2016-12-09 2020-02-25 中电科华云信息技术有限公司 容器集群部署多进程应用的监管系统及方法
US10574736B2 (en) * 2017-01-09 2020-02-25 International Business Machines Corporation Local microservice development for remote deployment
US10601871B2 (en) * 2017-01-18 2020-03-24 International Business Machines Corporation Reconfiguration of security requirements for deployed components of applications
WO2018177506A1 (en) * 2017-03-28 2018-10-04 Telefonaktiebolaget Lm Ericsson (Publ) Technique for allocating radio resources in a radio access network
US10356214B2 (en) * 2017-03-29 2019-07-16 Ca, Inc. Composing monolithic applications based on multi-container applications
US11038947B2 (en) * 2017-04-21 2021-06-15 Microsoft Technology Licensing, Llc Automated constraint-based deployment of microservices to cloud-based server sets
US11343352B1 (en) * 2017-06-21 2022-05-24 Amazon Technologies, Inc. Customer-facing service for service coordination
US10599500B2 (en) 2017-09-30 2020-03-24 Oracle International Corporation API registry in a container platform for automatically generating client code libraries
US10521246B1 (en) * 2018-06-13 2019-12-31 International Business Machines Corporation Application programming interface endpoint analysis and modification

Patent Citations (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020120685A1 (en) 1999-06-01 2002-08-29 Alok Srivastava System for dynamically invoking remote network services using service descriptions stored in a service registry
US20030204645A1 (en) * 2002-04-09 2003-10-30 Sun Microsystems, Inc. Method, system, and articles of manufacture for providing a servlet container based web service endpoint
US8346929B1 (en) 2003-08-18 2013-01-01 Oracle America, Inc. System and method for generating secure Web service architectures using a Web Services security assessment methodology
US7634759B2 (en) 2004-12-01 2009-12-15 Microsoft Corporation Distributed debugger environment
WO2011010909A1 (en) 2009-07-20 2011-01-27 Mimos Berhad A method and system for an intelligent framework of a service orientated architecture
US8707171B2 (en) 2009-08-04 2014-04-22 International Business Machines Corporation Service registry policy editing user interface
US9274848B2 (en) 2009-12-03 2016-03-01 International Business Machines Corporation Optimizing cloud service delivery within a cloud computing environment
US8352801B2 (en) 2009-12-24 2013-01-08 At&T Intellectual Property I, L.P. Systems, methods, and apparatus to debug a network application by utilizing a cloned network and an interactive debugging technique
US9201762B1 (en) 2010-04-21 2015-12-01 Marvell International Ltd. Processor implemented systems and methods for reversible debugging using a replicate process system call
US9483312B2 (en) 2010-08-16 2016-11-01 International Business Machines Corporation Locating service endpoints from a service registry
US8701128B2 (en) * 2011-02-14 2014-04-15 General Electric Company Method, system and computer program product for a client application programming interface (API) in a service oriented architecture
US9246987B2 (en) 2012-06-13 2016-01-26 International Business Machines Corporation Service registry for web services
WO2014145777A1 (en) 2013-03-15 2014-09-18 Servicemesh, Inc. Systems and methods for providing ranked deployment options
US20140324196A1 (en) 2013-04-25 2014-10-30 General Electric Company Real-time debugging systems and methods
US9201759B2 (en) 2013-07-26 2015-12-01 Sap Se Debugging applications in the cloud
US20150269257A1 (en) 2014-03-18 2015-09-24 Axis Ab Finding services in a service-oriented architecture (soa) network
US20160217050A1 (en) 2015-01-28 2016-07-28 Red Hat, Inc. Automated Container Migration in a Platform-as-a-Service System
US9632914B2 (en) 2015-05-21 2017-04-25 International Business Machines Corporation Error diagnostic in a production environment
US20160378527A1 (en) 2015-06-26 2016-12-29 Vmware, Inc. Cloning a virtual machine from a physical device based on a local snapshot
US20170046146A1 (en) 2015-08-11 2017-02-16 International Business Machines Corporation Autonomously healing microservice-based applications
WO2017084276A1 (zh) 2015-11-17 2017-05-26 乐视控股（北京）有限公司 用于容器部署的主机调度方法及系统
US20170147319A1 (en) 2015-11-25 2017-05-25 Red Hat, Inc. Active Representation of a Composite Application
US20170180346A1 (en) 2015-12-18 2017-06-22 Amazon Technologies, Inc. Software container registry service
US20170220451A1 (en) 2016-01-29 2017-08-03 Ca, Inc. Debugging in-cloud distributed code in live load environment
US10225140B2 (en) * 2017-04-26 2019-03-05 Oracle International Corporation Portable instance provisioning framework for cloud services

Non-Patent Citations (28)

* Cited by examiner, † Cited by third party
Title
"Cloud Endpoints, Develop, deploy and manage APIs on any Google Cloud Backend", Cloud Endpoints-API Management | Google Cloud Platform, Jan. 11, 2018, https://cloud.google.com/endpoints/, 5 pages.
"Compute Resources", Red Hat Openshift, Retrieved from the Internet, https://docs.openshift.com/enterprise/3.1/dev_guide/compute_resources.html, Jun. 20, 2016, pp. 1-5.
"Containers Live Migration Behind the Scene", JELASTIC, Retrieved from the Internet: https://vdocuments.mx/jelastic-containers-live-migration-behind-the-scene.html, Apr. 16, 2017, pp. 1-18.
"Handling Out of Resource Errors", Red Hat Openshift, Retrieved from the Internet: https://docs.openshift.com/container-platform/3.6/admin_guide/out_of_resource_handling.html, Jun. 27, 2017, pp. 1-8.
"Service Registry", retrieved from https://help.sap.com/saphelp_nw73/helpdata/en/D9/0F7E2C1C644992A195D38CFEC1B1F2/frameset.htm, Jan. 9, 2018, 3 pages.
"Swagger (Open API) Specification Code Generator Featuring C# and Razor Templates, Supports C#, Java, Node.js, Typescript, Python and Ruby", AZURE, Retrieved from the Internet: https://web.archive.org/web/20170604204029/https://github.com/Azure/autorest, Jun. 4, 2017, pp. 1-4.
"Cloud Endpoints, Develop, deploy and manage APIs on any Google Cloud Backend", Cloud Endpoints—API Management | Google Cloud Platform, Jan. 11, 2018, https://cloud.google.com/endpoints/, 5 pages.
Abeysinghe; Asanka, "API Registry and Service Registry", The Source, WSO2 Blogs, http://wso2.com/blogs/thesource, Jul. 24, 2014, 4 pages.
Anonymous, Connect and communicate with services in Service Fabric, retrieved from: https://github.com/MicrosoftDocs/azure-docs/blob/9f71dca2fb2b95fc34c15ebdabe37199681dd40/articles/service-fabric/service-fabric-connect-and-communicate-with-services.md, Aug. 23, 2017, 7 pages.
Arora, et al., "Setting budgets for live debugging", Abstract, Aug. 28, 2015, 13 pages.
Cutulescu; Gratian, "Building Backend Applications With Google App Engine, Google Cloud Endpoints, and Android Studio", 3 Pillar Global, https://www.3pillarglobal.com/insights/building-backend-applications-with-google-app-engine-google-cloud-endpoints-and-android-studio, retrieved Jan. 15, 2018, all pages.
Debug a Live App Using Console App, APCERA | Documentation, retrieved Jan. 15, 2018, 1 page.
Gutierrez, et al., Real-Time Debugging in Production with Bluemix Live Sync-Cloud Foundry Live | Altoros, https://www.altoros.com/blog/advanced-real-time-debugging-with-bluemix-live-sync/, Jun. 21, 2017, 13 pages.
Gutierrez, et al., Real-Time Debugging in Production with Bluemix Live Sync—Cloud Foundry Live | Altoros, https://www.altoros.com/blog/advanced-real-time-debugging-with-bluemix-live-sync/, Jun. 21, 2017, 13 pages.
International Application No. PCT/US2018/053612, International Search Report and Written Opinion dated Jan. 28, 2019, 15 pages.
International Application No. PCT/US2018/053618, International Search Report and Written Opinion dated Jan. 16, 2019, 17 pages.
International Application No. PCT/US2018/053620, International Search Report and Written Opinion dated Jan. 23, 2019, 15 pages.
International Application No. PCT/US2018/053626, International Search Report and Written Opinion dated Jan. 31, 2019, 15 pages.
International Application No. PCT/US2018/053628, International Search Report and Written Opinion dated Jan. 10, 2019, 11 pages.
Iturria; Carlos Rodriguez, "Teaching Best Practices to Design, Build, Secure and Monitor APIs", RedThunder.Blog, Retrieved from the Internet: https://redthunder.blog/2017/09/22/teaching-best-practices-to-design-build-secure-and-monitor-apis/#more-7733, Sep. 22, 2017, 22 pages.
Kang et al., "Container and Microservice Driven Design for Cloud Infrastructure DevOps", 2016 IEEE International Conference on Cloud Engineering, Apr. 4, 2016, pp. 202-211.
Kannan et al., Resource Quality of Service in Kubernetes, Retrieved from the Internet: https://github.com/kubernetes/community/blob/ca6e45b508cd1031905ad433803de12bfe72b8b6/contributors/design-proposals/node/resource-qos.md, updated Nov. 22, 2016, 4 pages.
Liu et al., "CIDE: An Integrated Development Environment for Microservices", 2016 IEEE International Conference on Services Computing, Jun. 27, 2016, pp. 808-812.
Numan, Milco, "My First Experience With Oracle Api Platform Cloud Service-Part 1", Syntouch Blog, Retrieved from the Internet: https://www.syntouch.nl/my-first-exper ience-with-oracle-api-platform-cloud-service-part-1/, Jun. 6, 2017, 16 pages.
Numan, Milco, "My First Experience With Oracle Api Platform Cloud Service-Part 2", Blog Retrieved from the Internet: https://www.syntouch.nl/my-first-experience-with-oracle-api-platform-cloud-service-part-2/, Jun. 23, 2017, 16 pages.
Numan, Milco, "My First Experience With Oracle Api Platform Cloud Service—Part 1", Syntouch Blog, Retrieved from the Internet: https://www.syntouch.nl/my-first-exper ience-with-oracle-api-platform-cloud-service-part-1/, Jun. 6, 2017, 16 pages.
Numan, Milco, "My First Experience With Oracle Api Platform Cloud Service—Part 2", Blog Retrieved from the Internet: https://www.syntouch.nl/my-first-experience-with-oracle-api-platform-cloud-service-part-2/, Jun. 23, 2017, 16 pages.
Pellegram, Gilbert, "Running Wordpress in a Kubernetes Cluster", Retrieved from the Internet: https://deliciousbrains.com/running-wordpress-kubernetes-cluster/, Aug. 22, 2017, pp. 1-3.

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11681573B2 (en) 2017-09-30 2023-06-20 Oracle International Corporation API registry in a container platform providing property-based API functionality
US10838788B2 (en) 2017-09-30 2020-11-17 Oracle International Corporation Real-time debugging instances in a deployed container platform
US11132241B2 (en) 2017-09-30 2021-09-28 Oracle International Corporation API registry in a container platform for automatically generating client code libraries
US10824489B2 (en) 2017-09-30 2020-11-03 Oracle International Corporation Dynamic node rebalancing between container platforms
US12450110B2 (en) 2017-09-30 2025-10-21 Oracle International Corporation Optimizing redeployment of functions and services across multiple container platforms and installations
US11755393B2 (en) 2017-09-30 2023-09-12 Oracle International Corporation API registry in a container platform for automatically generating client code libraries
US11336588B2 (en) 2020-06-26 2022-05-17 Red Hat, Inc. Metadata driven static determination of controller availability
US11991094B2 (en) 2020-06-26 2024-05-21 Red Hat, Inc. Metadata driven static determination of controller availability
US11456931B1 (en) 2021-04-06 2022-09-27 Amdocs Development Limited System, method and computer program for orchestrating loosely coupled services
US11659027B1 (en) * 2022-01-06 2023-05-23 Vmware, Inc. Multi-network/domain service discovery in a container orchestration platform
US20230291796A1 (en) * 2022-01-06 2023-09-14 Vmware, Inc. Multi-network/domain service discovery in a container orchestration platform
US12160467B2 (en) * 2022-01-06 2024-12-03 VMware LLC Multi-network/domain service discovery in a container orchestration platform
US20240031229A1 (en) * 2022-07-20 2024-01-25 Vmware, Inc. Synchronization of logical network configuration between multi-tenant network manager and local network manager

Also Published As

Publication number Publication date
US20200226013A1 (en) 2020-07-16
US10824489B2 (en) 2020-11-03
EP3688579A1 (en) 2020-08-05
JP7196164B2 (ja) 2022-12-26
JP2020536316A (ja) 2020-12-10
CN111279309B (zh) 2025-02-07
EP3688592B1 (en) 2024-04-03
WO2019068024A1 (en) 2019-04-04
CN111263933A (zh) 2020-06-09
JP2023027098A (ja) 2023-03-01
CN111279320A (zh) 2020-06-12
JP7774093B2 (ja) 2025-11-20
CN111263933B (zh) 2024-12-10
CN114035975A (zh) 2022-02-11
US11132241B2 (en) 2021-09-28
EP3688594A1 (en) 2020-08-05
EP3688594B1 (en) 2023-10-25
CN111279320B (zh) 2021-09-17
JP2023040001A (ja) 2023-03-22
JP7493450B2 (ja) 2024-05-31
JP7203096B2 (ja) 2023-01-12
JP2023139086A (ja) 2023-10-03
CN111279319A (zh) 2020-06-12
JP2020536321A (ja) 2020-12-10
US10599499B2 (en) 2020-03-24
WO2019068036A1 (en) 2019-04-04
EP3688592A1 (en) 2020-08-05
US11755393B2 (en) 2023-09-12
WO2019068029A1 (en) 2019-04-04
EP3688595B1 (en) 2025-07-02
CN111279321A (zh) 2020-06-12
JP2020536320A (ja) 2020-12-10
CN111279321B (zh) 2021-11-05
JP7481421B2 (ja) 2024-05-10
JP7182618B2 (ja) 2022-12-02
WO2019068031A1 (en) 2019-04-04
US20190102238A1 (en) 2019-04-04
US12450110B2 (en) 2025-10-21
WO2019068037A1 (en) 2019-04-04
US20190102226A1 (en) 2019-04-04
US20200218589A1 (en) 2020-07-09
JP2020536319A (ja) 2020-12-10
CN113641460B (zh) 2025-04-22
US20190102280A1 (en) 2019-04-04
JP7562619B2 (ja) 2024-10-07
JP7777565B2 (ja) 2025-11-28
CN113641460A (zh) 2021-11-12
US10838788B2 (en) 2020-11-17
JP2024105342A (ja) 2024-08-06
US20190102157A1 (en) 2019-04-04
CN111279319B (zh) 2024-12-10
US11681573B2 (en) 2023-06-20
CN114035975B (zh) 2025-11-25
CN111279309A (zh) 2020-06-12
JP7246381B2 (ja) 2023-03-27
EP3688593A1 (en) 2020-08-05
US20190102239A1 (en) 2019-04-04
JP2020536318A (ja) 2020-12-10
EP3688595A1 (en) 2020-08-05
US20220012111A1 (en) 2022-01-13
EP3688593B1 (en) 2022-06-22

Similar Documents

Publication Publication Date Title
US11755393B2 (en) API registry in a container platform for automatically generating client code libraries

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: ORACLE INTERNATIONAL CORPORATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CALDATO, CLAUDIO;SCHOLL, BORIS;REEL/FRAME:047409/0507

Effective date: 20181031

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: PRE-INTERVIEW COMMUNICATION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4