AWS IoT VS Windows 10 IoT

In this blog post series, we will look at a simple example of modeling an IoT device process as a workflow, using primarily AWS IoT and AWS Step Functions. Our example is a system where, when a device comes online, you need to get external settings based on the profile of the user the device belongs to and push that configuration to the device. The system that holds the external settings is often a third party... - Source: dev.to / about 1 year ago

Iot - MQTT broker to send messages to the Raspberry Pi. - Source: dev.to / over 2 years ago

" Amazon Web Services offers a broad set of global cloud-based products including compute, storage, databases, analytics, networking, mobile, developer tools, management tools, IoT, security and enterprise applications. These services help organizations move faster, lower IT costs, and scale. AWS is trusted by the largest enterprises and the hottest start-ups to power a wide variety of workloads including: web and... Source: over 2 years ago

AWS IoT Core - message broker between all devices and AWS. - Source: dev.to / over 2 years ago

If you have to ask, then you should be using AWS by default. They have plenty of IoT services for you to fiddle around with and get started. Source: almost 3 years ago

I would assume that Microsoft has some presence in these kinds of spaces as well (https://developer.microsoft.com/en-us/windows/iot/), but I find that there is a fairly low barrier to entry as far as learning how to manipulate linux well enough to build this type of functionality yourself. Or you can just as easily use the same knowledge to setup your desktop how you like it or whatever. They're the same thing... Source: about 2 years ago

It does, but Microsoft doesn't consider that to be a "home user" use-case. Instead, in their minds, it's a use-case exclusively of interest to embedded-device system integrators: https://developer.microsoft.com/en-us/windows/iot/. - Source: Hacker News / over 2 years ago

I originally stumbled across what looks like a silver bullet device for caller ID, the Artech AD102. This is a HID device though, not serial like a USB modem and requires DLLs to use. The node-hid package looked a plausible candidate here, but it became rapidly clear that the AD102 must be switched into a kind of "open for questions" mode to get responses out of it, mandating use of the DLLs. Those DLLs are only... - Source: dev.to / about 3 years ago