Service-to-service communication and authentication via a central network mesh

JP2023551382A5Active Publication Date: 2024-11-12GENENTECH INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2023527689
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2020-11-10
Filing Date
2021-11-08
Publication Date
2024-11-12
Estimated Expiration
2041-11-08

AI Technical Summary

Technical Problem

Distributed computing environments in healthcare face security and privacy challenges due to data centralization, hindering widespread adoption, as they lack effective mechanisms to control data access and maintain privacy, especially in compliance with regulations like HIPAA and GDPR.

Method used

A network mesh system implements pod-level networking with security rules and keys to manage data access and communication, ensuring secure interactions between services and resources, maintaining control over data storage and access, and adhering to regulatory standards.

Benefits of technology

The system provides secure, compliant, and efficient data access management, enhancing trust in cloud computing for healthcare by ensuring data privacy and security, facilitating seamless communication across distributed environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

The present disclosure relates to techniques for service-to-service communication and authentication over a network mesh. In particular, aspects relate to receiving a service request for a first service in a network mesh and obtaining information related to the first service. The information includes a location of a first pod that encapsulates the first service. The network mesh uses the location of the first pod to obtain security rules specific to the first pod. The network mesh forwards the service request to the first service based on the security rules for the first pod and obtains results of the service request from the first service. The results include sub-results obtained from the second service according to the security rules for the first pod that encapsulate the first service and the security rules for a second pod that encapsulate the second service.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Priority Claim This application claims the benefit and priority of U.S. Provisional Patent Application No. 63 / 111,997, filed on November 10, 2020, which is hereby incorporated by reference in its entirety for all purposes.

[0002] The present disclosure relates to digital and personal healthcare, and more particularly to techniques for service - to - service communication and authentication via a centralized network mesh in a distributed computing environment.

Background Art

[0003] In healthcare, data-driven technology solutions are being developed for personalized healthcare while reducing costs. As the healthcare landscape shifts to on-demand deployment systems for personalized medical services and solutions, healthcare providers are seeking help from developers to innovate solutions more quickly by automating and streamlining software deployment and service management processes. To support healthcare providers and services, developers have turned to distributed computing environments (e.g., cloud computing) as a healthcare information technology infrastructure standard. Cloud computing offers many advantages, including flexibility, cost and energy savings, resource sharing, and rapid deployment. For example, cloud computing can provide the complex infrastructure needed to support software deployment and service management processes within various service models (e.g., Analytics as a Service (AaaS)), which can help facilitate communication, collaboration, and coordination between different healthcare providers. Cloud computing can also help the healthcare industry deliver more value for money. For example, cloud computing can provide fast, flexible, scalable, and cost-effective infrastructure and applications. Cloud computing can also help store, manage, protect, share, and archive electronic health records (EHRs), laboratory information systems, drug information systems, and medical images.

[0004] While distributed computing environments such as cloud computing offer numerous benefits to healthcare providers, they function differently from legacy storage or information sharing solutions and therefore present unique privacy and security challenges. The centralization of data in the cloud raises many security and privacy concerns for individuals and healthcare providers. This centralization provides attackers with a one-stop shop for stealing data, intercepting data in transit, and transferring ownership of data to cloud service providers. Thus, individuals and healthcare providers lose some control over their sensitive data. Consequently, security, privacy, efficiency, and scalability concerns are hindering the widespread adoption of cloud technologies. For example, because users access data via internet connections, compliance with government regulations (e.g., the Healthcare Portability and Accountability Act (HIPAA), Good Practice Quality Guidelines and Regulations (GxP), and the General Data Protection Regulation (GDPR)) becomes a unique challenge for healthcare providers considering cloud solutions to support their software deployment and service management processes. Therefore, advancements are needed in compliant software deployment platforms built to ensure the confidentiality, availability, and integrity of protected healthcare information. [Overview of the project]

[0005] In some embodiments, the network mesh receives a service request for a first service; the network mesh retrieves information related to the first service from a cache or service registry, the information including the identification of a first pod containing the first service and the location of the first pod in a first distributed computing environment; the network mesh uses the location of the first pod to retrieve security rules for the first pod, the security rules defining (i) a unique address identifier for the first service and (ii) services that the first service is permitted to communicate with and access; the network mesh uses the unique address identifier for the first service to forward a service request to the first service; and the network mesh receives an access request from the first service to communicate with and access a second service. This involves receiving an access request in which the access request includes a security key specific to the second service; the network mesh retrieving information related to the second service from a cache or service registry, the information including the identification of the second pod containing the second service and the location of the second pod in the first or second distributed computing environment; the network mesh using the location of the second pod to retrieve security rules for the second pod, the security rules defining (i) a unique address identifier for the second service, and (ii) the services that the second service is permitted to communicate with and access; and the network mesh using the unique address identifier for the second service to forward the access request from the first service to the second service based on the security rules for the first pod and the security rules for the second pod.A computer implementation method is provided, which includes receiving the final result of a service request from a first service via a network mesh, wherein the final result includes sub-results obtained from a second service, and outputting the final result of the service request via the network mesh.

[0006] In some embodiments, obtaining the information relating to the first service or the information relating to the second service includes determining whether the information relating to the first service or the second service is available from a cache; if the information relating to the first service or the second service is available from a cache, obtaining the information relating to the first service or the second service from a cache; if the information relating to the first service or the second service is not available from a cache, obtaining the information relating to the first service or the second service from a registry; and, in response to obtaining the information relating to the first service or the second service from a registry, storing the information relating to the first service or the second service in a cache for subsequent requests.

[0007] In some embodiments, the security key is retrieved from the vault by a first service, which embeds the security key in the access request.

[0008] In some embodiments, an access request from a first service further includes a request for a second service to perform one or more actions on behalf of the first service and / or to obtain the service.

[0009] In some embodiments, the second service performs one or more operations on behalf of the first service and / or retrieves the service, and generates sub-results based on the performance of one or more operations and / or the retrieval of the service.

[0010] In some embodiments, the second service verifies the security key before performing one or more operations and / or before obtaining the service on behalf of the first service.

[0011] In some embodiments, the second pod is located in a second distributed computing environment that is different from the first distributed computing environment.

[0012] In some embodiments, security rules for a first pod further define (i) the number of instances available for the first service, and (ii) which instances are available to process a service request, and forwarding a service request to the first service includes determining which instances are available to process the service request based on the security rules for the first pod, and forwarding the service request to at least one of the instances of the first service.

[0013] In some embodiments, forwarding an access request from a first service to a second service includes determining whether security rules for a first pod define the second service as a service that the first service is permitted to communicate with and access; determining whether security rules for a second pod define the first service as a service that the second service is permitted to receive communications with and access; and forwarding an access request from the first service to the second service if the second service is a service that the first service is permitted to communicate with and access; and the first service is a service that the second service is permitted to receive communications with and access.

[0014] In some embodiments, security rules for a second pod further define (i) the number of instances available for the second service, and (ii) which instances are available to process access requests, and forwarding an access request from the first service to the second service further includes determining which instances are available to process the access request based on the security rules for the second pod, and forwarding the access request to at least one of the instances of the second service.

