Read Only Mode Very Soon
We are moving Meta to AWS today, this will involve about 30-45 minutes of โRead onlyโ mode while we copy the DB over.
The Discourse team is migrating Meta to AWS, temporarily entering read-only mode for 30-45 minutes. The move is part of expanding hosting options, with plans to publish performance data comparing AWS to their current bare-metal setup at Hurricane Electric. While AWS is significantly more expensiveโaround $1,000/month for Meta, compared to cheaper alternatives like Digital Oceanโthis cost is justified for high-end enterprise customers who require specific regional hosting (e.g., Europe or China). The team notes that AWSโs outbound mail throttling caused delays in notifications and oneboxing, but this has been resolved by switching to a third-party email provider. The discussion highlights that while cloud hosting offers scalability and monitoring tools, bare metal infrastructure provides better performance and lower long-term costs, especially for organizations with the expertise to manage high-availability systems. Some contributors emphasize that managing infrastructure, including failover and monitoring, requires significant human resources, making the total cost of ownership a key consideration beyond just hardware expenses. The team also mentions that future plans include a bare-metal rack in Europe to serve customers needing local hosting.
Read Only Mode Very Soon
We are moving Meta to AWS today, this will involve about 30-45 minutes of โRead onlyโ mode while we copy the DB over.
Everything should be the same once move is over, but you knowโฆ sometimesโฆ plans meet reality and โฆ well .. you know.
We are performing this move as part of our project to expand our hosting offers. Once the move is done we will try to publish some data about how performance looked like on AWS vs our super fast servers at Hurricane Electric.
OK Move is doneโฆ readonly is out
Will there be a blog post with the reasoning behind this? I remember a lot of posts from Discourse about how much more cycles/dollar were available from bare metal.
Perhaps , some high end customers require hosting on AWS cause they need to be in Europe or China, nothing is changing for our hosted customers.
I do want to do a blog post about how much faster and more predictable our hosting is than AWS at some point
That makes sense, yeah.
OK lets try this again and see if it works now?
This is me ensuring that incoming mail is working โฆ letโs see!
Iโd love to hear this for sureโฆ and perhaps even some guidance on making the migration ourselves if we have similar needs. Most excellent!
FYI: I had to re-login to meta since the move - I donโt know if itโs related.
Highly-likely related ![]()
This is very exciting news for those of us working globally. Look forward to hearing more.
Just to be clear we estimate running on AWS costs about $1000/month, for this site. It is extremely expensive. (Meta is deployed as an enterprise site on our end.)
Also @dax and @tobiaseigen have reported massively delayed oneboxing. @hawk has reported big delays in desktop notifications as well.
Wow thatโs a lot.
Can you share your monthly page views please Jeff? Around a million a month?
More than double that.
Congratulations on the basically flawless move! Iโd love to read what your architecture looks like on AWS.
Notification of this post just took 14 minutes to arrive:
UPDATE: It then took ~16 minutes to update this post to Onebox the above post reference.