Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Ghost does not support clustering or multiple dynos (CDN/HTTP-cache required to scale)
See original GitHub issueIssue Description
Hey @cobyism 👋 I’ve had a look at this Ghost/Heroku setup and unfortunately it promotes some practices that will result in broken Ghost installations.
Ghost does not support clustering in any form due to in-memory caches that will result in each instance getting out of sync with each other - there can only be 1 instance of Ghost for each site.
Can you please remove any mention of clustering, scaling up of dynos (unless advising not to do so!), and the use of node-cluster?
Issue Analytics
- State:
- Created 4 years ago
- Comments:16
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks for your reponse @johnonolan
I’m very happy to hear that Ghost can squeeze so much performance out of a single thread of javascript. That is clearly a testament to Ghost’s engineering practices and history to have so much confidence about this architecture.
Heroku’s dyno scaling is not just for “scaling code” but also to support rolling deployments without downtime and to load balance across healthy dynos if a server/dyno suffers hardware failure.
I always prefer operating a service that can scale horizontally, separate from whether or not the “code scales properly”.
How do you deploy new versions of a Ghost server without downtime or deal with hardware outages if Ghost does not support multiple servers?
To clarify, @mars, this issue was opened by way of an olive branch as an offer of help and guidance. We had both discussed and intended to offer to take over the project and have it officially maintained by the Ghore core team.
Unfortunately the petty hostility in this thread put an end to that idea.
All the best