Skip to content
This repository has been archived by the owner on Oct 16, 2023. It is now read-only.

Latest commit

 

History

History
32 lines (28 loc) · 1.95 KB

progresses.md

File metadata and controls

32 lines (28 loc) · 1.95 KB
Raw

Documentation on project progresses, results, findings and decisions.

Francesco Marino

Rome University of "Tor Vergata", Computer Engineering

A.Y. 2019/2020

Serverless composition workflow ideas:

  1. Video conversion:
    1. Local execution: needs external executables for functionality perform,
    2. not suitable for a serverless environment.
    3. Cloud execution: supported only by AWS Transcode.
  2. Text to speech conversion:
    1. needs to store data on S3 or Google Cloud Sotrage
    2. not suitable for benchmarking execution,
    3. hard to place it in a workflow.
  3. Translator:
    1. Language recognition step
    2. [If different from english] translation step
    3. Common english words ranking using NoSQL database:
      1. Amazon Dynamo DB atomic counters
      2. Google Bigtable row-wide atomicity

Findings and Decisions:

  1. Since both AWS Step Functions and Google Cloud Workflows [BETA] support only asynchronous invocations a serverless Python handler has been used (double billing constraint).
  2. Google authentication token function (needed for Google Cloud Workflows [BETA] execution), auth in benchmark application, pass token as HTTP argument just for testing scopes.
  3. AWS Api Gateway 30 seconds limit for any tipe of integration!
  4. Image detection functions with 512MB RAM for timing decreasings.
  5. Light changes in Java Image Detection workflow in Google Cloud Workflows [BETA] implementation due to impossibility for Java to create dictionaries! Setting application/json as response type!
  6. Execution region decided on the basis of Google CLoud Workflows [BETA] availability!
  7. Java on Google Cloud Functions is the bottleneck of the array dimension in memory test! AWS is ok with 2000000 too!
  8. Amazon AWS Throttling Exception when calling execution state on Step Functions. A busy waiting operation has been added in cycle to avoid too many API calls!