-
Workflow
-
Client posts to Sinatra app
-
API Request Scenarios
- Request API Format structure?
- Request when Sinatra down
- Large number of requests to Sinatra, can we take it?
- 400 response from Sinatra, is it possible?
-
Sinatra app
-
Actions
- Converts the request into CF compatible
- Posts the request to CF
-
Receives code response from CF and forwards to Client
- 200
- Creates transaction in workflow
- 400
- Request retries from Client
- Frequency?
- 500
- Workflow Down
- Request retries from Client
- Frequency?
- Receives and Converts the result into client compatible format
-
Posts the results to Client app
- Result API format verification
-
Receives code response from Client and forwards to CF
- 200
- Successful
- 400
- Request retries from CF
- Frequency?
- 500
- Workflow Down
- Request retries from CF
- Frequency?
-
Attributes
-
Secret Key from client Stored
- Generates Signature at Sinatra
- Matches the value with Clients Signature
- Successful match
- 200 OK response
- Unsuccessful match
- 200 along with failure message
- Saves no API data
- Keeps Users Private and Public keys
-
Keeps Template ID/Access hash
- Configure option?
-
Client Platform(Workflow)
- Processes transaction
-
Sends the result to Sinatra
- Completed
- Returned
-
Trail testing
- End to End testing with client on Monday