天青 - 使用什么样的服务，为Arduino的数据（IOT） [英] Azure - What service to use for Arduino data (iot)

问题描述

我有一个Aurdino YUN在那里我得到一些水数据（多少我已经使用）
我想获得在网络上这个数据与刚开始检查周围的湛蓝这似乎是一个了不起的服务，但有点势不可挡。

I have an Aurdino YUN where i get some water data ( how much i have used ) I would like to get this data on the web and have just started to check around with azure which seems to be an amazing service but a bit overwhelming.

我希望我的项目成长和即时通讯有点困惑，什么样的服务，我应该使用。

I expect my project to grow and im a bit confused as to what service i should use.

我的问题是。
我应该使用什么样的服务？
1.移动服务
2.蔚蓝事件总线

My questions is. What service should i use? 1. Mobile service 2. azure event Bus

我已经阅读了很多指南，他们似乎使用mobileservice但微软似乎想我用eventbus。

I have read alot of guides and they seem to use the mobileservice but Microsoft seems to want me to use the eventbus.

可有人请澄清对服务差或推荐我使用哪一个？

Can someone please clarify the difference on the services or recommend me which one to use?

BR
周华健

BR Emil

推荐答案

这是因为两个服务做完全不同的事情。事实上，你几乎可以考虑的另一个相反的：

That's because the two services do completely different things. In fact, you could almost consider one the opposite of the other:

• 移动业务提供服务的到的移动设备的呼叫的。虽然你可以使用它们来发布事件流，他们没有为此进行了优化。他们不存储流，没有消费者的概念，等你将不得不编写一个事件集线器没有自己的一切。


• 事件集线器存在的接受的从大量设备的大量数据的事件。它的设计接受每秒百万次的事件

• Mobile services provide services to mobile devices to call. While you could use them to post event streams, they aren't optimised for this. They don't store the stream, have no concept of consumers, etc. You would have to write everything that an Event Hub does by yourself.
• Event Hubs exist to accept a lot of data events from a large number of devices. It's designed to accept millions of events per second

移动服务只是没有为事件处理的。

Mobile Services just aren't made for event processing.

事件集线器提供了很多好处：

Event Hubs offer a lot of advantages:

• 的流缓存和排队，所以你不必消耗事件马上


• 您有一个简单的API来定义消费者，而没有有关事件的存储等，您只需拨打 receiver.Receive（）读取流中的下一个事件。


• 您可以有多个消费者处理的数据流。


• 消费者可以停止使用检查点的特定时间点恢复处理流。这样，如果一个消费者崩溃并重新启动最后一个检查点后不会丢失事件。


• 缩放是很容易的，如果流量很高，您只需购买更多的吞吐量单元

• The stream is cached and queued, so you don't have to consume events right away
• You have a simple API to define consumers, without bothering about event storage etc. You just call receiver.Receive() to read the next event from the stream.
• You can have multiple consumers processing a stream.
• Consumers can stop and resume processing at specific points in a stream using checkpoints. This way, if a consumer crashes and restarts it won't lose events after the last checkpoint.
• Scaling is very easy if the traffic is high, you simply buy more throughput units

您会发现在事件概述集线器一个更好的解释文章在MSDN。

You'll find a much better explanation in the Event Hubs Overview article at MSDN.

这篇关于天青 - 使用什么样的服务，为Arduino的数据（IOT）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！