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

Clarification about architecture, etc #4

Open
roynasser opened this issue Mar 5, 2015 · 1 comment
Open

Clarification about architecture, etc #4

roynasser opened this issue Mar 5, 2015 · 1 comment

Comments

@roynasser
Copy link

Hi, this sounds like an interesting project...

I'm wondering a few things, maybe you can help...

  • is this production ready? (I see its under development still, but any use in production?)
  • what is the topoloy exactly? does this go together with a mysql server? how would one scale this? or is it just a "connector" on a mysql master, and then this can be served out?

Thanks!

@numtel
Copy link
Owner

numtel commented Mar 6, 2015

I would say that more testing is probably needed to call this "production ready."

No load tests have been performed yet to determine memory usage (and/or leaking) or response time statistics. I have not actively implemented these on this project as I am working on a very similar, (yet unreleased) project for Postgres/MSSQL where I am performing these types of tests. I cannot give an exact timeframe for my ability to provide this testing to this package but it will be at least a couple of months.

The scaling question ties back into the lack of load testing. It should be theoretically possible to build a network of replicating MySQL servers that can be tapped but the efficiency is unknown at this point.

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

2 participants