[apache/incubator-teaclave] Improvements on Teaclave's performance (#517)

[Hongbo <no...@github.com.INVALID>]

<!--
  Thank you for suggesting an idea to make Teaclave better.
  Please fill in as much of the template below as you're able.
-->

### Motivation & problem statement

In some use cases, Teaclave can be slow and some components needs redesign.

1. For example, when passing a payload to Teaclave's client API, the payload will be transmitted back and forth between several services and this significantly affect its performance when the payload itself is very large. This also happens when the arguments is very large.
2. Another potential improvement is exposing interfaces for **unprotected** files, or allow users to use raw input files. Sometimes the user may not need to protect all the input files. For example, while conducting genome computing, the reference genome data is from public data set and it needs no protection, but the personal private genome info needs protection. Therefore Teaclave don't need to deal with the decryption of some files.

### Proposed solution

1. Redesign the framework and maybe treat the payload as a kind of "input file", therefore alleviate the transmission overhead.
2. Allow unprotected file upload or expose unprotected file interfaces

### Describe alternatives you've considered

I don't know if there is an alternative solution.

### Additional context

<!--
  Is there anything else you can add about the proposal?
  You might want to link to related issues here, if you haven't already.
-->

The performance of the DB inside Teaclave may also be enhanced.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave/issues/517