Systems and methods for inter-app communications
US-2017286614-A1 · Oct 5, 2017 · US
US11748090B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11748090-B2 |
| Application number | US-202218049265-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 24, 2022 |
| Priority date | Jan 29, 2019 |
| Publication date | Sep 5, 2023 |
| Grant date | Sep 5, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
According to some implementations, while a proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (cos) pods having first app version containers, configuration information is received including an identification of a second app version container image for a second app version. The second app version is an updated version of the first app version. Cos pods having second app version containers are brought up based on the second app version container image identified in the configuration information. Test and/or warmup traffic is caused to be routed to the second app version containers. Responsive to an indication regarding the routing of the test and/or warmup traffic to the second app version, causing a transition to sending production traffic to the second app version containers instead of to the first app version.
Opening claim text (preview).
What is claimed is: 1. A non-transitory machine-readable storage medium that provides instructions that, if executed by a machine, are configurable to cause said machine to perform operations comprising: while a proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (COS) pods having first app version containers, receiving configuration information including an identification of a second app version container image for a second app version, wherein the second app version is an updated version of the first app version; bringing up COS pods having second app version containers based on the second app version container image identified in the configuration information; causing test and/or warmup traffic to be routed to the second app version containers while the production traffic continues to be routed to the first application version, the causing including: causing the proxy to be configured with a set of one or more routing rules that distinguish between production traffic and test and/or warmup traffic; causing generation and transmission of the test and/or warmup traffic with a value in a header field that the proxy can use to route that traffic to the second app version; receiving an indication regarding the routing of the test and/or warmup traffic to the second app version; responsive to the indication, causing a transition to sending production traffic to the second app version containers instead of to the first app version; and starting a process to shut down the plurality of COS pods having the first app version containers. 2. The non-transitory machine-readable storage medium of claim 1 , wherein the configuration information includes a services collection identifier and a second app version identifier. 3. The non-transitory machine-readable storage medium of claim 1 , wherein the first application (app) version communicates with a database management system (DBMS) using a database name assigned to the first app version, wherein the configuration information includes DBMS connection information for the first app version and the second app version, and the operations further include: preparing the DBMS by loading app version specific database release artifacts within the second app version container image using the DBMS connection information for the second app version. 4. The non-transitory machine-readable storage medium of claim 3 , wherein the operations further include the preliminary operations of: preloading the DBMS connection information for the second app version into the DBMS; and registering the second app version container image in a container registry. 5. The non-transitory machine-readable storage medium of claim 3 , wherein the DBMS connection information for the first app version and the second app version each include database credentials. 6. The non-transitory machine-readable storage medium of claim 5 , wherein the database credentials including database usernames and passwords. 7. The non-transitory machine-readable storage medium of claim 5 , wherein the DBMS connection information includes a database instance name. 8. The non-transitory machine-readable storage medium of claim 3 , wherein the app version specific database release artifacts include a PL/SQL package and a set or one or more query optimization hints. 9. The non-transitory machine-readable storage medium of claim 3 , wherein the operations further comprise: causing a set of post release database cleanup activities related to the first app version. 10. The non-transitory machine-readable storage medium of claim 1 , wherein the operations further comprise: providing a set of parameters from the configuration information to a reusable deployment pipeline responsible for causing the transition to sending production traffic to the second app version containers instead of the first app version after the second app version containers have been validated. 11. The non-transitory machine-readable storage medium of claim 1 , wherein the operations further comprise: for each of the COS pods having the second app version containers: when the second app version container is live, responding affirmatively to requests whether the second app version container is live; monitoring whether the transition to sending production traffic to the second app version container has occurred; and responsive to requests as to whether the second app version container is ready, the second app version container responding affirmatively after determining that the transition to sending production traffic to the second app version container has occurred. 12. The non-transitory machine-readable storage medium of claim 11 , wherein the process comprises: when one of the plurality of COS pods having the first app version containers is ready to be shut down, starting a timer based on a time period indicated in the configuration information and instructing the first app version container to gracefully shut down; and when the timer expires, forcing the COS pod with the first app version container to shut down if it has not already. 13. The non-transitory machine-readable storage medium of claim 11 , wherein the monitoring whether the transition to sending production traffic to the second app version container has occurred includes: deriving a URL based on the configuration information; and pinging that URL until it indicates that the second app version container is receiving production traffic. 14. The non-transitory machine-readable storage medium of claim 11 , wherein the requests inquiring whether the second app version container is ready are readiness probe requests. 15. The non-transitory machine-readable storage medium of claim 1 , wherein the bringing up COS pods is performed until their number meets a number of COS pods from the configuration information. 16. The non-transitory machine-readable storage medium of claim 1 , wherein the causing the transition is started when a threshold number of the COS pods having the second app version containers are live. 17. The non-transitory machine-readable storage medium of claim 1 , wherein the process comprises: after causing the transition, starting a set of one or more timers based on a time period indicated in the configuration information and instructing the first app version containers to gracefully shut down; and based on expiration of the set of timers, forcing any of the COS pods having the first app version containers that are not yet shut down to shut down.
Related publications grouped by family.
Answers are generated from the same data shown on this page.