Yesterday’s YouTube “Code Report” from Fireship mentions Meteor[JS]. I’ll leave the link here for you to check out. You may want to leave Jeff a message afterwards.
2 Likes
You know nothing, Jon Snow.
1 Like
lets comment there 
1 Like
At video, there is this comment:
From nohandleforw:
Meteor 3.4 and 3.5 has solved most of the scaling issues, and I’ve run millions of concurrent users at scale. You should really look at what’s been going on in the meteor community the last year. I’ve built every one of my successful business and projects with meteor.
What kind of hardware/CPU/RAM and software does it require to run millions of concurrent users at scale with Meteor 3.5 ?
I would say that greatly depends on how the app is architected. Is everything real time? Is it using rest endpoints instead of meteor method calls and DDP connections? Are they caching data at the edge with a CDN? Are they running multiple node processes on individual machines or multiple machines with a load balancer to route traffic based on least connections?
These are all tricks I use to scale my meteor deployments.
4 Likes
More importantly, why can’t I run Meteor 3.5
1 Like
FYI: we’re recording a definitive podcast episode to use as an answer whenever someone asks “is Meteor.js dead?”
4 Likes
unfortunately we don’t have this info officially today, we are working to improve our observability stack first to be able to answer it.
I think it really depends on the application itself. A simple blog would be different from a full featured platform.