网络延迟，使用不同的PaaS解决方案 [英] Network latency with using different PaaS solutions

问题描述

不知道这是属于计算器或stackexchange。 MODS的 - 请点我朝着正确的平台

Not sure is this belongs to stackoverflow or stackexchange. Mods - please point me towards the right platform.

我无法找到统计的平均网络延迟（由于网络电话）和平均成本上涨（因为这些平台还收取网络入口/出口）由于涉及网络服务呼叫量 - 特别是当我们使用不同的提供商托管Web应用程序和数据库的主机。 pretty的每样东西是SSL来增加更多的延迟​​。是这样的延迟/成本显向消费者？我明白缓存会有所帮助，但有一个限度的。

I am unable to find statistics for an average network latency (due to network calls) and average cost hike (because these platforms also charge for network ingress/egress) due to the amount of web-service calls involved - especially when we use different providers for webapp hosting and database hosting. Pretty much everything is on SSL to add more delay. Is this delay/cost noticeable to a consumer ? I understand caching will help, but there's a limit to that.

我想补充一些背景 - 我想知道，如果它是一个聪明的决定，启动去与PaaS的（我计划使用CloudBees的/ mongolab）;或preFER推出的所有内容的IaaS（如EC2）。我想GAE不会有这样的问题，因为一切数据存储是云计算的一个组成部分？

Just to add some context - I am wondering if it's a smart decision for a startup to go with PaaS (I am planning to use Cloudbees/mongolab); or prefer rolling out everything on IaaS (like EC2). I guess GAE will not have such issues because everything Datastore is a part of their cloud ?

谢谢！

推荐答案

免责声明：我在CloudBees的工作。与我联系 [e-mail] 如果你想讨论具体的应用程序的限制的

Disclaimer: I'm working at CloudBees. Contact me [e-mail] if you want to discuss specific application constraints

CloudBees的（也可能是其他的PaaS，不能告诉）不账单的网络流量。相比于IaaS的，将账单I / O，网络，CPU周期等，PaaS的提供了一个更高层次的抽象再定价模式。

CloudBees (and probably other PaaS, can't tell) don't bill for network traffic. Compared to an IaaS that would bill I/O, network, CPU cycles, etc, a PaaS offer a higher level abstraction then pricing model.

网络延迟确实是被托管在PaaS的一个主要课题，可能在另一个大陆举办。 CloudBees的提供美国东部和欧洲，西部地区以托管应用程序。对于欧洲客户，托管在欧盟区，具有低延迟的网络连接是一个重大改进。

Network latency indeed is a major topic being hosted on a PaaS, that may be hosted on another continent. CloudBees offer US-east and EU-west regions to host application. For European customers, being hosted in EU zone, with low-latency network connection is a major improvement.

主机上的IaaS VS PaaS的可能是有意义的，但可能并不像你的启动是在早期阶段。使用PaaS的一个助推器，以获得quicly在线和交付功能，以您的客户。如果/当你成功了，也许你会preFER无论出于何种原因切换（？部分）到IaaS的，以至后来跟随Facebook和谷歌建立自己的数据中心：P

Hosting on a IaaS vs a PaaS can make sense, but probably not as your startup is in early stage. Use the PaaS as a booster to get quicly online and deliver features to your customers. If/when you're successful, maybe you'd prefer for whatever reason to switch (partially?) to a IaaS, and even later follow Facebook and Google building your own DataCenter :P

我们有许多初创公司如CloudBees的客户，有利于高水平的服务，以减少时间将产品推向市场，并专注于公司的实际业务。即使是工作在一个IaaS的是有趣的工程师，从商业角度看，它是不是真的是你想要开发人员专注于当你的公司是在一个竞争激烈的市场快速 - 而且还有很多的其他的话题，你可以有工程师有乐趣; ）

We have many startups as CloudBees customers, that benefit high level service to reduce Time-to-market, and focus on company actual business. Even working on an IaaS is fun for engineers, from business perspective it's not really what you want developers to focus on when your company has to be quick on a competitive market - and there's lot's of other topics you can have engineers to have fun with ;)

我不明白在GAE您的评论。谷歌的确是托管自己的数据存储。 PaaS的像CloudBees的依赖于合作伙伴的SaaS的蒙戈（mongoHQ.com），但是这一个托管于AWS以及网络延迟是一样的，如果CloudBees的托管它自己的蒙戈实例。

I don't get your comment on GAE. Google is indeed hosting his own DataStore. A PaaS like CloudBees relies on partner SaaS for Mongo (mongoHQ.com) but as this one is hosted on AWS as well network latency is the same as if CloudBees hosted it's own mongo instances.

这篇关于网络延迟，使用不同的PaaS解决方案的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！