As the Internet of Things (IoT) phenomenon continues to grow, Microsoft has responded by contributing two new editions of Windows 10 – Core and Enterprise –  that are aimed at radically different parts of the devices and systems market.

Here's how Windows 10 IoT is used today, and where it might be going in the future.

Windows 10 IoT Core

The Core edition is a barebones Windows kernel that has been stripped down significantly in order to run on low-power hardware. It is not a full version of Windows, but it is enough to light up the hardware and run whatever application is being designed for that board. This version of Windows 10 has no shell and essentially supports only universal apps – those coded to run in the managed environment of the Universal Windows Platform (UWP) and NOT traditional x86 or x64 apps. This OS version supports a maximum of 256MB of RAM and 2GB of device storage and can run on the x86 chip platform or the ARM platform for low-power devices.

To read this article in full, please click here

Ah, Windows Embedded. The Microsoft operating system that millions of devices and machines are running, typically with a custom application or skin running on top of it so that users don't automatically notice the OS. The operating system that underpins hundreds of thousands of medical devices, automatic teller machines, kiosks at airports and other crowded public places, industrial machinery and control planes, set top boxes, game consoles.

Windows Embedded is a relatively unheralded version of Windows whose existence might surprise you. But it seems like Windows Embedded's existence might also surprise a lot of folks up in Redmond. Here, at the Microsoft campus, despite all of the hullabaloo about Windows 10 and device updates -- and the new Creators Update and Redstone versions that will be coming down the pike at an almost breakneck speed -- Windows Embedded suffers from an opposite problem. It appears unfortunately stuck in a place where no future has clearly been laid out for it.

To read this article in full, please click here

According to a 2015 survey by IT Revolution Press in conjunction with Puppet Labs, organizations using DevOps deploy code 30 times faster than others, doing deployments multiple times per day. Moreover, change failure gets cut in half with DevOps and services are restored up to 168 times faster than they are at non-DevOps organizations.

DevOps: Failing more quickly, and recovering faster

Let’s focus on those last two points for a moment. One thing is for certain: Embracing DevOps also pays off from a disaster recovery standpoint, because the tools and procedures that you use to move applications from development to testing to production and back to development again can also be applied to failing over and recovering from disasters and service interruptions. The same tools that automate the entire DevOps life cycle can also help you make the most use of the resources you already have for recovery purposes.

To read this article in full, please click here