[0015] In some embodiments, a first service includes one or more programs deployed on one or more clusters packaged as a first container or a first set of containers on a first distributed computing environment, wherein the first container or first set of containers is packaged as a first pod, which is a higher-level structure representing one or more programs running on one or more clusters; and a second service includes one or more programs deployed on one or more clusters packaged as a second container or a second set of containers on a first or second distributed computing environment, wherein the second container or second set of containers is packaged as a second pod, which is a higher-level structure representing one or more programs running on one or more clusters.

[0016] Some embodiments of this disclosure include a system comprising one or more data processors. In some embodiments, the system includes a non-temporary, machine-readable storage medium containing instructions that, when executed on one or more data processors, cause one or more data processors to execute some or all of one or more of the methods and / or some or all of one or more processes disclosed herein. Some embodiments of this disclosure include a computer program product tangibly embodied in a non-temporary, machine-readable storage medium containing instructions configured to cause one or more data processors to execute some or all of one or more of the methods and / or some or all of one or more processes disclosed herein.

[0017] The terms and expressions used are for illustrative purposes only, not limitation, and in using such terms and expressions, there is no intention to exclude any equivalent or part of any of the features shown and described, however it should be recognized that various modifications are possible within the scope of the invention described in the claims. Accordingly, although the invention described in the claims is specifically disclosed by embodiments and optional features, modifications and variations of the concepts disclosed herein may be relied upon by those skilled in the art, and it should be understood that such modifications and variations are considered to be within the scope of the invention as defined by the appended claims. [Brief explanation of the drawing]

[0018] This disclosure will be explained in conjunction with the following attached drawings.

[0019] [Figure 1] This diagram illustrates a digital health platform for providing data-driven technology solutions across various embodiments.

[0020] [Figure 2] This shows diagrams of security systems in various embodiments.

[0021] [Figure 3] A swimlane diagram showing a process for inter-service communication and authentication in a digital health platform according to various embodiments is shown.

[0022] [Figure 4] A flowchart showing a process for inter-service communication and authentication via a centralized network mesh environment according to various embodiments is shown.

[0023] In the accompanying drawings, similar components and / or features can have the same reference labels. Further, various components of the same type can be distinguished by following a dash after the reference label and by a second label that distinguishes similar components. Where only the first reference label is used herein, the description is applicable to any of the similar components having the same first reference label regardless of the second reference label.

DETAILED DESCRIPTION OF THE INVENTION

[0024] I. Overview This disclosure describes techniques for inter-service communication and authentication via a centralized network mesh in a distributed computing environment. More specifically, embodiments of this disclosure provide a network mesh that enables pod-level networking that allows services to communicate securely with each other across multiple types of distributed computing environments. The network mesh and pod-level networking maintain the separation between services and resources so that it is easier to maintain control over where data is stored, who can access which data, and which resources a service or user can consume at a given time, and to ensure that the correct services and resources always have the correct access regardless of where the service or resource is executed or stored.

[0025] Cloud computing presents opportunities and challenges. Similar to many other information technology solutions, the cloud has various security issues and concerns. Since cloud computing typically operates in an open and shared environment, it is often vulnerable to data loss, theft, and malicious attacks. Weak cloud security is one of the important issues hindering the full adoption of cloud computing in the healthcare industry. Healthcare workers have many reasons not to trust cloud computing. For example, healthcare workers cannot freely control their medical records. Organizations and cloud providers usually store their data in different data centers located in different geographical locations. This represents an advantage as data storage on the cloud becomes redundant and in case of force majeure, different data centers can help with disaster recovery. On the other hand, this same advantage can pose security challenges as data stored in different locations is more prone to theft and loss. Additionally, data stored in different locations and its security are governed by various international, regional, and local regulations. Generally, there are many security risks associated with the use of cloud computing. For example, failure to separate virtual users, ID theft, privilege abuse, and inadequate encryption are some of these security risks.

[0026] To address these limitations and issues, the technologies for inter-service communication and authentication in this disclosure utilize pod-level networking governed by communication rules and security keys. In digital and personal healthcare environments, there are typically multiple partners interacting with each other, and these interactions need to be controlled in a secure manner to maintain isolation and traceability between services and resources. A service is any service that may be provided by one or more partners (e.g., healthcare-related services such as data analytics or software as a medical device). Resources are generally hardware and software resources that support a service (e.g., memory and processing units). However, it should be understood that in specific examples, resources may also include data, algorithms, models, etc. (e.g., healthcare-related data stored in a data store). To control these interactions in a secure manner, pod-level security rules are provided that define which services are permitted to communicate with each other and which resources those services are permitted to access. Furthermore, security keys (e.g., public / private key pairs) are provided that enable services to access other services or resources. This two-tier approach is facilitated by a centralized network mesh that has access to the pod-level security rules and location of each service on one or more distributed computing environments, in order to maintain isolation and traceability between services and resources. For example, when a service call is received by the network mesh, the network mesh routes the call to the appropriate service based on information about the pod-level security rules and the service's location, and the service can perform various actions to provide the service by accessing other services and resources through the network mesh using one or more security keys and proxy calls.

[0027] One exemplary embodiment of the present disclosure relates to a method comprising, in a network mesh, receiving a service request from a user for a first service, and the network mesh retrieving information related to the first service from a cache or service registry. The information includes the identification of a first pod containing the first service and the location of the first pod in a first distributed computing environment. The method further comprises, in a network mesh, retrieving security rules for the first pod using the location of the first pod. The security rules define (i) a unique address identifier for the first service, and (ii) services that the first service is permitted to communicate with and access. The method further comprises, in a network mesh, forwarding a service request to the first service using the unique address identifier for the first service, and the network mesh receiving an access request from the first service to communicate with and access a second service. The access request includes a security key specific to the second service. The method further comprises, in a network mesh, retrieving information related to the second service from a cache or service registry. The information includes the identification of the second pod containing the second service and the location of the second pod within the first or second distributed computing environment. The method further includes using the location of the second pod to obtain security rules for the second pod using a network mesh. The security rules define (i) a unique address identifier for the second service, and (ii) the services that the second service is permitted to communicate with and access. The method further includes using the unique address identifier for the second service to forward access requests from the first service to the second service based on the security rules for the first pod and the security rules for the second pod using a network mesh, and receiving the final result of the service request from the first service using a network mesh. The final result includes sub-results obtained from the second service.This method further includes forwarding the final result of a service request to the user via a network mesh. II. Digital Health Platform

[0028] Figure 1 shows a simplified diagram of a digital health platform 100 for providing data-driven technology solutions according to various embodiments. In the illustrated embodiment, the digital health platform 100 includes client computing devices 105 connected to a cloud-based infrastructure 110 via a network 115 including a network gateway 120 and a network mesh 125. The infrastructure 110 is adapted to run services or software applications within service pods 130 using resources provisioned within a deployment ring 135 by a cloud service provider 140 (e.g., a distributed computing environment) using various hardware and cloud infrastructure (e.g., private or on-premises cloud infrastructure and public cloud infrastructure). These services or software applications may be delivered to users of the client computing devices 105 as web-based or cloud services, for example, under an AaaS or SaaS model. Several providers, such as Amazon, Google, and Oracle, offer cloud services. The term cloud service is generally used to refer to services made available to users on demand via a communication network such as the Internet by a service provider's system (e.g., infrastructure 110), such as a healthcare provider or a government regulatory entity. Therefore, consumers can use cloud services provided by service providers without having to purchase separate licenses, support, or hardware and software resources to support the services. For example, a cloud service provider's system may host one or more programs, and users can use one or more programs on demand via the internet without having to purchase infrastructure resources to run one or more programs themselves.Cloud services are designed to provide easy and scalable access to applications, resources, and services.

