IP Library › Granted Patent US 10,678,512
Granted Patent B2
US 10,678,512 · App. 15/333,694 · Granted Jun 9, 2020

Enabling local development of microservices for hosting in remote orchestration engines

Inventor: Benjamin M. Browning (Brevard, NC)
Assignee: Red Hat, Inc.
G06F8/30G06F8/71H04L12/4641H04L12/66
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,678,512
App. No.
15/333,694
Granted
Jun 9, 2020
Kind
B2
Abstract

Enabling local development of microservices for hosting in remote orchestration engines is provided. In one example, a method includes registering, using an orchestration engine executing on a remote computing device comprising a processor device, a gateway service within the orchestration engine to have a same type as a microservice under development within a local development environment executing on a local computing device. A bidirectional connection between the gateway service and the local development environment is established. The gateway service within the orchestration engine receives inbound network traffic directed to the microservice under development, and redirects the inbound network traffic to the microservice under development.

Claims (34)

1. A method for enabling local development of a microservice for hosting in a remote orchestration environment, comprising:

registering, using an orchestration engine executing on a remote computing device comprising a processor device, a gateway service within the orchestration engine to have a same type as a microservice under development within a local development environment executing on a local computing device, wherein registering the gateway service to have the same type as the microservice under development comprises registering the gateway service as supporting a same application programming interface (API) contract as the microservice under development;

establishing a bidirectional connection between the gateway service and the local development environment;

receiving, by the gateway service within the orchestration engine, inbound network traffic directed to the microservice under development, the inbound network traffic comprising inbound network traffic originating from a microservice of one or more microservices hosted by the orchestration engine;

redirecting, by the gateway service within the orchestration engine, the inbound network traffic to the microservice under development;

receiving, by the gateway service within the orchestration engine, outbound network traffic originating from the microservice under development and directed to the microservice of the one or more microservices; and

redirecting the outbound network traffic originating from the microservice under development to the microservice of the one or more microservices.

2. The method of claim 1 , wherein establishing the bidirectional connection between the gateway service and the local development environment comprises establishing a bidirectional connection between the gateway service and a gateway client executing on the local computing device.

3. The method of claim 2 , wherein the gateway client comprises a virtual private network (VPN) client.

4. The method of claim 1 , wherein the gateway service comprises a virtual private network (VPN) server.

5. The method of claim 1 , wherein the gateway service is integrated into the orchestration engine.

6. A computing device, comprising:

a memory; and

a processor device coupled to the memory to:

register, using an orchestration engine executing on the processor device, a gateway service within the orchestration engine to have a same type as a microservice under development within a local development environment executing on a local computing device, wherein to register the gateway service to have the same type as the microservice under development is to register the gateway service as supporting a same application programming interface (API) contract as the microservice under development;

establish a bidirectional connection between the gateway service and the local development environment;

receive, by the gateway service within the orchestration engine, inbound network traffic directed to the microservice under development, the inbound network traffic comprising inbound network traffic originating from a microservice of one or more microservices hosted by the orchestration engine;

redirect, by the gateway service within the orchestration engine, the inbound network traffic to the microservice under development;

receive, by the gateway service within the orchestration engine, outbound network traffic originating from the microservice under development and directed to the microservice of the one or more microservices; and

redirect the outbound network traffic originating from the microservice under development to the microservice of the one or more microservices.

7. The computing device of claim 6 , wherein the processor device is further to establish a connection between the gateway service and the local development environment by establishing a connection between the gateway service and a gateway client executing on the local computing device.

8. The computing device of claim 7 , wherein the gateway client comprises a virtual private network (VPN) client.

9. The computing device of claim 6 , wherein the gateway service comprises a virtual private network (VPN) server.

10. The computing device of claim 6 , wherein the gateway service is integrated into the orchestration engine.

11. A computer program product for enabling local development of a microservice for hosting in a remote orchestration environment, the computer program product stored on a non-transitory computer-readable storage medium and including instructions to cause a processor device to:

register, using an orchestration engine executing on the processor device, a gateway service within the orchestration engine to have a same type as a microservice under development within a local development environment executing on a local computing device, wherein to register the gateway service to have the same type as the microservice under development is to register the gateway service as supporting a same application programming interface (API) contract as the microservice under development;

establish a bidirectional connection between the gateway service and the local development environment;

receive, by the gateway service within the orchestration engine, inbound network traffic directed to the microservice under development, the inbound network traffic comprising inbound network traffic originating from a microservice of one or more microservices hosted by the orchestration engine;

redirect, by the gateway service within the orchestration engine, the inbound network traffic to the microservice under development;

receive, by the gateway service within the orchestration engine, outbound network traffic originating from the microservice under development and directed to the microservice of the one or more microservices; and

redirect the outbound network traffic originating from the microservice under development to the microservice of the one or more microservices.

12. The computer program product of claim 11 , including instructions to cause the processor device further to establish a connection between the gateway service and the local development environment by establishing a connection between the gateway service and a gateway client executing on the local computing device.

13. The computer program product of claim 12 , wherein the gateway client comprises a virtual private network (VPN) client.

14. The computer program product of claim 11 , wherein the gateway service comprises a virtual private network (VPN) server.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 25, 2016
From: BROWNING, BENJAMIN M
To: RED HAT, INC.
Reel/Frame 040120/0872 →
Continuity (1)
Related Publication 20180113680A1 · Apr 26, 2018