Rakuten Mobile, Inc.

Rajasi Ahuja

Abhishek Sharma

Mohit Luthra

Bharath Rathinam

Jithin Chathankandath

Shinya Kita

Mihir Pathak

Amey Sandesh Wadekar

A method includes receiving a unilateral relationship between a first service specification and a second service specification; receiving a complimentary relationship between the second service specification and the first service specification; storing each relationship in a relationship table included in a service catalog; receiving a payload corresponding to the first service specification, where the payload includes a service specification relationship with the second service specification; verifying the service specification relationship in the payload correlates with the unilateral relationship stored in the relationship table; in response to the service specification relationship in the payload correlating with the unilateral relationship stored in the relationship table, verifying whether the complimentary relationship exists in the relationship table; and in response to the complimentary relationship existing in the relationship table, updating automatically a service corresponding to the second service specification with a service specification relationship with the first service specification.

System and method for creating a custom relationship between service specifications

Application artifact registration is performed by receiving a bundle service specification configured for deployment of a software service in a cloud native environment, transferring a bundle from an original address indicated in the bundle service specification to an object storage at a principal address, attaching, to the bundle service specification, a bundle identifier and the principal address, extracting a plurality of artifacts from the bundle, each of the plurality of artifacts being stored in the object storage at a subordinate address, and creating one or more artifact service specifications, each artifact service specification representing one or more of the plurality of artifacts, each service specification representing the corresponding subordinate address, an artifact identifier, and an artifact type of each represented artifact.

Application artifact registration

Relationship-apparent application artifact registration is performed by attaching, to the bundle service specification, a bundle identifier, the principal address, and an artifact relationship specification, the artifact relationship specification representing, for each of the one or more artifact service specifications, the subordinate address, the artifact identifier, and the artifact type of each represented artifact, and attaching, to each of the one or more artifact service specifications, a bundle relationship specification, the bundle relationship specification representing the bundle identifier and the principal address.

Relationship-apparent application artifact registration

A method includes creating a package of an application, registering the package with an orchestrator, triggering instantiation of the application in the orchestrator, generating initial configuration files for the instantiation of the application, changing an application state of the application to a planned state, changing the application state to a Keycloak state in response to obtaining client identification of the Keycloak information for the application, changing the application state to an instantiated state in response to deploying the application on the set of target servers, changing the application state to a configured state in response applying daily configuration files to perform daily configuration of the application in the set of target servers, and changing the application state to a monitored state in response to monitoring the application in the set of target servers by an observability framework tool.

Growing community of inventors

Tokyo, Japan

Rajasi Ahuja