Windows 7 arrived as a saving grace for Microsoft after its debacle with Vista. Microsoft saw enterprises easily upgrading to Windows 7 from XP and Windows 7 itself was available on sale for nearly seven years. Windows 8 and Windows 8.1 stayed on the shelves for just four years, which proves the outcome of the OS.

However, for those already running Windows 7 and Windows 8.1 on their PCs, worry not. Microsoft plans to continue support for Windows 7 and Windows 8.1 until January 2020 and 2023 respectively. Windows 10 upgrades have stagnated since the end of free update in July and this particular move should help the new OS reach more potential customers.

Bluemix supports several programming languages including Java, Node.js, Go, PHP, Swift, Python, Ruby Sinatra, Ruby on Rails and can be extended to support other languages such as Scala through the use of buildpacks.

Bluemix would offers the Services such as MySQL, Postgress Database, Node.js, Ruby on Rails, Map Reduce etc in a Catalogue. New Services are added on a regular basis. But there are very interesting services such as Auto Scaling, Application Monitoring which one can explore.

Design:
Salt was designed to be highly modular and easily extensible, to make it easy to mold to diverse applications.
The module design of Salt creates Python modules that handle certain aspects of the available Salt systems. These modules allow for the interactions within Salt to be detached and modified to suit the needs of a developer or system administrator.

Module types:
The Salt system maintains many module types to manage specific actions. Modules can be added to any of the systems that support dynamic modules. These modules manage all the remote execution and state management behavior of Salt. The modules can be separated into six groups:
• Execution modules are the workhorse for Salt’s functionality. They represent the functions available for direct execution from the remote execution engine. These modules contain the specific cross platform information used by Salt to manage portability, and constitute the core api of system level functions used by Salt systems
• State modules are the components that make up the backend for the Salt configuration management system. These modules execute the code needed to enforce, set up or change the configuration of a target system. Like other modules, more states become available when they are added to the states modules.
• Grains are a system for detecting static information about a system and storing it in RAM for rapid gathering.
• Renderer modules are used to render the information passed to the Salt state system. The renderer system is what makes it possible to represent Salt’s configuration management data in any serializable format
• Returners: the remote execution calls made by Salt are detached from the calling system; this allows the return information generated by the remote execution to be returned to an arbitrary location. Management of arbitrary return locations is managed by the Returner Modules.
• Runners are master side convenience applications executed by the salt-run command.

The specification does not specify the meaning of “small code footprint” or the meaning of “limited network bandwidth”. Thus, the protocol’s availability for use depends on the context. In 2013, IBM submitted MQTT v3.1 to the OASIS specification body with a charter that ensured only minor changes to the specification could be accepted. MQTT-SN is a variation of the main protocol aimed at embedded devices on non-TCP/IP networks, such as ZigBee

MQTT Methods:
MQTT defines methods (sometimes referred to as verbs) to indicate the desired action to be performed on the identified resource. What this resource represents, whether pre-existing data or data that is generated dynamically, depends on the implementation of the server. Often, the resource corresponds to a file or the output of an executable residing on the server.
Connect: Waits for a connection to be established with the server.
Disconnect: Waits for the MQTT client to finish any work it must do, and for the TCP/IP session to disconnect.
Subscribe: Waits for completion of the Subscribe or Unsubscribe method.
Unsubscribe: Requests the server unsubscribe the client from one or more topics.
Publish: Returns immediately to the application thread after passing the request to the MQTT client.

When it comes to building HTTP APIs, other frameworks weigh you down with tons of dependencies and unnecessary abstractions. Falcon cuts to the chase with a clean design that embraces HTTP and the REST architectural style.

Features:
Falcon tries to do as little as possible while remaining highly effective.
• Routes based on URI templates RFC
• REST-inspired mapping of URIs to resources
• Global, resource, and method hooks
• Idiomatic HTTP error responses
• Full Unicode support
• Intuitive request and response objects
• Works great with async libraries like gevent
• Minimal attack surface for writing secure APIs
• 100% code coverage with a comprehensive test suite
• Only depends on six and mimeparse
• Supports Python 2.6, 2.7, 3.3, 3.4 and 3.5
• Compatible with PyPy and Jython.