Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Scalable Persistence layer #7

Closed
fabiante opened this issue Sep 1, 2023 · 1 comment
Closed

Scalable Persistence layer #7

fabiante opened this issue Sep 1, 2023 · 1 comment
Labels
story User story which adds any value to the project
Milestone
v1 - First produc...

Comments

@fabiante
Copy link
Owner

fabiante commented Sep 1, 2023 •
edited
Loading

#6 added the HTTP API but does not use actual persistence. For that a new persistence layer is required. #29 added a lightweigth persistence layer based on SQLite.

Questions

  • What database to use? Interesting options
  • Should the first version already contain some abstraction to support multiple database types (KV, relational, FS)?
  • What configurations do have to be exposed?
@fabiante fabiante added the story User story which adds any value to the project label Sep 1, 2023
@fabiante fabiante mentioned this issue Sep 13, 2023
Closed
2 tasks
@fabiante fabiante changed the title Persistence layer Scalable Persistence layer Sep 14, 2023
@fabiante fabiante mentioned this issue Sep 16, 2023
Closed
2 tasks
fabiante added a commit that referenced this issue Sep 16, 2023
@fabiante
Fix database concurrency issues with RWMutex
b4df7bc 
This seems like a crude fix which should be replaced by a more sophisticated solution.

Right now I don't want to spend lots of time to develop a sophisticated solution, I am fine with a simple, crude sync.RWMutex.
My reasoning is that I intend to migrate towards a proper, scalable database anyway when nearing v1 (see #7).
This was referenced Sep 16, 2023
Merged
Open
@fabiante
Copy link
Owner Author

#50 improved this situation quiet a bit. I have not yet run load tests on Railyway but I consider this issue done. Performance related issues are discussed in #39. I consider Postgres to be scalable so if there is a need for it, scaling is now possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
story User story which adds any value to the project
Projects
None yet
Milestone
v1 - First production ready version
Development

No branches or pull requests
1 participant
@fabiante