[0029] In some cases, a user operating the client computing device 105 (e.g., a software or service consumer) utilizes one or more client applications to consume software products, services, or systems provided by various components 145 of the infrastructure 110. In other examples, a user operating the client computing device 105 (e.g., a developer) utilizes one or more client applications to upload the source code of software products, services, or systems provided by various components 145 of the infrastructure 110. Component 145 includes one or more processors, hardware components, or software components that can be run by a combination thereof. It should be understood that various different system configurations are possible, and these may differ from those shown for the digital health platform 100. Therefore, the embodiment shown in Figure 1 is an example of a distributed computing environment for implementing the digital health platform, and is not intended to be limiting.

[0030] The client computing device 105 includes various types of computing systems such as portable handheld devices, general-purpose computers such as personal computers and laptops, workstation computers, wearable devices, game systems, thin clients, various messaging devices, sensors or other sensing devices. These computing devices may run various types and versions of software applications and operating systems (e.g., Microsoft Windows®, Apple Macintosh®, UNIX® or UNIX-like operating systems, Linux or Linux-based operating systems such as Google Chrome® OS) including various mobile operating systems (e.g., Microsoft Windows Mobile®, iOS®, Windows Phone®, Android®, BlackBerry®, Palm OS®). Portable handheld devices may include mobile phones, smartphones (e.g., iPhone®), tablets (e.g., iPad®), personal digital assistants (PDAs), etc. Wearable devices may include Fitbit Versa® smartwatches, magic leap 1®, HTC Vive® and Oculus® virtual reality (VR) or augmented reality (AR) systems, and other devices. Game systems may include various handheld game devices, internet-enabled game devices (e.g., Microsoft Xbox® game consoles with or without Kinect® gesture input devices, Sony PlayStation® systems, various game systems provided by Nintendo®, and others).The client device 105 may be capable of running various different applications, such as various internet-related applications and communication applications (e.g., email applications, short message service (SMS) applications), and may use various communication protocols.

[0031] Network 115 is any type of network well known to those skilled in the art that can support data communication using any of the various available protocols, including but not limited to TCP / IP (Transmission Control Protocol / Internet Protocol), SNA (System Network Architecture), IPX (Internet Packet Switching), AppleTalk®, etc. Just as an example, Network 115 could be a local area network (LAN), Ethernet, Token Ring, wide area network (WAN), internet, virtual network, virtual private network (VPN), intranet, extranet, public switched telephone network (PSTN), infrared network, wireless network (e.g., a network operating under any of the IEEE 1002.11 protocols, Bluetooth®, and / or any other wireless protocols), and / or any combination of these and / or other networks.

[0032] The network gateway 120 is a network node that forms a secure path between multiple networks 115 operating on the same or different protocols. The network gateway 120 may provide network security using one or more of the following techniques: a firewall to monitor incoming and outgoing network traffic, a virtual private network to provide a private and secure communication channel, security scanning to identify security vulnerabilities in the network, and an access manager for authentication and authorization services. The network gateway 120 routes network traffic using service connectors that manage access to routers and various software products, services, or systems (e.g., using a service subscription business model). The network mesh 125 is a local network topology in which infrastructure 110 (e.g., bridges, switches, and other infrastructure devices) connect directly, dynamically, and non-hierarchically to as many other nodes as possible, working together to efficiently route data between devices and nodes. The network mesh 125 manages connectivity using one or more of the following techniques: load balancing, product, service, or system discovery, network access, routing, and peering, traffic mirroring, etc. Network 115, network gateway 120, and network mesh 125 work together to manage all data flowing in or out of infrastructure 110.

[0033] Component 145 includes one or more general-purpose computers, dedicated server computers (including, for example, PC (personal computer) servers, purpose-specific servers, midrange servers, mainframe computers, rack-mount servers, etc.), server farms, server clusters, or any other suitable configuration and / or combination of computers or systems that operate individually or in combination to provide resources, data, services, or programs to client computing devices 105 via the network 115. Component 145 may further include other computing architectures that include virtualization, such as one or more virtual machines running a virtual operating system, or one or more flexible pools of logical storage devices that can be virtualized to maintain virtual storage devices. In various embodiments, component 145 is adapted to run one or more services or software applications that provide the functionality described in this disclosure.

[0034] Component 145 also includes one or more data repositories. These data repositories may be used in various embodiments to store data and other information. For example, one or more of the data repositories may be used to store information for providing data-driven technology solutions such as software as a medical device (SAMD), and for verifying and deploying source code for implementing data-driven technology solutions. The data repositories may reside in various locations. For example, the data repositories used by the component may be local to the component, or they may be remote from the component and communicate with the component via a network-based or dedicated connection. The data repositories may be of different types. In certain embodiments, the data repositories used by the component may be databases, such as centralized databases, distributed databases, NoSQL databases, relational databases, etc. One or more of these databases may be adapted to allow the storage, updating, and retrieval of data to and from the database in response to SQL-formatted commands. In certain embodiments, one or more of the data repositories may also be used by an application to store application data. The data repository used by the application may be of a different type, such as a key-value store repository, an object store repository, or a general storage repository supported by the file system.

[0035] Component 145 also includes compute nodes adapted to run one or more programs, such as services or software applications that provide the functionality described in this disclosure (e.g., services or software applications delivered as web-based or cloud services, or applications for implementing continuous integration and continuous deployment (CI / CD) systems). Each node is optionally a representation of a single machine implemented within a cluster of nodes. A single machine may be a physical machine (e.g., a server in a data center) or a virtual machine hosted on a cloud provider such as Amazon Web Services® (AWS) having a set set of available CPU and RAM resources. In a cluster, nodes pool their resources to form a more powerful machine. Once one or more programs are deployed on the cluster, the cluster intelligently handles the distribution of work to the individual nodes. As nodes are added or removed, the cluster can shift work as needed. Which individual machine is actually running the code is not important to one or more programs or to infrastructure 110.

[0036] One or more programs deployed on one or more clusters are packaged as containers. Containers are a widely accepted standard, and various images can be defined for deploying one or more programs on infrastructure 110. Containerization allows infrastructure 110 to create self-contained execution environments. Any program and all its dependencies can be bundled into a single file and then shared on infrastructure 110. Container creation can be done programmatically, enabling a powerful, fully automated CI / CD pipeline used for verifying and deploying code on infrastructure 110. Containers are wrapped in a higher-level structure known as a pod 130. Containers within the same pod 130 can share the same resources and local network. In some cases, containers can communicate with other containers within the same pod 130 as if they were on the same machine, while maintaining some degree of isolation from others. Pods 130 are used as replication units within infrastructure 110. If a program or resources are strained by processing and a single pod 130 instance cannot bear the load, the infrastructure 110 may be configured to deploy new replicas of pod 130 to the cluster as needed. Even when there is no heavy load, it may be beneficial to have multiple copies of pod 130 running at all times in the production system to enable load balancing and fault tolerance. One or more instances of pod 130 are provisioned to a cloud infrastructure system provided by one or more cloud service providers 140.

