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

Infrastructure: Multiple web and indexing servers on production #29

Closed
m-i-l opened this issue Dec 14, 2020 · 1 comment
Closed

Infrastructure: Multiple web and indexing servers on production #29

m-i-l opened this issue Dec 14, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@m-i-l
Copy link
Contributor

m-i-l commented Dec 14, 2020

At the moment production has all 4 components (web, indexing, database and search) on the same server instance. As it grows it is going to need to scale these out. First would be to have multiple indexing servers and web servers. I've tested running multiple indexing server running concurrently and it is fine, and I've put a reverse proxy in to do the SSL termination so that should make it easier to add multiple web/app servers.

However, at the moment, all the servers are started via a docker-compose file, which is the same as dev except that it copies in the web and indexer code. If splitting over multiple servers, probably going to need some container orchestration, like Docker Swarm or Kubernetes. It would be nice to try and keep the dev setup as close to prod as possible though, ideally without making dev setup prohibitively complicated.

@m-i-l m-i-l added the enhancement New feature or request label Dec 14, 2020
@m-i-l m-i-l changed the title Multiple web and indexing servers on production Infrastructure: Multiple web and indexing servers on production Dec 14, 2020
@m-i-l
Copy link
Contributor Author

m-i-l commented Jul 3, 2022

I had 2,699 visitors to searchmysite.net on 16 May 2022 from the Hacker New post, and had 166,742 searches on 17 May almost all of which were from SEO spammers, and the system was fine, so I'm going to close this for now.

@m-i-l m-i-l closed this as not planned Won't fix, can't repro, duplicate, stale Jul 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant