10个注意事项在AWS上运行的WebRTC服务

WebRTC lets you embed real-time communications features into your website or mobile application, and you can host the solution in the cloud. Here are some key considerations

该供应商编写的技术底漆已经被网络世界编辑,以消除产品推广,但读者应该注意到它可能会倾向于提交者的做法。有个足球雷竞技app

You want to embed real-time communications features into your website or mobile application for direct peer-to-peer communication and you’ve landed on WebRTC. That’s a great start.

Now you realize that backend services are critical for building a robust solution. You are thinking about hosting your solution in the cloud, using an Infrastructure-as-a-Service (IaaS) environment built on top of Amazon Web Services (AWS). Again, good choice. AWS is an obvious first place to look as they’re a leader in the cloud services space.

但是你开始射击了AWS弹性计算(EC2)的情况下,S3桶,多之前,必须了解什么是参与是很重要的。

这里有您需要在AWS上部署的WebRTC前需要了解的十件事:

1.不要指望绝对的完美:AWS offers premium infrastructure services. More often than not it exceeds expectations, but it’s not perfect. Expect periodic EC2 failure and varied latency of services. Have a plan in place to work around the occasional issues that you will encounter (see below), and you won’t be caught off-guard.

2.可用性是至关重要的:在一个理想的世界,同一个服务器有足够的容量和速度没有任何问题,达到每一个人。不幸的是纯粹的幻想,而不是现实。为确保您的服务始终可用,设计失败的头脑和杠杆可用性区域冗余。规划无缝故障切换,水平和垂直。冗余将防止在故障的情况下或在意外发生广泛的停机时间。你永远不知道什么时候的海底光纤线路可能会被损坏或者会有一个地区停电。

Remember: Monolithic services fail as one. Redundant micro-services fail in isolation. When properly designed, they can recover quickly for minimal service interruption. Consider using rolling deployments, to prevent service delays and unexpected outages. And make sure you thoroughly map your hardware! Consider the ramifications for each component if it should stop working, and plan for queuing or re-routing.

3. Security and availability are opposing concepts:不要在亚马逊不算,让您的建筑安全。亚马逊将提供硬件,但它是你的工作,以确保您免受未经授权的访问,数据泄露和DDoS攻击的威胁时刻存在的基础设施。记住,AWS是黑客的头号目标,因此保护您的情况是至关重要的,因为被扫描的高级威胁活动。默认的安全保障不能提供足够的保护。创建安全服务,也高度可用,需要认真规划不仅在服务水平,但在每个连接的水平;安全性是可用性的对立面。

4. Network monitoring is also your responsibility:Traditional monitoring tools are not effective for monitoring WebRTC, including those provided by AWS and other off-the-shelf solutions. Set up a real-time network analysis and capacity monitoring system that offers custom metrics, so you can fix problems quickly when they arise. Otherwise, small problems can go unnoticed and could lead to extended periods of service disruption. The trick is to identify trending deviations from expected performance before customers do. With WebRTC it’s not always about full service outages.

5.你可以依靠AWS寻求帮助,但他们不会握住你的手:AWS expects customers to manage their own environments. Even so, the AWS team is incredibly supportive and will go to great lengths to improve overall performance, scalability and efficiency. Don’t hesitate to ask for help when you need it. It could prevent costly errors. A Business Support Subscription is a worthwhile investment, just in case. Also, understand that while AWS architects will offer guidance to the best of their ability on WebRTC-related infrastructure challenges, they won’t be able to provide the same level of guidance that they would be able to offer for high-volume transactional services.

6.设置计费提醒:考虑使用亚马逊的CloudWatch设立结算提醒,这样你就不会失去跟踪您的服务收费和使用情况。否则,你可能会在月底收到巨额账单。带宽利用率和EC2实例运行成本可以快速添加,如果你不重视。

7. Failing devices should be de-commissioned immediately:并非所有情况下都是平等的,即使他们是同一类的。网络问题可能意外出现因硬件故障,所以一定要确保基准,取代那些落在规范出来。删除影响的节点,并启动即使问题得到解决新的问题。否则,该设备可能会意外地再次失败。跟踪只有选择最好的实例。

8. Right-size the instances you use:Amazon offers many types of computing instances, and each one is optimized for different types of resource requirements. There are different configurations for processors, network capabilities, memory, and so on. There is no single best option for backend WebRTC services. Again, it all depends on your needs. Expect to benchmark, test, tweak, and repeat to find the best balance. Be aware that some instances come with limitations. For example, watch out for the CPU credit scheme on some of the lower-end instances.

9. Right tech, right tools:Make sure that WebRTC is the right solution for your needs. WebRTC is ideal for many, but not all applications. Scenarios where you need near-time and not real-time (like a viewer streaming live media or a broadcast) are not a fit for WebRTC. Amazon offers great solutions for streaming a la YouTube or Netflix, and is an ideal solution provider for that task, as well.

10. PaaS的提供者可能是你最好的选择:作为一个产品所有者或制定者,你的主要目标是创建一个伟大的产品,将满足用户和(在许多情况下),缩短产品的收入。托管您的AWS平台将有助于为您提供的WebRTC后端服务公司骨干,如果你牢记这点,而是一个DIY打造出可能是昂贵和费时。为了加快产品上市时间,并保持产品的重点,考虑利用第三方的PaaS提供商。PaaS的供应商将消除建立和维护一个实时通信组件的艰巨挑战。这是风险较小,而且会缩短产品上市时间。

特马实业是一种嵌入式实时通信平台作为服务(PaaS)提供商,能够为客户构建实时通信功能到任何应用,任何设备,在任何规模。特马实业是双方的工作成员World Wide Web Consortium(W3C)和互联网工程任务组(IETF)。在W3C和IETF提供由谷歌Chrome,Mozilla Firefox浏览器和Opera使用的WebRTC标准的实现。特马实业也帮助bring WebRTC到到微软的Internet Explorer和Apple Safari桌面浏览器。

加入对网络世界的社有个足球雷竞技app区Facebook的LinkedIn对那些顶级心态的话题发表评论。

版权© 2016Raybet2

IT薪资调查:结果是在