[0037] A cloud infrastructure system provided by one or more cloud service providers 140 includes infrastructure resources used to facilitate the provision of one or more instances of pods 130 that support various cloud services provided by infrastructure 110. To facilitate the efficient use of these resources for provisioning one or more instances of pods 130, the resources may be bundled into a set of resources or resource modules (also called “distribution rings 135” or “stateful rings 135”). Each resource module or distribution ring 135 may contain a pre-integrated and optimized combination of one or more types of resources. In certain examples, different distribution rings 135 may be pre-provisioned for different types of cloud services. For example, a first set of distribution rings 135 may be provisioned for SAMD services, and a second set of distribution rings 135 may contain a different combination of resources than the distribution rings 135 in the first set of distribution rings 135, and may be provisioned for data analytics services, and so on. For some cloud services, the resources allocated to provision the services may be shared among the services.

[0038] The digital health platform 100 further includes one or more kernels 150. Each kernel 150 is adapted to operate on each cloud infrastructure system provided by one or more cloud service providers 140. The kernel 150 is a cluster manager that provides resource allocation and isolation across distributed applications or frameworks throughout the digital health platform 100. The kernel 150 provides one or more programs with an application programming interface (API) for orchestrating services and software, including resource management and scheduling. The architecture of the kernel 150 includes agent nodes for executing tasks, master nodes for submitting tasks to the agent nodes, area managers for election and for looking up the addresses of the master nodes, and a framework for coordinating with the master nodes to schedule tasks on the agent nodes.

[0039] The digital health platform 100 further includes a CI / CD system 155. The CI / CD system 155 is implemented within a cloud infrastructure system, enabling the digital health platform 100 to frequently update, test, and deliver changes within the source code of software products, services, or systems. As detailed herein, in healthcare, there are government regulations regarding data security (e.g., data integrity and data privacy) that software must comply with. The CI / CD system 155 allows these policy regulations to be incorporated into the code, enabling compliance to be automatically tracked, verified, and reconfigured. In the SAMD example, data storage locations, server access control, and activity logging may be incorporated into the source code, ensuring user data is protected and managed during software use. Encryption and password-protected behavior may be further incorporated during continuous integration. During continuous delivery, security and monitoring tools can be used to track user activity and detect errors that could lead to security threats.

[0040] The CI / CD system 155 may also be used to provision machine learning models. While machine learning models are initially trained using datasets, over time, the model may drift or the data may change, leading to the need for updated machine learning models. If the machine learning model runs within a software application, the code associated with the software application can include triggers for when the machine learning model should be retrained. For example, the code may include instructions to retrain the machine learning model at predetermined time intervals when new training data is available or when it is determined that the machine learning model's performance falls below a threshold. Furthermore, software developers may explore variations in the model architecture and hyperparameters in a test environment based on monitoring the performance of the machine learning model in a production environment or based on estimated improvements for model optimization. The CI / CD system 155 facilitates building, testing, and deployment to production environments once it is determined that the machine learning model meets performance requirements. III. Security Systems

[0041] Figure 2 shows a simplified diagram of a security system 200 for inter-service communication and authentication over a centralized network mesh in a distributed computing environment 205, according to various embodiments (including the network gateway 120, network mesh 125, and pod 130 as described with reference to Figure 1). Although only a single distributed computing environment is shown, it should be understood that multiple distributed computing environments may be implemented within the digital health platform, and each distributed computing environment will have its own set of components as shown in Figure 2. In the illustrated embodiment, the security system 200 includes one or more client applications 210 (e.g., applications / software modules in a device operated by human actors such as patients and / or service consumers), a Domain Name System (DNS) 215, a gateway 220, a network mesh 225, a public agent 230, and a private agent 235. The public agent 230 provides public services to the user 210. The private agent 235 includes service pods 240, a vault 245, and a vault gateway 250 that work together to provide private services.

[0042] The client application 210 is operated by the user to consume software products, services, or systems provided by the digital health platform. The client application 210 may consume software products, services, or systems by communicating with the digital health platform via the distributed computing environment connector and DNS215 (e.g., by sending requests). DNS215 is a hierarchical distributed database that stores IP addresses and other data, enabling IP addresses to be looked up by name in order to forward calls to IP addresses. For example, when a request from a user is received by the digital health platform, the distributed computing environment connector identifies a distributed computing environment that can fulfill the request, forwards the request and the distributed computing environment that can fulfill the request to DNS215, which looks up the IP address and other data associated with the distributed computing environment and forwards the request to the gateway endpoint of the gateway (e.g., gateway 220) of the associated distributed computing environment (e.g., distributed computing environment 205).

[0043] When connected to a gateway endpoint, the client application 210 can communicate with an authorization unit (e.g., an access management system) to access one or more services within a session. For illustrative purposes, the “session” as described herein includes a session or access session that provides a user with access to one or more services. Sessions disclosed herein may be referred to, for example, an SSO session, an authentication session, or any other type of session that provides access to a user. Services may include, but are not limited to, files, web pages, electronic content, documents, web content, computing resources, or access and functionality provided by applications. For example, a digital health platform may include accessible services such as software products, cloud services, or systems. Services may be requested and accessed using applications. For example, an application may request access to a service from a service server based on a URL that identifies the requested service. When used herein, when an action is “triggered” or “based on” something, this means that the action is triggered or based on at least part of something. Services may be stored and / or managed by one or more computer systems, for example, a distributed computing system. The distributed computing system can facilitate or control access to one or more services when authenticating a user via a client application 210.

[0044] In order for one of the services on a client computing device to be accessed by a client application 210, the user is required to authenticate in order to establish a session (e.g., an SSO session) that provides the user with access to the service via the client application 210. The client computing device initiates the authentication process by requesting access to the authorization unit. The authentication process may include the client computing device displaying one or more GUIs to receive the user's authentication information and submitting the authentication request to the authorization unit. Authentication is established based on verifying the user's authentication information for the authentication defined for the service for which access is requested. When attempting to access a service, the user interacts with an application (e.g., part of or separate from client application 210) that manages access to the user's account via the authorization unit. For example, the application may be an access management application that can present a GUI. Using the application and / or client application 210, the user requests access to one or more services, authenticates, and requests changes in the authentication level.

[0045] Communication between the user's client computing device and the authorization unit is received via gateway 220. Gateway 220 supports access management services. For example, an SSO gateway may implement one or more access agents to balance requests from the client application 210 and / or to process these requests. The client computing device may send and receive one or more communications with agents to facilitate access by the client computing device to one or more services. The authorization unit may send and receive one or more communications with agents to facilitate access by the client computing device to one or more services. A service may be made accessible to the client application 210 based on the successful authentication of the authentication information. Upon receiving the authentication information, the authorization unit verifies whether the requested service is a protected service that requires authentication information for access. The authorization unit determines whether access to the service is protected. If it determines that the service is not protected, the authorization unit authorizes access to the service (e.g., a public service). If the authorization unit determines that access to the service is protected, it determines user authentication via the client application 210 based on the authentication information. Specifically, the authorization unit collects authentication information about one or more levels and / or one or more factors of authentication, and the authorization unit may verify whether the authentication information matches the authentication information registered to enable the user to access the service via the client application 210. Once user authentication is determined, the authorization unit may determine whether the user is authorized to access the service based on the access permitted to the user. The authorization unit may send a communication to the client computing device to indicate the authorization of the user regarding whether the user is authorized to access the service.Next, once it is determined that the user has been authenticated and is authorized to access the service at will, the service is enabled as a service accessible to the user via the client application 210.

