Skip to content
This repository has been archived by the owner on Feb 17, 2021. It is now read-only.

Batch processing in cloud functions sucks #87

Open
OR13 opened this issue Sep 20, 2019 · 0 comments
Open

Batch processing in cloud functions sucks #87

OR13 opened this issue Sep 20, 2019 · 0 comments

Comments

@OR13
Copy link
Collaborator

OR13 commented Sep 20, 2019

Cloud functions need to load all state needed to operate.

the batch handling that sidetree normally uses, does not map well to cloud functions, especially with our current database integrations and syncing between couchdb and the in memory rxdb instance.

We don't want to start each cloud function execution by syncing a whole data base (we aren't doing this, but we need a workaround for improving perf and avoiding infura calls for cloud functions).

We need to implement a direct to couchdb querying interface for element, and provide a better seperation of concerns between offline first mobile pwa nodes, just in time cloud function full nodes, and always on full node servers (the traditional case).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant