I'll talk to that :)
Then we can have a another way called multiple balancers
That way, one server accepts the HTTP traffic
all others accepts direct DDP traffic
They need to have DNS
entires for each
Then browser directly connect to the DDP server
If the server is down, browser detects an error
then it'll try to connect to some other DDP server
There is no with DNS here
DNS issue comes
when we try to server HTTP traffic from two different servers
It's an issue, but it's also true if you HaProxy
solution is to use something like Route 53 which does health checks
And we can use a low TTL to get rid of caching
Hope, I answered well :)
And Cluster is one part of the tooling
We'll have a full high performance ddp-proxy which can do rate limits
SSL, monitorting and some other stuff
If the DDP server is exposed to the public, we must have SSL
That's why we added it to Meteor Up
so how does that SSL work? do you still need nginx or something?
Since NodeJS suck at SSL
We don't do it
Yes we can use nginx, stud, haproxy or something
We are using it with Meteor Up
It has SSL support via stud
Soon we have a meteor-proxy (or ddp-proxy)
Which will be written in go
and it'll have SSL support
@mjmasn I think it was you asking about Fibers yesterday, wasn't it? I was struggling to remember a blog post on it, well: https://meteorhacks.com/fibers-eventloop-and-meteor.html
If anyone here has an evented mind subscription (or has thought about it) his latest series: https://www.eventedmind.com/classes/build-a-multi-page-app-with-iron-meteor-6737880d is really, really good.