[0046] Once a service is enabled as a service accessible to the client application 210, the gateway 220 forwards the request to the network mesh 225. The network mesh 225 is a dedicated layer built into a distributed computing environment that manages communication and networking concerns at the service level (e.g., how various services share data with each other). Ideally, less communication between services is better. However, this is not always possible, as services often depend on each other to complete their operations. In such cases, the network mesh 225 manages and protects communication between services by (i) authenticating subsequent requests or interactions between the user and various services using an authorization unit, (ii) optionally encrypting communication between services, and (iii) enforcing security rules or policies (e.g., pod-level security rules for communication between services within the same pod and between services in different pods). To facilitate these operations, the network mesh 225 includes routers and one or more proxies adapted to intercept calls to and between services, and is comprised of security rules or policies for controlling and routing calls to and between services. In addition to managing and ensuring communication between services, Network Mesh 225 can also provide support for service discovery and load balancing. For example, Network Mesh 225 may retrieve a corresponding pool of service instances from pod endpoints. Network Mesh 225 then sends or routes requests to specific service instances and records the resulting latency and response type. Based on various factors, including observed latency of recent requests, Network Mesh 225 may select the instance most likely to return a fast response.

[0047] The public agent 230 is adapted to provide one or more public services. While these services are designated as public, this does not necessarily mean that authentication / authorization is not required to access them. In some cases, one or more levels or factors of authentication and / or authorization may be required to access the public services. The network mesh 225 manages and ensures communication between the client application 210 and the public agent 230. In some cases, this includes authenticating requests or interactions between the user and various public services using an authorization unit, and routing calls to and between services provided by the public agent 230 while enforcing security rules or policies.

[0048] The private agent 235 is adapted to provide one or more private services contained within a service pod 240 (for example, a first service having a first pod and a second service in a second pod). The network mesh 225 manages and ensures communication between the client application 210 and the private agent 235. In some cases, this includes routing calls to and between services provided by the private agent 235 while enforcing security rules or policies. The private agent 235 utilizes the vault 245 and vault gateway 250 to communicate with other services and manage and store security keys or access keys used by each service to access other services. The vault gateway 250 is a network node that forms a secure path between services and the vault 245. The vault gateway 250 may provide vault network security using one or more of the following technologies: a firewall to monitor incoming and outgoing network traffic, a virtual private network to provide a private and secure communication channel, security scanning to identify security vulnerabilities in the network, and an access manager for authentication and authorization services. The Vault Gateway 250 routes vault traffic using routers and service connectors that manage access to the vault and various secrets, namely security or access keys.

[0049] Vault 245 manages and stores security keys or access keys. Security keys are short-term credentials that allow a service to communicate with and access another service. Security keys may be used to sign programmatic requests to another service (e.g., the application programming interface of another service). A security key consists of an access identifier and a secret access key. Similar to usernames and passwords, a service must use both the access identifier and the secret access key together to authenticate access requests. Security keys may be managed using one or more rules or policies stored in a data store ("policies") to control access to services. Policies define other services that each service may access. For example, an administrator may allow certain services to be accessed only by certain services in order to maintain isolation between services and / or data privacy. Vault 245 determines, based on one or more policies, which security keys a service obtains to access other services. IV. Technologies for deploying services on a digital health platform

[0050] Figures 3 and 4 illustrate the processes and operations for inter-service communication and authentication over a centralized network mesh. Individual embodiments may be described as processes, which may be shown as flowcharts, flow diagrams, data flow diagrams, structural diagrams, or block diagrams. While flowcharts describe operations as sequential processes, many operations may be performed in parallel or simultaneously. Furthermore, the order of operations may be reordered. A process terminates when its operations are complete, but may have additional steps not shown in the diagrams. A process may correspond to a method, function, procedure, subroutine, subprogram, etc. If a process corresponds to a function, its termination may correspond to the function's return to the calling function or the main function.

[0051] The processes and / or operations shown in Figures 3 and 4 may be implemented by one or more processing units (e.g., processor cores), hardware, or software (e.g., code, instructions, programs) executed by a combination thereof. The software may be stored in memory (e.g., on a memory device, on a non-temporary computer-readable storage medium). The specific sequence of processing steps in Figures 3 and 4 is not intended to be limiting. Other sequences of steps may be performed according to alternative embodiments. For example, in alternative embodiments, the steps outlined above may be performed in a different order. Furthermore, the individual steps shown in Figures 3 and 4 may include multiple substeps that can be performed in various orders as appropriate to the individual steps. Furthermore, additional steps may be added or removed depending on the particular application. Those skilled in the art will recognize many variations, modifications, and alternatives.

[0052] Figure 3 illustrates process 300 for inter-service communication and authentication in a digital health platform. The process shown in flowchart 300 is implemented by the architecture, systems, and technologies shown in Figures 1 and 2.

[0053] In step 305, the network mesh receives a service request (e.g., a request from a user for access to a service such as service A). The network mesh resolves the request by determining whether it is familiar with the service. This determination may be made by determining whether the network mesh has data about the service in a cache. A cache is a hardware or software component that stores data (e.g., information about various services) so that future requests for that data can be processed more quickly. Data stored in the cache may be the result of previous requests for the service or copies of data stored elsewhere. If the network mesh has data about the service in the cache, the network mesh retrieves the data from the cache. The data includes the identification of one or more pods (e.g., pod A) containing the service (e.g., service A), and the location of one or more pods in a distributed computing environment. The location may include a specific distributed computing environment, node, cluster of nodes, instance of a node or cluster, or a combination thereof, running one or more pods. The data informs the network mesh which pods are encapsulating a service (e.g., managing the service) and how to access the pods encapsulating the service (e.g., the IP address of the pod in the distributed computing environment).

[0054] In step 310, if the network mesh does not have the data for the service in its cache, it contacts the data registry to retrieve the data for the service. The data registry is a single true point of reference that stores data about all services running on the digital health platform (e.g., multiple distributed computing environments). Similar to the cache, the data informs the network mesh which pods are encapsulating the service (e.g., managing the service) and how to contact the pods encapsulating the service (e.g., the IP addresses of the pods in the distributed computing environment). The data retrieved by the network mesh from the registry may be stored in the cache for downstream processing and future requests.

[0055] In step 315, the network mesh communicates with one or more pods (e.g., Pod A) that encapsulate a service based on data retrieved from a cache or registry. The communication includes a request from the network mesh for security rules for one or more pods. The security rules define (i) a unique address identifier for the service, and (ii) the services that the service is permitted to communicate with and access. For example, the security rules for Pod A define a unique address identifier for Service A and the services that Service A is permitted to communicate with and access. When each pod is created, each pod is assigned rules or policies that govern other pods or services that may communicate with and access the service encapsulated by each pod. One or more rules may be written by an administrator, such as the administrator of the digital health platform. Additionally, when created, each service is assigned a unique address identifier address. This address is tied to the lifetime of the service and does not change while the service is active. Network meshes and pods communicate with services via unique address identifiers, and this communication to services can be managed by rules or policies and automatically load-balanced across instances of pods that encapsulate the services.

