Intel Edison & Microsoft Azure Meetup
Download as PPTX, PDF0 likes469 views
Документ обсуждает интеграцию Intel Edison и Microsoft Azure для IoT устройств, предлагая универсальную платформу для как корпоративного, так и энтузиастов использования. Он описывает возможности облачной аналитики, обработки и хранения данных, а также поддержку различных операционных систем и языков программирования. Также представлена информация о масштабируемости, безопасности и плате по факту использования облачных сервисов Azure.
Intel Edison & Microsoft Azure Meetup
- 1. Intel Edison & Microsoft Azure Alex Belotserkovskiy {Microsoft Russia | DX | Tech Evangelist Cloud, IoT & HPC}
- 2. Специальные редакции IoT для устройств 20 лет опыта с Windows Embedded Одна платформа для всех устройств Как для корпоративного использования, так и для энтузиастов С учетом текущих реалий Редакция IoT - бесплатно Клиентская и облачная перспективы Для решений, требущих вычислительные ресурсы Легко разворачивать и управлять Оплата по факту использования Масштабирование Безопасность Поддержка Windows, Mbed, Linux, iOS, Android, RTOS Azure IoT
- 3. Устройства Сбор Хранение Аналитика Вывод Event Hubs SQL Database Machine Learning App Service Service Bus Table/Blob Storage Stream Analytics Power BI External Data Sources DocumentDB HDInsight Notification Hubs Внешние источники Data Factory Mobile Services Logic Apps { }
- 5. Azure Service Bus Queues Topics Event hubs /azure-sdk-for-python/ /azure-sdk-for-php/ /azure-sdk-for-node/ /azure-sdk-for-java/ /azure-sdk-for-ruby/ HTTP(S) https://github.com/windowsAzure/ AMQP 1.0 AMQP 1.0 Embedded Proton-C AMQP 1.0
- 6. Источники событий Сервисы в облаке Хранение и анализ Своя обработка Пользовательск ие интерфейсы Пайплайн на другие сервисы Event Hub
- 8. message = Message(base64.b64encode('Hello World')) sbs = ServiceBusService(service_namespace, shared_access_key_name=key_name, shared_access_key_value=key_value) sbs.send_queue_message(queue_name,message) from azure.servicebus import ServiceBusService, Message, Queue from azure.storage import QueueService import base64 service_namespace = '<YOURSERVICENAME>' key_name = 'MyIoTDevices' key_value = '<YOURKEY>' queue_name = 'mytestqueue'
Editor's Notes
- #5: When we start trying to solve IOT scenarios, there are three key challenges we need to overcome How to deal with unpredictable peaks and valleys in communication from potentially millions of devices Support massive ingestion of data And support that ingestion for terabytes of data This system will also need to be able to buffer the data so we have predictability in processing, store the messages securely, with low latency.
- #7: The event hub is a managed service built specifically to solve these challenges. Whereby queues and topics are focused on individual messages. Event Hubs are about scalable “throughput units” that (by general availability) will enable up to a gigabyte per second with a message based price point that is far more affordable. The trade off is that it operations less as a brokered messaging solution then it does as a huge buffered stream that you can consume and even rewind back through. It allows you to have a massive number of devices, sending their discrete payload, buffer that data up, then consume it at your own leisure. Multiple sources can consume the messages. Be it to persist them into storage, processing and act on them. If the incoming load spikes, Event Hub will help buffer that load, giving your back end processes time to catch up.
- #12: The event hub is a managed service built specifically to solve these challenges. Whereby queues and topics are focused on individual messages. Event Hubs are about scalable “throughput units” that (by general availability) will enable up to a gigabyte per second with a message based price point that is far more affordable. The trade off is that it operations less as a brokered messaging solution then it does as a huge buffered stream that you can consume and even rewind back through. It allows you to have a massive number of devices, sending their discrete payload, buffer that data up, then consume it at your own leisure. Multiple sources can consume the messages. Be it to persist them into storage, processing and act on them. If the incoming load spikes, Event Hub will help buffer that load, giving your back end processes time to catch up.