Skip to content
This repository was archived by the owner on May 1, 2024. It is now read-only.

[Discuss] saving code on the fly in our base #26

@jimages

Description

@jimages

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

  1. the string is less than 10KB for each snippet
  2. 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions