| ▲ | _el1s7 5 hours ago |
| > 30 MySQL databases (248 GB of data)
> 34 Nginx virtual hosts across multiple domains
> GitLab EE (42 GB backup)
> Neo4J Graph DB (30 GB graph database)
> Supervisor managing dozens of background workers
> Gearman job queue
> Several live mobile apps serving hundreds of thousands of users
He's doing all of that on a single server?!I'm not against vertical scaling and stuff, but 30 db instances in one server is just crazy. |
|
| ▲ | vb-8448 5 hours ago | parent | next [-] |
| It's an average of 8GB per database, I guess he serves multiple clients and decided to "segregate" each client on its instance. If it's acceptable for the business it's nothing wrong with his setup. |
| |
| ▲ | _el1s7 5 hours ago | parent [-] | | > Several live mobile apps serving hundreds of thousands of users It seems like he's having a database for each app. | | |
| ▲ | vb-8448 4 hours ago | parent [-] | | Could be, but this doesn't change my statement: if it's acceptable from the business standpoint there is nothing wrong with this setup. |
|
|
|
| ▲ | leetrout 5 hours ago | parent | prev [-] |
| > 30 db instances They didn't say that and the article didn't allude to that. 1 instance with 30 databases. |
| |
| ▲ | _el1s7 5 hours ago | parent [-] | | Ah yes that's probably true, but still having 30 apps in a single db instance doesn't seem better... |
|