[0056] In step 320, security rules for one or more pods are obtained from one or more pods (e.g., Pod A). The one or more pods receive a request from the network mesh for security rules, retrieve the security rules from their data storage, and forward the security rules to the network mesh.

[0057] In step 325, the service request is forwarded to the service (e.g., service A) based on security rules. For example, the network mesh uses a unique address identifier for the service to communicate with the resource request and forward the resource request to the resource. In some cases, the network mesh uses a unique address identifier and a proxy associated with the service to communicate with the service and forward the service request to the service. The proxy may then be used for any subsequent communication with the service regarding the service request.

[0058] In step 330, the service receives and processes a service request. Processing may involve the service performing one or more programmatic actions to satisfy the service request. For example, in the case of a service request, the service may perform one or more actions to provide a service such as collecting medical data, transforming medical data, or communicating medical data. In some cases, as part of satisfying the service request, the service may need to communicate with and access other services on other pods (e.g., pod B) (e.g., retrieve data from a separate data storage device such as service B). In such cases, in step 335, the service connects to the vault and obtains a secret key to communicate with and access another service on another pod.

[0059] In step 335, the vault connects to the service and uses one or more rules or policies stored in the datastore to control access to another service. For example, upon connecting to the service, the vault determines, based on one or more policies, whether the service is permitted to communicate with and access another service. If the service is permitted to communicate with and access another service based on one or more policies, the vault retrieves the security key for the other service and forwards the security key to the service in step 340. If the service is not permitted to communicate with and access another service based on one or more policies, the vault notifies the service that it is not permitted to communicate with and access the other service.

[0060] In step 345, if a service is permitted to communicate with another service and access that service, the service receives the security key of the other service and embeds the security key in the access request to the other service. For example, a service may generate an access request that asks the other service to perform one or more programmatic actions to help fulfill a service request. The access request may be signed using the security key.

[0061] In step 350, the service communicates access requests using the network mesh. In some cases, the service communicates access requests using the network mesh via a proxy associated with the service. The service communicates access requests to the network mesh because (i) the service does not have a unique address identifier for the service, and (ii) the network mesh is able to maintain control and security over all inter-service communications.

[0062] In step 355, the network mesh receives and processes access requests from services. The processing of access requests is similar to the processing of service requests described in steps 305-325 (not shown in Figure 3).

[0063] In step 360, the network mesh forwards access requests from one service to another based on the security rules of the pod associated with the service (e.g., Pod A) and the security rules of the pod associated with another service (e.g., Pod B). In some cases, the network mesh forwards access requests from one service to another service via a proxy associated with the service. The forwarding includes the network mesh determining whether the security rules of the pod (e.g., Pod A) define another service (e.g., Service B) as a service that Service A is permitted to communicate with and access, and whether the security rules of the other pod (e.g., Pod B) define Service A as a service that another service (e.g., Service B) is permitted to receive communications from and access. If another service (e.g., Service B) is a service that Service A is permitted to communicate with and access, and Service A is a service that another service (e.g., Service B) is permitted to receive communications from and access, then the network mesh forwards access requests from one service to the other service.

[0064] In step 365, another service receives an access request from the network mesh and verifies the security key. If the security key is invalid, the other service directly notifies the service of the invalid security key. If the security key is valid, the other service processes the access request. Processing involves another service performing one or more programmatic actions to help fulfill the service request. For example, in the case of a service request, the service may perform one or more actions to provide the service, such as collecting medical data, transforming medical data, or communicating medical data.

[0065] In step 370, the other service returns the result of processing the access request directly to the service. In some cases, the other service communicates the result of the access request using the service via a proxy associated with the service.

[0066] In step 375, the service receives the result of the access request and integrates the result of the access request with the result of the service processing the service request to generate the final result of the service request. The service may then output the final result of the service request to the network mesh, which communicates the final result of the service request to the user, for example, via a network gateway.

[0067] Figure 4 shows a process 400 for inter-service communication and authentication over a centralized network mesh. In step 405, the network mesh receives a service request for a first service, for example, from a user. In some cases, the service request is a request for a service, and the first service is the first service. The first service may include one or more programs deployed on one or more clusters packaged as a first container or a first set of containers on a first distributed computing environment, and the first container or first set of containers may be packaged as a first pod, which is a higher-level structure representing one or more programs running on one or more clusters.

[0068] In step 410, the network mesh retrieves information related to the first service from a cache or service registry. The information includes the identification of the first pod containing the first service and the location of the first pod in the first distributed computing environment. Retrieving the information may include (i) determining whether information related to the first service is available from the cache; (ii) if information related to the first service is available from the cache, retrieving the information related to the first service from the cache; (iii) if information about the first service is not available from the cache, retrieving information about the first service from the registry; and (iv) in response to retrieving information related to the first service from the registry, storing the information related to the first service in the cache for subsequent requests.

[0069] In step 415, the network mesh uses the location of the first pod to obtain security rules for the first pod. The security rules define (i) a unique address identifier for the first service, and (ii) the services that the first service is permitted to communicate with and access. In some cases, the security rules further define (iii) the number of instances available for the first service, and (iv) which instances are available to process service requests.

[0070] In step 420, the network mesh forwards the service request to the first service based on the security rules for the first pod. Forwarding includes (i) determining which instances are available to process the service request based on the security rules for the first pod, and (ii) forwarding the service request to at least one instance of the first service using a unique address identifier for the first service.

[0071] In step 425, the network mesh receives an access request from the first service to communicate with and access the second service. The second service may include one or more programs deployed on one or more clusters packaged as a second container or a second set of containers on the first or second distributed computing environment, the second container or second set of containers may be packaged as a second pod, which is a higher-level structure representing one or more programs running on one or more clusters. The access request includes a security key specific to the second service. The security key is obtained by the first service from a vault, and the first service embeds the security key in the access request. The access request may also include a request from the second service to perform one or more actions on behalf of the first service and / or to obtain the service. In some cases, the access request is a request for a service, and the second service is the second service.

[0072] In step 430, the network mesh retrieves information related to the second service from a cache or service registry. The information includes the identification of the second pod containing the second service and the location of the second pod in the first or second distributed computing environment. In some cases, the second pod is located in the second distributed computing environment, which is different from the first distributed computing environment. Retrieving the information may include (i) determining whether information related to the second service is available from the cache; (ii) if information related to the second service is available from the cache, retrieving the information related to the second service from the cache; (iii) if information about the second service is not available from the cache, retrieving information about the second service from the registry; and (iv) in response to retrieving information related to the second service from the registry, storing the information related to the second service in the cache for subsequent requests.

[0073] In step 435, the network mesh uses the location of the second pod to obtain security rules for the second pod. The security rules define (i) a unique address identifier for the second service, and (ii) the services that the second service is permitted to communicate with and access. In some cases, the security rules further define (iii) the number of instances available for the second service, and (iv) which instances are available to process access requests.

