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.

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

Currently not webscale #776

Open
avelardi opened this issue Aug 1, 2016 · 0 comments
Open

Currently not webscale #776

avelardi opened this issue Aug 1, 2016 · 0 comments

Comments

@avelardi
Copy link

avelardi commented Aug 1, 2016

Without a NoSQL backend, I'm not seeing a clear or easy way to make this project webscale. I see the MySQL connector exposed, but that doesn't offer proper sharding or performance increases when scaled. At the rate this project is gathering momentum, I fear we will hit the theoretical limits of the backend. Redis/MongoDB is the clear solution to all of these issues. A quick comparison will show webscale technology is the clear way to go with built in sharding modules and double hashed memory storage:

image

Better performance can be achieved by running Redis in front of it so we can then store all values in the queue. On top of that, we can have varnish cache additional content for even better scalability in the end.

I'm gonna start working on a clean transition version so we can migrate to a solution better suited for the cloud.

Note: In addition to moving to Varnish/Redis/Mongo (the defacto webscale stack in the cloud to date) we'll also enable sha-1 encryption keys during memory transport to ensure all data is securely stored in ram persistently, but this will need to be another issue.

@progval progval changed the title Currently not webcale Currently not webscale Jan 23, 2017
@vttn vttn mentioned this issue Aug 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant