Methodology

User flow

User flow diagram

1. When user visits Software provider's (SP) website and prompts to sign up, user will enter their Recloud ID. For example: id.kate.com

2. The software provider redirects the user to their lD URL or login URL.

3. User enters their credentials. Recloud provider performs authentication, checks user's access grants against the software provider and redirects to the software provider with access token or a prompt to user to grant access as per OAuth 2.0 specification.

4. Once the user is authenticated, software provider can choose to provide a trail version of the software served from their own server or let the user install the software on their own cloud.

5. If the user chooses to install the software on their cloud, software provider redirects to Recloud installation URL identified from access token.

6. Recloud provider checks access grant to install software and performs authorization if required.

7. Recloud provider installs software on user's cloud by running a background job to fetch the software from software provider's public repository URL or Recloud public registry and run the code to create cloud resources and deploy the application.

Software development life cycle

1. The developer of the application writes code using the stack of their choice that supports serverless. Developer also writes infrastructure as code. Infrastructure like serverless functions or docker containers or serverless databases that the app requires can be used.

   Infra as Code examples: AWS CDK, Pulumi

2. Developer adds support to recloud by using recloud SDKs which takes care of OAuth flow and app installation when users chooses to install their app.

3. Developer pushes code to their cloud repository like Github or Gitlab.

4. Developer signups on Recloud public registry as a developer and establishes pipeline to push newest code from developer's cloud repository to recloud sandbox registry.
5. Developer can then test their applications by signing up with any recloud provider and installing their application from recloud sandbox registry.

6. Once the development is complete, the developer pushes the stable version of their app to recloud public registry.

7. Once published, any user can install the app either visiting developer's website or visiting recloud registry and completing the login.

app development life cycle using recloud

Recloud provider - implementation

A recloud provider is just another Software provider.

1. Once a Client signs up to use recloud, recloud provider will create and allocate a default private cloud or shared public cloud for the client and installs authentication module, installation module in it.
2. Clients can choose to link their existing private cloud and virtual network from providers like AWS, Azure, GCP etc.

3. The authentication module exposes a URL which client can customize and use as their Recloud ID. Authentication module is just another application installed on client's cloud which takes care of authentication for client, for all of their applications.
4. The installation module takes care of installing a new application on client's cloud.

5. During installation, recoud provider will create and allocate a Recloud application URLfor each application so that client can access their applications.