2 ms·

I respectfully disagree on some key points. - 'key' people left because they were service providers (including Arunoda). When the platform became mature and ea

I respectfully disagree on some key points. - 'key' people left because they were service providers (including Arunoda). When the platform became mature and easier to use, they could not get business. - DDP works great, Apollo is a GraphQL layer, two separate projects and target users. If you have a lot of users you need to design pub/sub carefully regardless of tool. Reactivity makes it a bit tougher, but comes with great benefits (unless your project is 'simple' or more static) - Scalability? It's great, and we are the proof -- you just need to know what you are doing (i.e. redis)

KajMagnus 8y ago
About: "we are the proof" — who are you? :- ) It'd be interesting to have a look at your website or web app or Git repo or something. And, if you have time, I think it'd be interesting with a few words about how / why that shows Meteor works well? E.g. num concurrent users that get pub/sub messages? (Your HN profile is blank, there's a GitHub user though with your username, who seem to do lots of Meteor related work. I'm using Nginx and Nchan for pub/sub messages, and ... I'm curious about Meteor and other things too. No plans to switch from Nchan though.)