You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2024. It is now read-only.
Many user complain that their code get lost when they close their broswers. Shall we consider save user code on the fly? My opinion is that we can set a demand (2000 read/write per seconds for example) and fork a new branch to experiment with other powerful programming language and tools. Only can we merge when our performance meet our demands.
assumption
the string is less than 10KB for each snippet
It doesn't matter if user's code will be save later after they save code in server case the lastest code is saved in the browser. we should keep. That means we should only keep the eventually consistent with the latest code.
Proposal on the architecture
We should try to save users code only when they try to test their code. After the website receive the requests, it save the code in the MQ and responded with OK. So the browsers can run very fast. and we have consumers to save the codes in our databases.
The text was updated successfully, but these errors were encountered:
Many user complain that their code get lost when they close their broswers. Shall we consider save user code on the fly? My opinion is that we can set a demand (2000 read/write per seconds for example) and fork a new branch to experiment with other powerful programming language and tools. Only can we merge when our performance meet our demands.
assumption
Proposal on the architecture
We should try to save users code only when they try to test their code. After the website receive the requests, it save the code in the MQ and responded with OK. So the browsers can run very fast. and we have consumers to save the codes in our databases.
The text was updated successfully, but these errors were encountered: