
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/khEdCXoWqpsJ.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
> --
> You received this message because you are subscribed to the Google Groups "Google App Engine" group.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
>
>
But even for EU bound traffic, they probably route it to US
datacenters first then route it via internal networks to the EU.
Mainly for quality of service reasons, they have more control over
their internal network (even it it works via public internet) than
pure public internet.
So they would be paying US 'entry/exit' rates, but only charging EU rates.
> I'd be **very** interested to see someone setup TyphoonAE on a VPS and
> compare true cost-- it would be hilarious if TyphoonAE+VPS beat GAE native.
Surely that is not that far fetched? Esp. if you only count the cost
of the VPS itself, not the time to setup and maintain TyphoonAE
running on that VPS (and maintaining the VPS itself)
It's like just about anything, DIY can usually save money. But it
takes time instead.
But the real value of GAE, comes with scalablity. Take your
installation and instantly scale it to 15 VPS's. How about 200
servers? Multi-terabyte datastore?
Multi-datacenter replication and failover? Someone on call to deal
with the sudden 'darkness' of large numbers of your machines
disappearing.
(all possible - but quickly gets non-trivial. particully if want to
scale quickly)