[0074] In step 440, the network mesh forwards the access request to the second service based on the security rules for the first pod and the security rules for the second pod. This forwarding includes (i) determining whether the security rules for the second pod define the second service as a service that the first service is permitted to communicate with and access; (ii) determining whether the security rules for the second pod define the first service as a service that the second service is permitted to receive communications from and access; and (iii) if the second service is a service that the first service is permitted to communicate with and access, and the first service is a service that the second service is permitted to receive communications from and access, forwarding the access request from the first service to the second service using a unique address identifier for the second service. In some cases, the forwarding further includes (iv) determining which instances are available to process the access request based on security rules for the second pod, and forwarding the access request to at least one instance of the second service using a unique address identifier for the second service. The second service may perform one or more actions on behalf of the first service and / or retrieve the service, and may produce sub-results based on the performance of one or more actions and / or the retrieval of the service. The second service may verify a security key before performing one or more actions and / or before retrieving the service on behalf of the first service.

[0075] In step 445, the network mesh receives the final result of the service request from the first service. The final result includes sub-results obtained from the second service.

[0076] In step 450, the network mesh outputs the final result of the service request and, if necessary, communicates the final result to the user, for example. Viewed. Further consideration.

[0077] Some embodiments of this disclosure include a system comprising one or more data processors. In some embodiments, the system includes a non-temporary computer-readable storage medium containing instructions that, when executed on one or more data processors, cause one or more data processors to execute some or all of one or more of the methods and / or some or all of one or more processes disclosed herein. Some embodiments of this disclosure include a computer program product tangibly embodied in a non-temporary machine-readable storage medium containing instructions configured to cause one or more data processors to execute some or all of the methods and / or some or all of one or more processes disclosed herein.

[0078] The terms and expressions used are for illustrative purposes only, not limitation, and in using such terms and expressions, there is no intention to exclude any equivalent or part of any of the features shown and described, however it should be recognized that various modifications are possible within the scope of the invention described in the claims. Accordingly, although the invention described in the claims is specifically disclosed by embodiments and optional features, modifications and variations of the concepts disclosed herein may be relied upon by those skilled in the art, and it should be understood that such modifications and variations are considered to be within the scope of the invention as defined by the appended claims.

[0079] The subsequent description provides only preferred exemplary embodiments and is not intended to limit the scope, applicability, or configuration of the Disclosure. Rather, the subsequent description of preferred exemplary embodiments provides possible descriptions for implementing various embodiments for those skilled in the art. It will be understood that various modifications can be made to the function and arrangement of the elements without departing from the spirit and scope set forth in the appended claims.

[0080] Specific details are given in the following description to provide a complete understanding of the embodiments. However, it will be understood that embodiments can be carried out without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form so as not to obscure the embodiments with unnecessary detail. In other examples, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail to avoid obscuring the embodiments.

Claims

1. 1. A computer-implemented method, comprising: receiving a service request for a first service at a network mesh; retrieving, by the network mesh, information related to the first service from a cache or service registry, the information including an identification of a first pod that includes the first service and a location of the first pod within a first distributed computing environment; obtaining, by the network mesh, security rules for the first pod using the location of the first pod, the security rules defining (i) a unique address identifier for the first service, and (ii) services that the first service is permitted to communicate with and access; forwarding, by the network mesh, the service request to the first service using the unique address identifier for the first service; receiving, by the network mesh, an access request from the first service to communicate with and access a second service, the access request including a security key specific to the second service; retrieving, by the network mesh, information related to the second service from the cache or the service registry, the information including an identification of a second pod that includes the second service and a location of the second pod within the first distributed computing environment or the second distributed computing environment; obtaining, by the network mesh, security rules for the second pod using the location of the second pod, the security rules defining (i) a unique address identifier for the second service, and (ii) services that the second service is permitted to communicate with and access; forwarding, by the network mesh, the access request from the first service to the second service based on the security rules for the first pod and the security rules for the second pod using the unique address identifier for the second service; receiving, by the network mesh, a final result of the service request from the first service, the final result including a sub-result obtained from the second service; and outputting, by the network mesh, the final result of the service request.

2. obtaining the information related to the first service or obtaining the information related to the second service, determining whether the information related to the first service or the second service is available from the cache; if the information related to the first service or the second service is available from the cache, obtaining the information related to the first service or the second service from the cache; if the information related to the first service or the second service is not available from the cache, obtaining the information related to the first service or the second service from the registry; 2. The computer-implemented method of claim 1, further comprising: in response to obtaining the information related to the first service or the second service from the registry, storing the information related to the first service or the second service in the cache for subsequent requests.

3. The computer-implemented method of claim 1 or 2, wherein the security key is obtained by the first service from a vault, and the first service embeds the security key in the access request.

4. 4. The computer-implemented method of claim 3, wherein the access request from the first service further comprises a request for the second service to perform one or more actions and / or obtain a service on behalf of the first service.

5. 5. The computer-implemented method of claim 4, wherein the second service performs the one or more operations and / or obtains the service on behalf of the first service and generates the sub-result based on the performance of the one or more operations and / or obtainment of the service.

6. 6. The computer-implemented method of claim 5, wherein the second service verifies the security key before performing the one or more operations and / or before obtaining the service on behalf of the first service.

7. The computer-implemented method of claim 1 , wherein the second pod is located in a second distributed computing environment that is different from the first distributed computing environment.

8. The security rules for the first pod further define (i) a number of instances available for the first service, and (ii) which instances are available to process the service request, and forwarding the service request to the first service. determining the instances available to process the service request based on the security rules for the first pod; and forwarding the service request to at least one of the instances of the first service.

9. forwarding the access request from the first service to the second service; determining whether the security rules for the first pod define the second service as a service that the first service is permitted to communicate with and access; determining whether the security rules for the second pod define the first service as a service that is permitted to allow the second service to receive and access communications; 9. The computer-implemented method of claim 1, further comprising: forwarding the access request from the first service to the second service if the second service is a service with which the first service is authorized to communicate and access, and the first service is a service with which the second service is authorized to receive communications and grant access.

10. The security rules for the second pod further define (i) a number of instances available for the second service and (ii) which instances are available to process the access request, and forwarding the access request from the first service to the second service comprises: determining the instances available to process the access request based on the security rules for the second pod; 10. The computer-implemented method of claim 9, further comprising forwarding the access request to at least one of the instances of the second service.

11. the first service includes one or more programs deployed on one or more clusters packaged as a first container or a first set of containers on the first distributed computing environment, the first container or the first set of containers packaged as the first pod, which is a high-level construct representing the one or more programs running on the one or more clusters; 11. The computer-implemented method of claim 1, wherein the second service includes one or more programs deployed on one or more clusters packaged as a second container or a second set of containers on the first distributed computing environment or a second distributed computing environment, the second container or the second set of containers packaged as the second pod, which is a higher-level construct representing the one or more programs running on the one or more clusters.

12. 1. A system comprising: one or more data processors in a network mesh; A non-transitory computer-readable storage medium containing instructions that, when executed on the one or more data processors, cause the one or more data processors to: Receiving a service request for a first service; Retrieving information related to the first service from a cache or service registry, the information including an identification of a first pod that includes the first service and a location of the first pod within a first distributed computing environment; using the location of the first pod to obtain security rules for the first pod, the security rules defining (i) a unique address identifier for the first service, and (ii) services that the first service is permitted to communicate with and access; forwarding the service request to the first service using the unique address identifier for the first service; receiving an access request from a first service to communicate with a second service to access the second service, the access request including a security key specific to the second service; obtaining information related to the second service from the cache or the service registry, the information including an identification of a second pod that includes the second service and a location of the second pod within the first distributed computing environment or the second distributed computing environment; Using the location of the second pod to obtain security rules for the second pod, the security rules defining (i) a unique address identifier for the second service, and (ii) services that the second service is permitted to communicate with and access; forwarding the access request from the first service to the second service based on the security rules for the first pod and the security rules for the second pod using the unique address identifier for the second service; receiving a final result of the service request from the first service, the final result including sub-results obtained from the second service; and outputting the final result of the service request.

13. obtaining the information related to the first service or obtaining the information related to the second service, determining whether the information related to the first service or the second service is available from the cache; if the information related to the first service or the second service is available from the cache, obtaining the information related to the first service or the second service from the cache; if the information related to the first service or the second service is not available from the cache, obtaining the information related to the first service or the second service from the registry; and in response to obtaining the information related to the first service or the second service from the registry, storing the information related to the first service or the second service in the cache for subsequent requests.

14. The system of claim 12 or 13, wherein the security key is obtained by the first service from a vault, and the first service embeds the security key in the access request.

15. 15. The system of claim 14, wherein the access request from the first service further comprises a request for the second service to perform one or more actions and / or obtain a service on behalf of the first service.

16. The system of claim 15 , wherein the second service performs the one or more operations and / or obtains the service on behalf of the first service and generates the sub-result based on the performance of the one or more operations and / or the obtainment of the service.

17. 17. The system of claim 16, wherein the second service verifies the security key before performing the one or more actions and / or before obtaining the service on behalf of the first service.

18. 18. The system of claim 12, wherein the second pod is located in a second distributed computing environment that is different from the first distributed computing environment.

19. The security rules for the first pod further define (i) a number of instances available for the first service, and (ii) which instances are available to process the service request, and forwarding the service request to the first service. determining the instances available to process the service request based on the security rules for the first pod; and forwarding the service request to at least one of the instances of the first service.

20. forwarding the access request from the first service to the second service; determining whether the security rules for the first pod define the second service as a service that the first service is permitted to communicate with and access; determining whether the security rules for the second pod define the first service as a service that is permitted to allow the second service to receive and access communications; and forwarding the access request from the first service to the second service if the second service is a service with which the first service is authorized to communicate and access, and the first service is a service with which the second service is authorized to receive communications and grant access.

21. The security rules for the second pod further define (i) a number of instances available for the second service and (ii) which instances are available to process the access request, and forwarding the access request from the first service to the second service comprises: determining the instances available to process the access request based on the security rules for the second pod; 21. The system of claim 20, further comprising forwarding the access request to at least one of the instances of the second service.

22. the first service includes one or more programs deployed on one or more clusters packaged as a first container or a first set of containers on the first distributed computing environment, the first container or the first set of containers packaged as the first pod, which is a high-level construct representing the one or more programs running on the one or more clusters; 22. The system of claim 12, wherein the second service includes one or more programs deployed on one or more clusters packaged as a second container or a second set of containers on the first or second distributed computing environment, the second container or the second set of containers packaged as the second pod, which is a higher level construct representing the one or more programs running on the one or more clusters.

23. 1. A computer program product for causing one or more data processors of a network mesh to carry out operations, said operations comprising: Receiving a service request for a first service; Retrieving information related to the first service from a cache or service registry, the information including an identification of a first pod that includes the first service and a location of the first pod within a first distributed computing environment; using the location of the first pod to obtain security rules for the first pod, the security rules defining (i) a unique address identifier for the first service, and (ii) services that the first service is permitted to communicate with and access; forwarding the service request to the first service using the unique address identifier for the first service; receiving an access request from a first service to communicate with a second service to access the second service, the access request including a security key specific to the second service; obtaining information related to the second service from the cache or the service registry, the information including an identification of a second pod that includes the second service and a location of the second pod within the first distributed computing environment or the second distributed computing environment; Using the location of the second pod to obtain security rules for the second pod, the security rules defining (i) a unique address identifier for the second service, and (ii) services that the second service is permitted to communicate with and access; forwarding the access request from the first service to the second service based on the security rules for the first pod and the security rules for the second pod using the unique address identifier for the second service; receiving a final result of the service request from the first service, the final result including sub-results obtained from the second service; and outputting the final result of the service request.

24. obtaining the information related to the first service or obtaining the information related to the second service, determining whether the information related to the first service or the second service is available from the cache; if the information related to the first service or the second service is available from the cache, obtaining the information related to the first service or the second service from the cache; if the information related to the first service or the second service is not available from the cache, obtaining the information related to the first service or the second service from the registry; 24. The computer program product of claim 23, further comprising: in response to obtaining the information related to the first service or the second service from the registry, storing the information related to the first service or the second service in the cache for subsequent requests.

25. 25. The computer program product of claim 23 or 24, wherein the security key is obtained by the first service from a vault, and the first service embeds the security key in the access request.

26. 26. The computer program product of claim 25, wherein the access request from the first service further comprises a request for the second service to perform one or more actions and / or obtain a service on behalf of the first service.

27. 27. The computer program product of claim 26, wherein the second service performs the one or more actions and / or obtains the service on behalf of the first service and generates the sub-result based on the performance of the one or more actions and / or the obtainment of the service.

28. 28. The computer program product of claim 27, wherein the second service verifies the security key before performing the one or more actions and / or before obtaining the service on behalf of the first service.

29. 29. The computer program product of claim 23, wherein the second pod is located in the second distributed computing environment that is different from the first distributed computing environment.

30. The security rules for the first pod further define (i) a number of instances available for the first service, and (ii) which instances are available to process the service request, and forwarding the service request to the first service. determining the instances available to process the service request based on the security rules for the first pod; and forwarding the service request to at least one of the instances of the first service.

31. forwarding the access request from the first service to the second service; determining whether the security rules for the first pod define the second service as a service that the first service is permitted to communicate with and access; determining whether the security rules for the second pod define the first service as a service that is permitted to allow the second service to receive and access communications; and forwarding the access request from the first service to the second service if the second service is a service with which the first service is authorized to communicate and access and the first service is a service with which the second service is authorized to receive communications and grant access.

32. The security rules for the second pod further define (i) a number of instances available for the second service and (ii) which instances are available to process the access request, and forwarding the access request from the first service to the second service comprises: determining the instances available to process the access request based on the security rules for the second pod; 32. The computer program product of claim 31, further comprising forwarding the access request to at least one of the instances of the second service.

33. the first service includes one or more programs deployed on one or more clusters packaged as a first container or a first set of containers on the first distributed computing environment, the first container or the first set of containers packaged as the first pod, which is a high-level construct representing the one or more programs running on the one or more clusters; 33. The computer program product of claim 23, wherein the second service includes one or more programs deployed on one or more clusters packaged as a second container or a second set of containers on the first or second distributed computing environment, the second container or the second set of containers packaged as the second pod, which is a higher level construct representing the one or more programs running on the one or more clusters.

34. A non-transitory machine-readable storage medium having recorded thereon a computer program according to any one of claims 23 to 33.